Skip to content

Remove the "no resources in sub folders" restriction for branch bundles #11439

@bep

Description

@bep

I'm working on some cool stuff that requires some simplifications in how we process /content files.

Currently

  • resources for branch bundles (e.g. sections, home page) need to live in the root folder of that bundle.
  • every non-content-file inside /content that's not part of a bundle gets copied to /public as it would live in /static.
content
├── _index.md
├── foo.png
└── posts
    ├── _index.md
    ├── baz.png
    ├── images
    │   ├── image1.png
    │   ├── image2.png
    │   └── image3.png
    ├── p1.md
    └── p2
        ├── bar.png
        └── index.md

Given the above example, the images in posts/images will with this proposal be part of the posts section bundle.

That will in some (rare?) setups be a breaking change but I would argue that

  1. It feels more natural and is easier to understand/document.
  2. It will probably solve more problems that it breaks.

/cc @jmooring

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions