This project is not covered by Drupal’s security advisory policy.

Demo of Geysir interface
Native paragrap interface

News: there is a new screencast: Landingpage Geysir experimental submodule!

LandingPage is a constructor tool that was designed specifically to allow building lading pages easily and quickly.

It was built with open architecture that simplifies adding new components. You can manipulate a set of Paragraphs and customize templates for existing Paragraphs to create your Landing Page

To get an idea for how this works, try installing 'LandingPage Event Example' submodule and Bootstrap Theme, which is required to run it.

Test it on simplytest.me

As soon as the instance runs, just turn on in Extends 'LandingPage Event Example' module or 'LandingPage Promo Example' module.

Also please try "LandingPage Geysir (experimental)" submodule, that provide extended Paragraph editing functionality in the view mode. This submodule uses Geysir module, with "sort" and "add new paragraphs" features added.

There are several submodules that generate dummy LandingPages (with sample pages to get you an idea without installing):
- LandingPage Event Example (http://landingpage.abzats.com/landingpage/examples/event)
- LandingPage CV Example (http://landingpage.abzats.com/landingpage/examples/cv)
- LandingPage CaseStudy Example (http://landingpage.abzats.com/landingpage/examples/casestudy)

Please donate to support the module.

I'm currently working on a tutorial for how to add new custom components and how to create beautiful pages.

Project is in active development. Alpha version is available.

More information in README.txt

Screencasts:

Projects with similar functionality:

The main difference is in the architecture of the modules.

Different supported paragraph types included in the main module in the Parade package, but in LandingPage package each supported paragraph type is a separate sub-module. So you can turn on and use paragraph types that you really need only. But the main idea of such separation is to have an open architecture solution. So one can create a separate paragraph type (need to follow the name convention to be automatically attached to LandingPage content type) as a custom module with new fields and thus extends the existing functionality.

The second difference is in the theme and templates approach:

  • LandingPage module provide Theme filed inside LandingPage content type. You can have themes and templates from scratch and another design for your landing page without inheriting of the existing styles of your default theme and stupid overwriting CSS properties.
  • You can set for each paragraph view mode a separate template (take a look in /themes/landingpage_bootstrap/templates/paragraph--landingpage-*.html.twig)
  • also there is an ability to add inline styles for each paragraph that, of course, not the best option, but provide extremely high and unlimited customization abilities in admin area.
  • for each paragraph you can set several classes and support them in your LandingPage theme, I'm not sure that Classy Paragraph approach does'n do the same. But as I remember my experience with that module it allow to customize one class only for each paragraph.

So my Package is not an out-of-the-box solution, but some kind of Drupal Lego or API that can be used by Drupal developers better that by content managers of Drupal sites.

Additional examples

Supporting organizations: 

Project information

Downloads