Lightning's mission is to enable developers to create great authoring experiences and empower editorial teams. Through custom modules and configuration, Lightning aims to target four functional areas:
- Layout
- Preview
- Media
- Workflow
You'll notice that Lightning 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 Lightning has done. So we started with a blank slate and justified each addition from there.
This is an early release of a subset of the planned features for Media, Layout and Workflow.
The current version of media includes the following functionality:
- A preconfigured Text Format (Rich Text) with CKEditor WYSIWYG.
- A media button (indicated by a star -- for now) within the WYSIWYG that launches a custom media widget.
- The ability to place media into the text area and have it fully embedded as it
will appear in the live entity. The following media types are supported:
- Tweets
- Instagram Posts
- YouTube Videos
- Images
- Drag-and-drop image uploads
- Ability to create new media through the media library (/media/add)
- Ability to embed tweets, Instagrams, and YouTube videos directly into CKEditor from an embed code
We hope to make the following enhancements to the Media feature:
- Ability to float media left or right, display inline, or display block with no float
- Ability to resize media and crop image media
- Support for audio assets (SoundCloud, etc.)
Lightning provides the ability to create a landing page through a custom form wizard that uses Page Manager and Panels + Panels IPE. Two layouts are provided by defaults (via Panels) and others can be added through the Layout Plugin or contrib such as Radix Layouts.
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 (archived, draft, needs review, and published). 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.
The roadmap is subject to change, but our projected schedule is:
- Late February 2016: Full Layout Support
- Late March 2016: Tagged release
You can also look for general enhancements along the way like OOTB Pathauto with sane defaults and preconfigured roles and permissions that we think the majority of site builds will use.
# Move the tests folder into docroot and switch into that folder.
# From docroot:
mv profiles/lightning/tests tests && cd tests
# Copy the behat.local.example.yml to behat.local.yml and replace BASE_PATH
# with the path to your local install.
cp behat.local.example.yml
# Install dependencies with Composer.
composer install
# Run the tests
bin/behat --profile=dev
# Requires Node.js and NPM.
# From /profiles/lightning/modules/lightning_features/lightning_media/tests/js;
npm install && npm test