Skip to Content

Config Files

Sitepins stores all project settings directly inside your Git repository under the .sitepins folder. This ensures configuration stays version-controlled alongside your code.


πŸ“ Repository Structure

your-repository/ β”œβ”€β”€ .sitepins/ β”‚ β”œβ”€β”€ config.json # Content, media, and public folder mappings β”‚ β”œβ”€β”€ schema/ # Form blueprints for collections (e.g. blog.json) β”‚ └── snippet/ # Reusable shortcodes & component blueprints β”œβ”€β”€ src/content/ # Your markdown and data files └── public/images/ # Your media files

πŸ“„ .sitepins/config.json

The .sitepins/config.json configuration file open in the code editor

The central configuration file is automatically managed by the Sitepins UI:

{ "content_dir": "src/content", "media_dir": "public/images", "public_dir": "public", "default_frontmatter": "yaml", "default_extension": "md" }
  • Zero Vendor Lock-In: You can edit .sitepins/config.json manually in any text editor, or through Project Settings β†’ Configure.
  • Portable Across Environments: If a teammate clones your repo, Sitepins recognizes the configuration immediately without requiring re-setup.
Last updated on