Pages, posts, and files
© MyReady
Where pages, posts, and images live on disk, and when to open the Files tab instead of the everyday editor.
Teaching post. Draft it when the map is obvious.
Launch method: home. Blocks: Quick start.
Two views of the same project
Pages / Posts — daily work: copy, images, FAQ, HTML, draft, languages. Save triggers a rebuild.
Files — Hugo tree: font under static/fonts/, archive, search by name. Not a second site.
Do not edit the same thing in both places at once. One channel per task.
Where things live
| What | Path |
|---|---|
| Home | content/_index.en.md / content/_index.ru.md |
| Inner page | content/pages/<name>/index.en.md |
| Post | content/posts/<name>/index.en.md |
| Home images | content/media/ |
| Material images | next to index.*.md in the page or post folder |
| Shared static | static/ |
| Title, palette, AI | not in Markdown: Settings (Site title, Branding, AI) |
Folder name = URL. Contacts live in content/pages/contact/, not content/contact/.
Remember
- On pages and home you write H1 in the body. Posts take H1 from the card.
- HTML fragment is full-bleed; text and quotes stay in the column.
- Leave
themes/default/alone unless you truly need a custom theme. - API keys only in Settings, never in Markdown.
Practical order
- Create pages/posts in the editor (“+ New file”).
- Attach images with the Image block.
- Use Files for fonts, archives, tree search.
- After a manual file edit, reopen the same locale in the editor.
Next: Site agent, HTML snippets, FAQ.