locomotivecms/engine — Issue #316: Layouts
Author: did
Created: 2012-03-04 11:41:27+00:00
State: open
Labels: feature

I heard a lot of "complaints" about not having layouts in locomotive. At first, I didn't plan to implement layouts because of the locomotive philosophy: pages are layouts for other pages.
But I do admit that in a lot of cases, it makes a lot of sense to have layouts. So I agree to implement it so that we can use both of the 2 ways.
On a code standpoint, the Page class will inherit from the Layout class. Besides, we'll have a whole section in the back-office to manage layouts.

How to assign a layout to a page ? super simple. {% extends 'layouts/my_layout %} :-)

Just a quick concern, what happens if we modify the name of a layout or delete of them ? What happens to pages related to these layouts ? Any thoughts ?