But what is a chapter? Is that a page on the root level?
Yeah - at least that’s what I call it (maybe it’s wrong?).
I always think of a site in these terms;
- Book
- Chapter
- Page
- Items
And those items stand for;
- Site
- Root-level page (mostly visible in the main menu)
- Sub-pages of every root-level page
- Page elements (DOM level)
I know this is not 100% correct, because a chapter is a page and can contains pages (which are chapters as well…).
But to keep an eye on the basic set-up I always think in these terms ![:slight_smile: :slight_smile:](https://emoji.discourse-cdn.com/apple/slight_smile.png?v=9)
So a chapter contains at least one page (the page that powers the chapter) and can contain sub-pages.
When you have 9 chapters, you will always have 9 pages.
But when 2 chapters also have sub-pages, the total amount of pages is… 9 + 2 = 11
I hope this makes sense ![:slight_smile: :slight_smile:](https://emoji.discourse-cdn.com/apple/slight_smile.png?v=9)
There was an error in the widget; the images were counted as chapters. I fixed it, but please do download the newest version.
Lol - I created my own (flat file based) CMS in the late '90’s, and I did use the same concept;
- Language
- Book
- Chapter
- Page
- Items
That way I could manage “complex” site with a lot of content easy; I always knew which page belonged to a certain chapter ![:stuck_out_tongue: :stuck_out_tongue:](https://emoji.discourse-cdn.com/apple/stuck_out_tongue.png?v=9)
It looks like rubbish… all iFrames and inline scripting ![:frowning: :frowning:](https://emoji.discourse-cdn.com/apple/frowning.png?v=9)
But it also worked with plain textfiles for the content and did have dynamic (sub-) modules.
You could also schedule posts and add comments to it, in case you were collaborating in an online team…
Please notice, this is more than 15 years old
and all written in .ASP