Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: de-RGB, remove hideblocks

With Magnolia "front-end development" we are referring to the most common task on most web projects: developing templates to generate the actual HTML of the projects. The links below point to information about working with Magnolia specifically as a front-end developer. 

We assume you already have Magnolia up and running.

Understand

Light development in Magnolia: Learn how to work with Magnolia without Java programming skills.

Modules : Magnolia projects are built out of modules, learn about the different kinds of modules and their structure.

YAML: Learn about using YAML to configure Magnolia. Spaces are important.

Introduction to templating: Magnolia templating mechanism explained.

Learn 

Hello Magnolia: Create a simple template in Magnolia. 

Creating a website with Magnolia: Create a website with Magnolia, including the creation of a light module.

Tip

Also check out the new front-end developer training courses offered by Magnolia!

Hide block

Tomas' stuff from conference is private, point to corp training site instead https://documentation.magnolia-cms.com/pages/viewpage.action?spaceKey=WORKSHOPSFE&title=Workshop+at+Magnolia+conference+2016

Light dev webinarhttps://wiki.magnolia-cms.com/display/WIKI/2015-09-02+light+development+webinar+handout

Develop

Magnolia CLI : Magnolia command line interface (CLI) is an  npm  package providing a CLI tool to setup and facilitate light development with Magnolia.  

Create light modules: Create and use a fully-functional template module.

Web resources: Access CSS, JS and other web resources.

Magnolia templating kit: Use these templates as they are or to gain inspiration to create your own.

Define template definitions: Define your blueprints for creating pages, areas and components.

Scripts and functions: Write template scripts and work with templating functions.

Define dialogs:  Define the editable content properties of your templates.

Work with images: All about storage and rendering.

REST: Access Magnolia content using REST.

Hide block

Template best practices?

 

Share your components - in your team, or with the community.

Deployment : Missing an overview, feels that the information is scattered all over. When to deploy war, when to deploy jar.

Java integration?

  • How does LD relate to Maven/Java development?
  • Working with light dev when you also need Java modules. Create maven modules to cover the workspace setup, bootstraps, Java etc., Then the other teams could create light modules that relied on those

    .

    Additional resources

    Cotoolz: IDE add-on which validates input and assists when editing YAML.


    Hide block

    For an exhaustive list of the documentation pages containing front-end information, see the front-end dev aggregated list