Make yourself
at home.

Supper is a Food & Recipe Journal theme for Ghost: a home for everyday cooking, seasonal recipes and stories from your kitchen. This guide takes you from a fresh theme installation to publishing and maintaining your own site.

Start with the quick setup, then use the chapter list or guide search when you need a specific answer. No build tools are needed to install the supplied theme ZIP. Basic recipes use Ghost’s normal editor blocks.

• A working Ghost 6 publication and an owner or administrator account that can upload themes and change settings. Check the current Ghost hosting plan allows custom themes if you use Ghost(Pro).
• The installable supper-0.7.4.zip, plus the supplied routes.yaml. A documentation archive is a separate download, not the theme to upload.
• Your site name, logo if you have one, and your own licensed photographs and content.
• Working transactional email for signup/sign-in and administrative recovery. Self-hosted Ghost needs a mail configuration from your hosting provider or SMTP service. The theme does not include an email account.

Before changing an established site, back up its content, images, active theme, settings and routes. Keep a copy of template edits. Try the theme on a staging site first if you already have custom collections or important URLs.

Supper’s interface and the recipe heading convention are English. The current compatibility range is Ghost >=6.0.0 <7.0.0; this guide does not claim Ghost 7 compatibility. Admin labels may vary between Ghost versions. Use the Settings search if a label has moved.

1. Install the theme. Upload the installable ZIP and activate Supper. To start with samples, follow Import demo content before completing the remaining steps.
2. Upload routes. Use the separate routes upload in Ghost Admin.
3. Add your navigation. Recipes → /recipes/, Kitchen journal → /journal/, Our table → /about/.
4. Set your brand. Choose your site name, logo, fonts and theme palette.
5. Publish a recipe. Add the internal tag #recipe, a public primary tag, native Ingredients/Method blocks and your own content.
6. Fill the editorial sections. Use #seasonal, #weeknight and #journal as explained in Home setup. Leave at least one recipe unreserved for the hero.
7. Create Our table. Publish an About page with the slug about and update your author profile.
8. Check the visitor journey. Test mobile, light/dark, Search, email signup and the member view on your own site.

Do not expect the theme upload to create posts, pages, tags, navigation or editor Snippets automatically. Those belong to your publication.

1. Open your publication’s Ghost Admin at your-site-domain/ghost/.
2. Go to Settings → Design & branding. Open the theme controls and choose Change theme, then Upload theme. Depending on your Ghost version, this can be inside the Design/Customize view.
3. Select supper-0.7.4.zip without extracting that installable archive.
4. When Ghost finishes validation, activate Supper and open the public site.
5. Continue to the separate routes step. Theme activation alone does not replace your routes.

If your browser automatically unzips downloads, locate the original ZIP or download it again. If your purchase contains a larger product bundle, extract that outer bundle and upload only the installable Supper theme ZIP inside it.

Official reference: Installing a Ghost theme.

Routes create the curated Home, recipe collection and kitchen journal. Keep a download of your current routes before replacing them.

1. Open Settings → Advanced → Labs and find Routes or Upload routes YAML. Some Ghost versions show Labs directly in Settings.
2. Download your current routes file as a backup.
3. Upload the Supper routes.yaml supplied alongside the theme. You can also extract a copy from the theme ZIP.
4. Visit /, /recipes/ and /journal/ to confirm the new layout.

Download Supper routes.yaml

routes:
  /:
    template: home
collections:
  /recipes/:
    permalink: /{slug}/
    template: custom-recipes
    filter: tag:hash-recipe
  /journal/:
    permalink: /{slug}/
    template: index
    filter: tag:-hash-recipe
taxonomies:
  tag: /tag/{slug}/
  author: /author/{slug}/

Official reference: Ghost content collections.

Open Settings → Site → Navigation. Add these entries to Primary navigation and save:

Primary navigation appears in the header and collapses behind the mobile menu button. Use Secondary navigation for the footer. Labels are yours to change; links must point to routes or pages that exist.

Supper currently supports a single-level menu. Nested labels or special prefix characters do not create dropdowns. Keep the header concise; put extra collection links in Recipes or the footer.

The theme’s header includes its own Search, color toggle and membership controls. You do not need to add duplicate links for those. When membership is available, visitors see Join the table and signed-in members see Your account.

Official reference: Ghost site navigation.

