Configuration tells Sitepins where things live in your repository. It’s four fields, and Sitepins suggests values for all of them based on the framework it detected.

Step 1: Content Folder

The parent directory containing your content files — Markdown, MDX, JSON, YAML, or TOML.

Suggestions by framework:

• Astro / Next.js / TanStack Start — src/content
• Hugo — the language content folder, for example content/english (or exampleSite/content/english in theme repositories)

Click the dropdown to browse every folder in your repository and pick the one that holds your content.

Step 2: Media Folder

The directory where Sitepins uploads and manages images and other assets.

Suggestions by framework:

• Astro / Next.js — public/images
• Hugo — assets/images or static/images

Step 3: Public Folder

How your site refers to those assets in the browser.

Suggestions by framework:

• Astro / Next.js — public
• Hugo — static

When you select a Media Folder, Sitepins automatically suggests its parent as the Public Folder — pick public/images and it proposes public.

Media Folder vs Public Folder

These two are easy to confuse, so here’s the difference:

• Media Folder is the real path in your repository. Example: public/images/blog. It’s where uploads are written and what the media library browses.
• Public Folder is the prefix that gets stripped when generating URLs. Example: public. It’s what makes an image stored at public/images/blog/hero.png render as /images/blog/hero.png in your site.

Get the public folder wrong and images will look fine in the editor but 404 on the deployed site.

Step 4: Site Configs (Optional)

Select the configuration files that control your site’s theme, navigation, or metadata. Sitepins renders them as editable forms so non-technical editors can change a menu label or a homepage headline without opening a code editor.

Suggestions by framework:

• Astro / Next.js — src/config
• Hugo — config/_default, hugo.toml, data, i18n

You can select individual files (theme.json, menu.json, config.json), whole folders, or any mix. Selected files appear under Configs in the sidebar. See Config Files.

Saving Your Configuration

1. Review your selections.
2. Click Finish Setup on first run, or Update Configuration afterwards.

Sitepins writes .sitepins/config.json into your repository, plus a small manifest at <public folder>/.well-known/sitepins.json. Both are committed like any other change.

Once saved:

• Sitepins scans and maps your content files
• The folder tree appears in the sidebar
• The visual and Markdown editors become available
• The media library is ready

Commit Configuration

Below the folder setup is a single toggle: Custom Commit Messages.

• On — a dialog appears before each commit where you write the message and an optional extended description
• Off — Sitepins generates the message for you (“Update file”, “Rename X to Y”, “Create new blog”, and so on)

Turn it on if you follow a commit convention or work in a repo with strict history rules. Leave it off for a faster save loop.

Changing Configuration Later

Go to Project Settings → Configure at any time, adjust the paths, and save.

Next Step

Setup is done. Take a look around with the Interface Tour, or go straight to the Rich Text Editor.