I found this post about extending columns.
I don’t want to extend multiple columns or a whole layout, just one single column:
# site/blueprints/pages/default.yml
title: Default
columns:
main:
width: 2/3
fields:
text: fields/text
sidebar:
extends: columns/sidebar
# site/blueprints/columns/sidebar.yml
width: 1/3
sections:
pages: sections/pages
files: sections/files
It doesn’t work, though. Am I doing something wrong?
Have you tried adding the column name?
# site/blueprints/columns/sidebar.yml
sidebar:
width: 1/3
sections:
pages: sections/pages
files: sections/files
Can’t remember what I tried when I wrote that post…
That doesn’t work. It would be pretty weird compared to extending sections/fields/tabs too, wouldn’t it?
If it worked for you when you wrote that post maybe there was a regression?
Extending columns is not mentioned in the Reusing & extending blueprints article either.
True. Hm, if you don’t find a solution, I’ll try to look into it later.
Hm, the only way I can get it to work is like this:
sidebar.yml
columns:
sidebar:
width: 1/3
sections:
pages: sections/notes
default.yml
title: Test
extends: sections/sidebar
columns:
main:
width: 2/3
fields:
text: true
But that turns the order you wanted upside down.
Or like this:
Default.yml
title: Test
extends: sections/sidebar
columns:
main:
width: 2/3
sections:
fields:
fields:
text: true
sidebar:
sections:
notes: false
sidebar.yml
columns:
main:
sidebar:
width: 1/3
sections:
notes: sections/notes
pages:
type: pages
create: default
template:
- about
- home
- default
With main defined but empty.
Thanks a lot for checking 
Both hacks have some downsides, so I’ll stick with inline columns.
Considering you can extend every other element, I’ll add an issue in the ideas repository.
1 Like