Open Settings → Design & branding and choose the Brand tab. Set the publication icon and logo, then choose Heading font and Body font under Typography. Save the changes. Change the publication title in the site’s general settings.

The header uses your uploaded logo; if no logo exists, it uses the site title. The footer uses the site title. Choose a logo that stays legible against both light and dark backgrounds. Use the native preview and check the mobile header rather than relying on the uploaded image’s original dimensions.

Ghost supplies the selected heading and body fonts. Theme default uses Georgia/serif for headings and Arial/sans-serif for body text. Keep font choices readable for quantities, fractions and long instructions.

To use Ghost’s native accent color, set Theme → Site wide → Color palette → Brand. Tomato, Olive, Saffron and Plum use their own light/dark accents. Brand may adjust an unreadable accent toward the text color; the displayed accent is not guaranteed to match every input color exactly.

Default color scheme is the starting choice for new visitors. A visitor’s saved header-toggle choice takes precedence. System follows their operating system until they make a manual choice. Use a fresh private window when checking a changed default.

Supper also provides presentation styling for supported native Search, Portal and Comments frames. Those applications still own their forms, account and discussion behavior; arbitrary third-party embeds do not inherit every theme choice.

Official reference: Ghost design settings.

Find the Brand controls in Ghost Admin

These are unedited captures from the Supper 0.7.1 installation. The controls are unchanged in 0.7.4. On a small screen, open an image to read its original full-size controls.

Home is assembled from posts and author/tag information. You do not edit it as an ordinary Page, and the block order is fixed. Configure its copy and visibility in Theme → Homepage.

A useful starter content plan

Publish at least one unreserved recipe for the hero, several more unreserved recipes for Fresh, up to three seasonal recipes, up to four weeknight recipes, and two journal stories. Add images to the public tags you want in occasion links and fill in the hero author’s profile.

Empty optional sections are omitted and limits are maximums. If every recipe is reserved, the hero has no eligible post and Meet the cook has no lead author. The Ghost Featured toggle does not select these Home posts; the template uses tags and publication order.

Turning off Show home signup affects Home only. Other page signup panels remain separate and also depend on native membership being enabled.

Home block switches in Ghost Admin

1. Create a new Post. Enter a descriptive title, a custom excerpt and optionally a feature image with accurate alt text.
2. Add a public collection tag, such as Weeknight suppers, as the first public tag. Add the internal tag #recipe as well. Type the leading # when creating an internal tag in Ghost Admin.
3. Start with an ordinary introductory paragraph.
4. Add a Heading 2 named Ingredients. Follow it with a native bulleted list: one ingredient per item, including quantities and units as normal text.
5. For ingredient groups, add a Heading 3 such as For the dressing and another bulleted list before the next Heading 2.
6. Add a Heading 2 named Method, then a native numbered list with one instruction per step.
7. Optionally add Heading 2 Kitchen notes and paragraphs for your tested substitutions, storage or serving notes.
8. Set access, preview the post, then publish when ready.

Keep Ingredients and Method in English. The checklist recognizes a native H2 beginning with Ingredients and bulleted lists before the next H2. Do not put the entire recipe inside a Markdown or HTML card: the checklist intentionally skips card contents. Nested subitems remain ordinary bullets.

On the published site, readers can check ingredients, see progress, reset the list, jump to ingredients and enter Focus mode. The optional contents list uses actual H2 headings. Checklist state resets on reload. Focus mode does not keep a device screen awake.

Download the recipe block checklist

Prep time, cooking time and yield are your authored facts, not automatic estimates. Basic recipes work without this panel.

1. Insert a native HTML card immediately after the introduction.
2. Paste the example below and replace all uppercase placeholders with accurate information for this recipe.
3. Keep the recipe-facts class. Save the card as a Recipe facts Snippet if you want to reuse it.
4. Preview the article. The theme moves the existing card into the recipe header without duplicating it.

<div class="recipe-facts">
  <div><small>Preparation</small>YOUR PREP TIME</div>
  <div><small>Cooking</small>YOUR COOKING TIME</div>
  <div><small>At the table</small>YOUR YIELD OR SERVINGS</div>
</div>

Download the optional facts template

Values might be 15 minutes, 35 minutes and 4 bowls for your own tested recipe; these are examples, not universal defaults. Use No cooking when accurate. Remove a field’s entire inner <div>…</div> line for an unknown value, or omit the whole card. Never publish placeholder words.

