Inside the HTML file’s body, you’ll see an HTML structure very similar to your projects table of contents: the entire project’s content is wrapped in a
div element with the CSS class
pmb-project. Inside that are
divs with CSS classes
The main matter’s structure depends on how many levels of nested content it contains.
If there is no nested content (ie, just one layer of sections), there will just be a list of divs with class
pmb-article-wrapper, each containing a tag with the class
At first, the
pmb-article-wrapper divs appear unnecessary. But you’ll see how they’re consistent with what’s coming up…
If your project’s contents are divided into parts, ie has 1 level of nested content, it builds on the HTML structure from before.
For each part, there will be a div with the CSS class
pmb-part-wrapper containing an element with the CSS class
pmb-part (very similar to before). What follows is the exact same as a project with no parts: a series of divs with the class
pmb-article-wrapper, each containing an element with the CSS class
More levels of nesting are possible, depending on the design. The next level up are “volumes”, which are divided into parts. The next level up from that is “anthologies” which are divided into volumes.
The HTML structure repeats with each of these higher levels: for each volume there is a
pmb-volume-wrapper which contains a
pmb-volume and then a list of
pmb-part-wrapper, etc. Likewise, for each anthology there is a
pmb-anthology-wrapper which contains a
pmb-anthology followed by a list of
What if you have some articles organized into projects, but some outside of projects? What HTML structure will that have? Will the content that’s not nested be considered a “part” or an “article”? An “article”. Whether a section is an article, part, volume, or anthology is determined by how many levels of content there are below it.
As always, if you have further questions, please contact us.