sunwei
1
Both of them are in Content Management.
Both of them are used to organize content.
Why we create two similar concept to org content, is there any specific reason?
Please help me to understand it well, so that I know what’s the best practices to use those two concepts.
1 Like
frjo
2
A page bundle is a single page with assets.
A section is a collection of many pages and/or sub sections.
sunwei
3
Hi frjo, Thanks for reply.
In the Page Bundles doc.
There are two types of Page Bundles.
- Leaf Bundle is for single page.
- Branch Bundle is for section pages
That’s why makes me confused, why we need those two different concepts for page and pages.
1 Like
Georg
4
- Branch bundles (for sections etc.) offer a list view and render a list template.
- Leaf bundles are single pages.
A list view requires a more complex data structure than a single page and is usually applied less often.
And there is another kind of content view one may say, which we can apply in a more flexible way: taxonomies and their terms.
1 Like
sunwei
6
That makes a lot sense.
Bundle related to filesystem. And section here is related to Page kind.
Based on those domain knowledge, here is my use case:
I want to use Hugo help me to build a online book service, which should have features like:
- Create book with name
- Create menu
- Create preface
- Create Chapter
- Create Section
- …
So the API provided by Hugo will looks like:
- Create book with name
- POST /site/name
- POST /site/page/home
- Create menu
- POST /site/page
- Create preface
- POST /site/page
- Create Chapter
- POST /site/page/section
- Create Section
- POST /site/page/section?parent
- …
Any suggestion?
Maybe I need to start another thread to discuss it.
sunwei
7
Just create another thread to continue the discussion, thanks a lot.