This optional workflow requires editing the short HTML text in the card. Supper does not add dedicated cooking-time form fields in Ghost Admin. Without JavaScript, facts remain readable where you placed them in the article. No facts card means no empty metadata panel.

Facts are part of the accessible recipe body. They are not included in the guest recipe body when the post is restricted. The theme does not generate Recipe JSON-LD, calculate nutrition, convert units or scale quantities.

Once you have created your native recipe blocks, select the body content and choose the snippet icon in Ghost’s editor toolbar. Name it Recipe starter. To insert it into another post, use the slash menu and select the saved snippet, or type /Recipe starter on a blank line and choose it from the menu.

Save the optional facts card separately as Recipe facts if useful. After insertion, replace all placeholder text and use the card’s Edit control to change its HTML values.

Snippets copy body content only. They do not set a post’s title, excerpt, tags, access, author or feature image. Add #recipe to each new recipe. Changes to a saved snippet do not rewrite older posts.

The files in Downloads are authoring helpers, not a Ghost import file. Theme installation does not install the local demo’s Snippets into your site.

Official reference: Ghost reusable snippets.

A recipe normally has a public tag such as Weeknight suppers and the internal tag #recipe. Public tags appear on the site and get archive pages; internal tags control selection behind the scenes. Add a clear tag name, slug, description and feature image in Ghost’s Tags area.

Set Recipe collection tags to comma-separated public tag slugs, for example:

weeknight-suppers,vegetable-forward,weekend-baking

Use existing slugs without # prefixes or spaces inside a slug. Up to eight matching tags appear as navigation links. Ghost determines their returned order; this field selects which tags appear, not their manual order. Leave it blank to keep only All recipes.

The links open native tag archives with pagination. A tag archive can include journal stories as well if you assign that public tag to them. It is not a combined filter for cooking time, diet or ingredients.

Related recipes match the current post’s primary public tag and #recipe, excluding the current post. Related journal stories match the primary tag but exclude #recipe. No primary tag or no matching posts means no related block. Use Show related posts and Related posts limit in Post settings; the limit is an upper bound.

Create an ordinary Post without #recipe. It uses the journal article layout and appears in /journal/. Add the internal tag #journal if it should also be eligible for Home’s journal block.

Set the title, feature image/alt text, custom excerpt, author and body in Ghost. The journal archive follows publication order, with a lead story and remaining entries without duplicating that lead on the same page. The Featured toggle does not select the lead.

Use native headings, paragraphs and supported editor cards for stories. Reading time describes the article; it is never presented as cooking time. The journal article includes native Comments and related journal stories when available.

Create Our table

1. Open Pages in Ghost Admin and create a Page.
2. Give it your own title, excerpt and body. Set the URL slug to about.
3. Optionally add a feature image, alt text and caption. Publish the page and link Our table to /about/ in navigation.

The theme automatically uses page-about.hbs for this slug. Its title/feature-image display respects the page’s native visibility control. The editorial principles, invitation and discovery section include fixed template text; your story body comes from the editor.

Update author profiles

Open the author’s profile from Ghost Settings/Staff or the staff profile area available to your role. Edit their name, bio, portrait, location and website. These feed the author archive. Home’s cook introduction uses the first author of the hero recipe; it does not have a separate author selector.

Create other pages using normal Ghost Pages and add their destinations to navigation yourself. Missing author portraits or post images have theme fallbacks, but real, consistent photography gives the strongest result. Policy/legal page content is supplied by the site owner.

Open Design & branding → Theme. Supper has 10 Homepage, 7 Site wide and 3 Post settings. Save after previewing. Native Brand controls, Navigation and membership settings are separate.

Homepage

Site wide

Post

The settings panel in Ghost Admin

The screenshots below show the actual 0.7.4 controls alongside their live preview. Scroll the right-hand panel to move between Homepage, Site wide and Post. Save only after making your own intended changes.

Configure membership access and Portal in Ghost’s native settings. The theme provides signup/account links and access-aware templates; it does not create a separate account system.

1. Enable the signup access appropriate for your publication.
2. Configure Portal’s branding, available plans and account/support details in Ghost.
3. For self-hosted Ghost, ask your host to configure transactional mail and confirm sender-domain authentication. Test a real signup/sign-in email at an address you control.
4. On each post, choose public, members or paid-member access. View the same page while signed out to confirm the intended gate.

