Folio CMS

Open-source Rails CMS for content platforms that need editorial comfort, custom workflows and an architecture ready for years of development.

🌐Web Applications

Folio is an open-source Rails CMS for teams that need to manage content, media, roles and custom workflows in one system. Editors get a focused admin. CTOs get an open architecture that can be developed for years without replacing the platform.

Admin for everyday work

Pages, content blocks, the Tiptap editor, media library, roles and publishing are ready as a foundation that we adapt to the way a specific team works.

For leadership, that means a faster launch and fewer operational bottlenecks. For editors, less waiting for developers. For product teams, one system that can grow with the project.

What Folio solves for decision makers

Faster start. Admin, authentication, media library, pages and publishing are not rebuilt from scratch on every project. Budget can move sooner into features that make your product different.

One system for content and operations. Multi-site, localization, menus, sitemap, files and internal roles stay together instead of spreading everyday work across disconnected tools.

Technical continuity. Folio is built on Rails and open-source code on GitHub. The client has access to the code, documentation and a clear path for further development.

What CTOs and development teams get

Folio is a standard Rails engine, not a closed SaaS layer. The project remains a regular Rails application: custom models, controllers, ViewComponent rendering, Stimulus behavior, tests, background jobs and integrations.

Content is built from atoms and Tiptap blocks. Media runs through File and FilePlacement. Localization uses Traco and localized fields. Extensions are handled through generators and app/overrides, so the project can adapt Folio without forking the engine.

Real code from this website

Folio features are composed in Rails models through regular concerns. This is a shortened example from the project/reference model on sinfin.digital.

app/models/sinfin_digital/project.rb

Ruby

1234567891011121314

class SinfinDigital::Project < ApplicationRecord
  include Folio::Tiptap::Model
  include Folio::Publishable::Basic
  include Folio::BelongsToSite
  include Folio::FriendlyIdForTraco
  include Folio::HasAttachments
  include Folio::Sitemap::Base
  include Folio::Audited::Model

  audited console: true

  has_folio_tiptap_content(:tiptap_content, locales: %i[cs en])
  translates :title, :perex, :slug, :url, :tiptap_content
end

When Folio fits

Folio fits when a website is more than a set of static pages. Typical cases include editorial systems, content platforms, multilingual product websites, client portals, catalogs, media libraries, internal roles, SEO requirements, integrations and long-term development.

For a simple brochure website, Folio can be more foundation than the project needs. It works best when the product will grow and gradually connect to more data, services or internal workflows.

Where Folio runs

An open foundation you can inspect

We develop Folio as an open-source Rails engine. Review the repository, documentation and architecture. In a collaboration, we show the actual admin, content blocks and how Folio would fit your project.

Folio on GitHub → github.com/sinfin/folio

How to Set Up MCP Server in Folio and Cursor