Alternative representation

[A----]

I've been fiddling with the idea for a while now. In many cases, I need to have different representations of the same page. There are ways (namely headers) but those have limitations. They does not use the same pipeline as page content (so, no plugins).

Here comes what I called Alternative Representations. It's one or more other markdown files next to the usual one. Its use cases are:

• Summaries but on steroïds
• Other kind-of-similar use-cases : having different representation of the page when displayed on the home page / search results page / …
• Complex content in classic or modular pages

Here's an super-simple illustration of the last use case. I need a two-columns page (or page module). Additionnally, I want to use the image-captions plugins. Here's what I get if I use a header:

Now, using the alternative representation:

Content pipeline (including plugins) processes the alternative MD file, caption is displayed.

My folder looks like this:

In my left-column template, I now use this:

{{ page.alternativeRepresentation('side-content').content | raw }}

As of now, implementation might have unexpected results in some cases (namely multi-language sites) and I may need some guidance there.

[mahagr]

Well, we had the same idea as I've implemented one to flex already. In there you can have an unlimited number of layouts for both collections and objects.

It should already kind of work for the Flex Pages as well, just define the layouts and use the render() method. Unfortunately, as it is now, all the layouts are shared between every page type... So that part may still need some work.