Members sign in through Ghost’s email flow; depending on its current Portal version, the email can provide a link and a six-digit verification code. Administrative password recovery is a separate Ghost flow. The theme does not store member passwords or deliver email itself.

Signup/account panels are shown only when native membership is available. Show home signup affects the Home panel; disabling native membership affects membership-dependent controls throughout the theme.

Transactional email versus newsletters

Signup/sign-in messages are transactional mail. Newsletter delivery is configured separately in Ghost; a working SMTP account does not automatically configure bulk newsletter sending. For self-hosted newsletters, follow Ghost’s documented Mailgun setup. Supper styles your website, not the email newsletter template.

Paid membership

Paid tiers and checkout use Ghost’s own Stripe integration and require a supported Stripe setup. Buying Supper does not configure a payment account. Validate checkout and tier access on your own staging setup before selling paid subscriptions. Supper’s current tests do not certify a completed production payment lifecycle.

Restricted ingredients, method and authored facts stay outside the guest recipe body. Images and files uploaded to Ghost are ordinary web assets: a member gate is not private file storage.

References: Ghost mail configuration and Ghost memberships.

Search

Use the header magnifying glass or Find a recipe button. Search is Ghost’s native application and searches the publication, including journal stories. It is not a recipe-only ingredient or dietary search engine.

Portal

Join the table opens signup; Your account opens the signed-in account view. You can add native links such as #/portal/signup, #/portal/signin and #/portal/account where needed. Their behavior follows your Ghost membership configuration.

Comments

Enable Comments in Settings → Membership → Access, choosing the audience permitted by Ghost. Native Comments appear in accessible recipe/journal articles. Readers need an eligible signed-in membership to contribute; Ghost handles moderation and notifications.

Test Search, Portal and a real comment after configuring your own publication. If an embedded app fails, check its network requests, Ghost settings and browser extensions, then compare in a current standard browser. Do not install development iframe adapters or patch Ghost core as part of normal theme setup.

Official reference: Ghost Comments.

Use the native editor for images, gallery cards, quotes, tables, video, audio, toggles and other Ghost cards. Keep Ghost’s normal card assets available; Supper loads article styles on posts and pages. Third-party embeds still depend on their provider.

• Feature images: choose a clear subject and sensible crop. The theme serves responsive image sizes up to 1600 px; uploading a huge original will not improve every small card.
• Alt text: describe meaningful image content. Do not repeat surrounding paragraphs or use filenames as alt text.
• Galleries and wide images: use native gallery and width controls. Supper does not include a separate custom photo viewer.
• Tables: keep headings meaningful and the table concise. Wide article tables scroll inside their own region so the page remains readable on mobile.
• Video/audio: provide captions/transcripts when appropriate, poster art and reasonable file sizes. Avoid several autoplaying or heavy embeds above the recipe.
• Colors inside cards: author-chosen card backgrounds and text may need manual contrast checks in light and dark mode.

Use only media you can publish and redistribute as needed. The separate demo package includes CC0 photographs under its supplied licenses; the theme code license does not override those rights. Remove fictional people, sample facts and placeholder content before launch.

1. Use the editor’s Preview action to inspect the article. Check the mobile preview and the actual public page when published.
2. Before publishing, confirm the title, excerpt, author, public primary tag, #recipe if appropriate, alt text and access level.
3. Choose Publish. Review Ghost’s website/email delivery choices carefully. Select website-only publication when you do not intend to email subscribers.
4. For a future release, use Ghost’s scheduling controls and verify the publication’s time zone and the planned date before confirming.

Drafts and scheduled posts do not appear in public Home/collection queries until published. Previewing a change does not necessarily save Design settings; use Save there. The theme does not override Ghost’s scheduling or newsletter-recipient controls.

Check the printed recipe

Open an accessible recipe and choose Print recipe. Inspect your browser’s print preview before printing. Supper removes site navigation and surrounding panels, using a light paper layout. The accessible article and notes print; it is not a shortened recipe-card export. Browser headers/footers, paper size and margins are controlled in the print dialog.

Set meaningful titles, excerpts, feature images and metadata in Ghost’s native post/site settings. Supper retains Ghost’s normal head/footer integration and uses semantic article structure. Check the public URLs and redirects when moving an existing site.

