Download the PHP package nrel/dam without Composer

On this page you can find all versions of the php package nrel/dam. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package dam

Build Status

Drupal Dam

Dam's mission is to enable developers to create great authoring experiences and empower editorial teams.

You'll notice that Dam appears very sparse out of the box. This is by design. We want to empower editorial teams and enable developers to jump-start their site builds. That means that a developer should never have to undo something that Dam has done. So we started with a blank slate and justified each addition from there.

Installing Dam

The preferred way to install Dam is using our Composer-based project template. It's easy!

If you don't want to use Composer, you can install Dam the traditional way by downloading a tarball from our drupal.org project page. (Please note that the tarball does not contain any experimental features.)

You can customize your installation by creating a sub-profile which uses Lightning as its base profile. Lightning includes a Drupal Console command (lightning:subprofile) which will generate a sub-profile for you.

What Dam Does

Through custom modules and configuration, Lightning aims to target four functional areas:

Media

The current version of media includes the following functionality:

Extending Dam Media (Contributed Modules)

Drupal community members have contributed several modules which integrate Dam Media with additional third-party media services. These modules are not packaged with Dam or maintained by Acquia, but they are stable and you can use them in your Dam site:

Layout

Lightning includes the Panelizer module, which allows you to configure the layout of any content type using a drag-and-drop interface (Panels IPE). Lightning also includes a Landing Page content type for you to create landing pages with their own one-off layouts and content.

Any content type that uses Panelizer will allow you to set up default layouts for each view mode of that content type, which you can choose from (or override on a one-off basis) for individual pieces of content.

Eight layouts are provided out of the box by Panels. You can create your own layouts (see the Layout Plugin module) or install a contributed library of layouts like Radix Layouts.

Workflow

Lightning includes tools for building organization-specific content workflows. Out of the box, Lightning gives you the ability to manage content in one of four workflow states (draft, needs review, published, and archived). You can create as many additional states as you like and define transitions between them. It's also possible to schedule content (either a single node or many at once) to be transitioned between states at a specific future date and time.

Preview (Experimental)

The Workspace Preview System (WPS) gives site builders, editors, authors, and reviews the ability to send collections of content through an editorial workflow and preview that content within the context of the current live site. WPS is a collection of contributed Drupal modules with additional configuration UX improvements that all just works out of the box.

Note that the Workspace Preview System is experimental and is not currently included in stable releases of Lightning. If you would like to use it, see "Experimental Features" below.

Project Roadmap

We publish sprint plans for each patch release. You can find a link to the current one in [this meta-issue][meta_releases] on Drupal.org.

Experimental Features

Some components of Lightning (such as the Workspace Preview System) are currently experimental until they stabilize. Experimental features should be considered bleeding-edge and are not safe for production environments.

Experimental features are kept in Lightning's development branch. To use experimental features, you will need to create your Lightning code base from this branch. This can be done only with the Composer- based project template -- check there for more information on how to use experimental features.

Resources

You can find general best practices documentation inside the help directory of each Lightning "base" module. Integration with the Advanced Help module is planned.

Demonstration videos for each of our user stories can be found here.

Please use the Drupal.org issue queue for latest information and to request features or bug fixes.

Running Tests

These instructions assume you have used Composer to install Lightning. Once you have it up and running, follow these steps to execute all of Lightning's Behat tests:

Behat

$ cd MYPROJECT
$ ./bin/drupal behat:init http://YOUR.LIGHTNING.SITE --merge=../tests/behat.yml
$ ./bin/drupal behat:include ../tests/features --with-subcontexts=../tests/features/bootstrap --with-subcontexts=../src/LightningExtension/Context
$ ./bin/behat --config ./docroot/sites/default/files/behat.yml

If necessary, you can edit to match your environment, but generally you will not need to do this.

Known Issues

Media

Workflow


All versions of dam with dependencies

PHP Build Version
Package Version
Requires nrel/communications Version ^1.1.1.18
brightcove/api Version ^1.0
drupal/decoupled_auth Version ^1.0@alpha
drupal/default_content Version ^1.0@alpha
drupal/elasticsearch_aws_connector Version 5.x-dev
drupal/elasticsearch_connector Version 5.x-dev
drupal/file_entity Version 2.x-dev
drupal/page_manager Version ^4.0
drupal/taxonomy_manager Version 1.x-dev
drupal/file_download Version ^1.0
drupal/protected_file Version ^1.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package nrel/dam contains the following files

Loading the files please wait ....