The layouts allows you to define the common markup of a web page inside its own file and then other templates can re-use that markup by just replacing the certain sections. In this, you will learn:

  • How layouts work in Edge
  • Using sections to inject content inside a layout
  • Known limitations and using components as an alternative

Creating a Layout

Layouts are the standard Edge template files, but written with the purpose to be extended by the other templates. For demonstration, lets create a layout to hold the markup for a blog.

node ace make:view layouts/blog
# ✔  create    resources/views/layouts/blog.edge

Now, open the newly created file and paste the following contents inside it.

<!DOCTYPE html>
<html lang="en">
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>{{ title }}</title>
        <a href=""> Adonis Blog </a>
        <li><a> Home </a></li>
        <li><a> Posts </a></li>

    @section('content')    @endsection  </main>

Next, create a new template file that will use the above layout and defines its own content.

node ace make:view posts/list

# ✔  create    resources/views/posts/list.edge

  <p> Here comes the list of posts </p>

Finally, render the posts/index.edge template.

Route.on('/').render('posts', { title: 'AdonisJS Blog' })

Now, if you visit http://localhost:3333, you must see the content being injected at the right place.

How it works?

  • The layout/blog.edge template is created with a purpose to be used as a layout and hence it defines @section that other template can inject content into.
  • Also, it relies on the title variable to set the page title.
  • The parent template (one using the layout) can inject the content by using the @section tag with the same name.
  • The @layout always have to be at the first line in the parent template, otherwise the layout is ignored.

Defining sections

Sections allows you to define areas in your layout that can be overwritten by the parent templates. You can create as many sections as you want, just make sure they all have unique names for a given layout.

<div class="content">


Most of the times, the sections inside the layouts are empty. So instead of writing @endsection, you can self close a tag by prefixing it with a bang (!) character.

<div class="content">
    @!section('sidebar')  </aside>

    @!section('content')  </main>

Inheriting Sections Content

The default behavior of sections is to overwrite the contents of a section defined inside a layout. For example:

The master template defines a scripts section that has a list of default scripts.

  <script src=""></script>
  <script src="/app.js"></script>

The parent template re-defines the scripts section with the intention to append a new script.


  <script src="/index.js"></script>

But, as per the default behavior of sections, the first two scripts defined by the master layout have been removed.

To address this problem, Edge sections comes with an inheritance model. Just like the Javascript classes, you can use the @super tag to inherit the existing content of a section.


  @super  <script src="/index.js"></script>


The layouts and sections are only evaluated during compile time and this approach comes with its own set of limitations.

  • The name of the layout and the section has to be a static string. You cannot compute these names from a Javascript expression evaluated at runtime.
  • You cannot nest sections inside each other. It is not really a limitation, but instead a design choice.
  • The parent template can only contain @section and @set tags. Everything else outside of sections is ignored.