Supper does not automatically generate Recipe structured data. Native article metadata is not Recipe JSON-LD. Do not assume a recipe’s checklist or cooking facts make it eligible for Google recipe rich results. No nutrition, rating or timing values are invented by the theme.

For a fast site, upload appropriately sized/compressed images, keep the number of font families small, limit heavy third-party scripts/embeds and use sound hosting/caching. Measure the public HTTPS site with realistic content, including an article as well as Home. Scores vary with hosting, network, content and Ghost’s native applications; no fixed PageSpeed score is guaranteed.

Check link and focus visibility, keyboard navigation and your chosen colors whenever you customize the design. Theme checks do not certify every author-selected background, embed or image overlay.

Performance assets in 0.7.4

Static JPEG priority covers use responsive AVIF derivatives with a WebP fallback; other priority covers and occasion icons use WebP, all generated by Ghost. Lazy photographs retain their source format to avoid recompression growth; original uploads and image licenses remain unchanged. Home preloads its actual selected lead image and uses smaller occasion icons. Lazy images have low fetch priority. Recipes containing native card markup retain their native editor-card assets, as do other posts and pages. Plain recipes skip the unused card CSS/JS bundle. Search, Portal and Comments remain available.

Home and reading views embed partials/home-styles.hbs copied from assets/css/screen.css. Reading views also embed partials/content-styles.hbs from assets/css/content.css. If you edit CSS and zip manually, update these partials too; the workspace product builder regenerates them automatically. Collection pages retain the cacheable external stylesheet. The supplied ready-made ZIP needs no build step.

Start with editable sample content using the separate Supper demo ZIP. It contains 12 recipes, 2 Kitchen journal stories, Our table and Photo credits pages, 6 public collection tags, 5 internal tags and 19 locally packaged CC0 photographs. Recipe bodies use native Ghost headings and lists, so Ingredients checklists, Method, the table of contents and Focus mode work without an external recipe plugin.

• Supper demo 0.7.4 ZIP — included in the customer downloadImport this separate ZIP unchanged; it includes the photographs.
• Import checklistPlain-text setup, conflict handling and cleanup instructions.
• Photo sources and creditsIndividual photographer, source file and CC0 links for every photograph.
• Demo content licensesPhotograph rights and permission to reuse the original sample text.

Import in Ghost Admin

1. Install and activate Supper first. Use supper-0.7.4.zip in Theme settings.
2. Open Settings → Advanced → Import/Export. In Migration tools, choose Universal import. Labels may differ between Ghost versions.
3. Select supper-demo-0.7.4.zip. Upload the ZIP itself, without extracting it or choosing export.json separately. It belongs in Universal import, not the theme uploader. Wait for completion and review any import report.
4. Check Posts, Pages and Tags. Expect 14 imported posts and 2 imported pages. The recipes have #recipe; every imported post/page has #supper-demo. Ghost may add its own dated import tag. Existing content is retained.
5. Resolve page conflicts. A new Ghost site already has an About page. Preserve or rename that page, then set the imported Our table page slug to about if Ghost imported it as about-2. Review all actual slugs before linking. Draft the default Coming soon post if you do not want it in Kitchen journal.
6. Upload or merge the supplied routes. Follow the Routes chapter. Add primary navigation: Recipes → /recipes/, Kitchen journal → /journal/, Our table → /about/. Add Photo credits → /photo-credits/ in secondary navigation.
7. Make the site yours. Set your logo, fonts, palette and theme options. Update your own staff name, bio and portrait. Ghost assigns imported content to the destination owner; no fictional staff account is created.
8. Review access and email. One recipe is Members only and one is Paid members only to demonstrate native access gates. Change them to Public if unnecessary. The package does not configure a paid plan, Stripe, Portal or email delivery.

How the Home content is organized

The demo has one general recipe for the hero and four further general recipes for Latest. Three recipes carry #seasonal; four carry #weeknight. These pools are separate, so the default Home does not repeat a recipe. Two posts use #journal without #recipe. Four public tags have images for the occasion links. Keep these tags when editing the samples, or follow the Home chapter to build your own pools.

Images, sample text and removal

All 19 photographs are packaged locally and listed as CC0 on their individual Wikimedia Commons source pages. See the supplied credits and CC0 terms. Images illustrate the layout and may show different preparations; photographers did not test or endorse the sample recipes. Original sample prose may be copied, edited and published with your site. Review recipes, quantities, facts, allergies and food safety before publishing your own production content.

