Product and build plan

SiteForge

A simple website builder for small businesses that want a polished, fast, secure website without WordPress maintenance, plugin upgrades, caching drama, or deployment guesswork.

View the build roadmap Read the technical plan

Made for businesses that need presence, not plumbing.

SiteForge targets local service companies, consultants, studios, restaurants, shops, and small teams that need company pages, team profiles, galleries, a small blog, and strong SEO, but do not want to maintain a CMS runtime on their public website.

Static output

Export to ordinary hosting

Published sites are plain HTML, CSS, JavaScript, and optimized assets. They can be deployed to FTP, SFTP, S3-compatible storage, or downloaded as a ZIP backup.

Guided editing

No layout-breaking drag and drop

Experts, designers, or AI create templates with fixed placeholders and exposed variables. Business users edit the content and approved options instead of rearranging the whole design.

Rails admin

Comfortable backend workflow

The admin app uses Rails 8.1, PostgreSQL, Hotwire, Stimulus, Turbo, Tailwind, and importmap. It manages sites, content, previews, translations, exports, and integrations.

The MVP keeps creative power close to the template.

The first version should avoid building an Elementor clone too early. Instead, it should prove the core loop: choose a template, fill structured content, preview instantly, optimize assets, and deploy a static site.

Business Homepage SEO settings Global styles Hero section Services block Team block Gallery Contact form Publish

Live responsive preview

Reliable websites for local companies.

Editors update content while the layout stays clean, responsive, and exportable.

Template and AI plan Static export plan

Core decisions for version one.

These are the recommended product and architecture choices based on your answers.

Recommended rendering model

Use Rails to store and manage content, then render templates through a server-side static renderer. Templates should be file-based bundles with HTML/Liquid-like placeholders, a schema file for editable fields and variables, CSS, optional JS, and metadata.

  • Fast live preview from the same renderer used for export.
  • Designer-friendly template files instead of database-only blobs.
  • Strict placeholder validation before publishing.

Recommended build model

Start with framework-free static output generated directly by Rails services. Avoid Astro/Vite for MVP unless a template genuinely needs a frontend build step. Add a build adapter later if advanced templates require it.

  • Lower maintenance burden for the first product.
  • Easier auditing of exported HTML for SEO and security.
  • Less magic for designers creating templates.