An EdgePress article has YAML metadata followed by Markdown. Use the CLI to create the file, then edit the body below the second ---. This example collects the syntax I use for a practical note:

## What I noticed

A paragraph with **emphasis**, a [link](https://example.org/) and `inline code`.

- A short list
- Another point

> A quoted observation.

| Step | Result |
| --- | --- |
| Build | Static HTML |

- [x] Draft
- [ ] Preview

![A photograph](/images/walk.jpg)

!document[Report](/documents/report.pdf)

!embed[ishare](https://ishare.js.gripe/s/EXAMPLE)

The site renders headings, paragraphs, emphasis, links, lists, quotations, fenced code, GFM tables and task lists. Put code inside triple backticks with a language name. The page already displays the article title; body sections start at ##.

Copy media into content/assets/ before referencing its site-root path. A picture opens the shared image viewer; an explicit original URL is requested on activation. A local document is previewed automatically by the reusable document viewer. External documents need a registered service, current consent and CORS.

!embed[ishare](URL) is a standalone line, using the real published share URL instead of EXAMPLE. Register the service in plugins.consent.services before using it; requests wait for consent and demand. The same extension can be used in a Pages text element. Do not put embeds into article front matter.

Pages use structured elements, so a whole Markdown article should not be pasted into a Pages text field. Use the complete Pages example for layout. Preview with npm run dev and build before publication.