Import once. Re-importing can create duplicates and suffixed slugs; it does not synchronize or update earlier samples. To remove demo content, identify posts with #supper-demo, inspect Pages separately, and remove only confirmed samples. Keep any shared tags or images still used by your own content. A site backup is the reliable rollback option.

The package contains no users, members, comments, credentials, mailing lists, site settings, subscriptions or payment data. Snippets, navigation, routes, Brand, theme settings and transactional email need normal manual setup.

Authoring helpers

• routes.yamlUpload separately in Ghost’s Routes settings.
• Recipe starter checklistInstructions for native editor blocks; not an import file.
• Recipe facts HTMLOptional authored HTML card; replace placeholders.

Use Admin for routine changes. Keep a record of any template/CSS modifications so they can be reapplied when updating the theme.

The fixed announcement strip at the top of Supper is template copy; Ghost’s separate Announcement bar feature does not edit that text. There is no visual page builder or drag-and-drop block ordering. Some wording intentionally requires template editing because the 20-setting set focuses on the main publishing workflow.

For small custom CSS, Ghost Code Injection may be appropriate. For template edits, keep an editable backup of the theme, update only the intended files, then zip the theme files with package.json at the archive root and validate before uploading. Do not rename custom setting keys casually: upgrades can lose values associated with removed keys.

1. Read the new release notes and verify its Ghost compatibility before updating.
2. Download your active theme and routes. Back up content, images and important settings separately. Record theme options and any custom code/template edits.
3. Test the new ZIP on staging. Upload and activate it through Ghost Admin, following the installation chapter.
4. Upload routes only when the release instructions require changes; compare with any existing custom routes before replacing them.
5. Reapply reviewed custom edits as needed. Test Home, Recipes, a public recipe, a member recipe, Journal, About, Search and Portal on desktop/mobile.
6. If a theme regression occurs, reactivate your saved previous theme and, if you changed routes, restore the saved routes. Content/database changes require their own backup plan.

A theme update does not intentionally replace your posts, images or members. It also does not preserve edits made inside the old uploaded theme folder automatically. Keep documentation and authoring helpers with your product files rather than uploading the documentation ZIP as the theme.

Start with the symptom below. Check the theme version and Ghost version before changing code. Never share passwords, tokens or private member data in a support report.

• Confirm routes, navigation and About all resolve on your own domain.
• Replace demo identities, placeholder words, untested sample facts and unlicensed images.
• Keep an eligible general recipe for the hero and deliberate seasonal/weeknight pools.
• Check logo, fonts, palette, image crops and text on desktop and mobile in both modes.
• Try Ingredients, Reset, Focus mode, Escape, links and print preview with a real recipe.
• Test Search and Portal, then receive an actual signup/sign-in email at an address you control.
• Check member content signed out and signed in. Test native Comments with an eligible member.
• If selling subscriptions, validate your own payment configuration and tier access.
• Confirm backups, legal pages, support contact and production HTTPS.

This is your publication setup checklist, not a claim that all production hosting/payment combinations have already been tested by the theme author.

Contact Atelier Themes at contact@atelierthemes.com. Include the theme version, Ghost version, affected public URL, browser/device, a screenshot and steps to reproduce. If you have an order reference, include it. Share only the minimum information needed; never email credentials, API keys or member exports.

Describe whether the issue concerns theme layout, authoring, hosting/email, a native Ghost application or custom code. Your host or the relevant platform provider may need to help with server configuration and account/payment delivery. Your purchase includes 12 months of email support and access to released updates from the original purchase date. Continued use of versions lawfully received is allowed after that period; renewal is optional, with no automatic recurring charge. See License, support and refunds for the Single Website terms and the voluntary 14-day refund promise, including requests after download or customization. Mandatory statutory rights remain unaffected.

Purchase terms

• Read the complete license, support and refund policies
• Single Website license
• 12-month support and update policy
• 14-day refund and cancellation policy
• Third-party and demo-content notices

Official Ghost references

• Theme installation
• Routing and content collections
• Design and fonts
• Site navigation
• Reusable Snippets
• Member Comments
• Self-hosted configuration and mail

Guide prepared for Supper 0.7.4 · 29 October 2026 · English edition.