cf-backup../source/cf-backup.html.md.erb
(cloudfoundry/docs-bbr, whole page)../published/cf-backup.html)cf-backup.notes<div class="note caution"> with a
<ul> of four items, each opening with a bold sentence. Lists in notes
are always HTML and always in a <div> in the book
(survey).<p class="note">
with no </p>. 4 of the book’s 241 HTML notes are written this way, two of
them here.| # | Kind | Title | Sits in | Holds | Source |
|---|---|---|---|---|---|
| 1 | caution | Caution | the introduction, before “Supported Cloud Foundry configurations” (h2) |
a list of 4 items: bold lead-ins, 2 code spans, 1 link | L16-L29 |
| 2 | caution | Caution | “Selective backup and restore configurations for blobstores” (h3), after its table and before the h4 |
1 paragraph, 1 link to a heading on the page (#selective-backup-restore-steps) |
L66-L71 |
| 3 | note | Note | “Applying ops files in the correct order” (h3), after the last list, before “Next steps” (h2) |
1 paragraph, 2 code spans | L109-L111 |
“Sits in” is the heading of the section the note belongs to, as the notes check reads it: the nearest heading above the note, or the page title for a note before the first heading.
</p> at the end of each note’s paragraph, where the published page ends
it (the book’s Markdown processor wraps the note in a paragraph, and the
browser ends it at the next heading:
<p><p class="note caution"> … section below.</p>, published copy line
603). This is the cleanup of R-24
markup cleanup before conversion; the text does not change. As written,
the open notes break one tool and stop two others
(results).