Appearance
Lists
Press supports ordered and unordered lists with nesting and marker customisation.
Unordered Lists
xml
<ul>
<li>Market research and competitive analysis</li>
<li>Product design and prototyping</li>
<li>User testing and iteration</li>
<li>Launch planning</li>
</ul>Ordered Lists
xml
<ol>
<li>Submit the application form</li>
<li>Await confirmation within 5 business days</li>
<li>Complete the onboarding questionnaire</li>
<li>Attend the introductory workshop</li>
</ol>Nested Lists
Nest lists by placing a <ul> or <ol> inside a <li>:
xml
<ul>
<li>Engineering
<ul>
<li>Frontend</li>
<li>Backend</li>
<li>Infrastructure</li>
</ul>
</li>
<li>Design
<ul>
<li>Product design</li>
<li>Brand design</li>
</ul>
</li>
<li>Operations</li>
</ul>You can mix ordered and unordered lists:
xml
<ol>
<li>Phase One: Discovery
<ul>
<li>Stakeholder interviews</li>
<li>Market analysis</li>
</ul>
</li>
<li>Phase Two: Development
<ul>
<li>Architecture design</li>
<li>Implementation</li>
</ul>
</li>
</ol>Marker Styling
Customise list markers using the marker- prefix on any style attribute. These attributes target the bullet or number, not the list item content:
xml
<ul>
<li marker-font-color="#2563eb" marker-width="16pt">First item with a blue bullet</li>
<li>Second item with a blue bullet</li>
</ul>Alternatively, you can style all bullet markers in the <styles> section:
xml
<styles>
<ul>
<child name="li">
<marker-font-color>#2563eb</marker-font-color>
<marker-width>16pt</marker-width>
</child>
</ul>
</styles>
| Attribute | Description |
| ------------------- | ------------------------------------- |
| `marker-font-color` | Colour of the bullet or number |
| `marker-font-size` | Size of the marker |
| `marker-width` | Width allocated for the marker column |
| `marker-font-style` | Style (bold, italic) of the marker |
## Lists in Markdown Flows
Lists also work in markdown flows:
```xml
<flows>
<body type="markdown">
Key deliverables:
- Completed audit of existing systems
- Migration plan for legacy databases
- Training materials for new platform
Implementation steps:
1. Provision staging environment
2. Run parallel systems for two weeks
3. Cut over to production
</body>
</flows>