django-camomilla-cms 6.5.0

Django powered cms

Our beloved Django CMS

⭐️ Features

• 🧘‍♀️  Built on top of the django framework
• 🥨  Beaked page abstract model to let you manage everything you need as a page.
• 🏞️  Optimized media management with autoresize
• 👯  Enable relations inside django JSONFields
• ⚡️  AutoCreate api endpoints from models
• 🚧  Enable JsonSchema directly in models endpoints

Camomilla is a Django CMS that allows you to create and manage your website's content with ease. It provides a simple and intuitive interface for managing pages, media, and other content types. Camomilla is built on top of the Django framework, which means it inherits all the features and benefits of Django framework. We try to continuously improve Camomilla by adding new features and fixing bugs. You can check the CHANGELOG to see what has been added in the latest releases.

📦 Quick Start

Here you can find some quick setup instructions to get started with Camomilla. For more detailed information, please refer to the documentation.

[!TIP]

Env Virtualization 👾

Use a virtualenv to isolate your project's dependencies from the system's python installation before starting. Check out virtualenvwrapper for more information.

Install django-camomilla-cms and django from pip

$ pip install django
$ pip install django-camomilla-cms>=6.0.0

Create a new django project

$ django-admin startproject <project_name>
$ cd <project_name>

Create a dedicated folder for camomilla migrations

$ mkdir -p camomilla_migrations
$ touch camomilla_migrations.__init__.py

Create migrations and prepare the database

$ python manage.py makemigrations camomilla
$ python manage.py migrate

Add camomilla and camomilla dependencies to your project's INSTALLED_APPS

# <project_name>/settings.py

INSTALLED_APPS = [
    ...
    'camomilla', # always needed
    'camomilla.theme', # needed to customize admin interface
    'djsuperadmin', # needed if you whant to use djsuperadmin for contents
    'modeltranslation', # needed if your website is multilanguage (can be added later)
    'rest_framework',  # always needed
    'rest_framework.authtoken',  # always needed
    ...
]

Run the server

$ python manage.py runserver

🤖 AI-readable docs (llms.txt / MCP)

The documentation site is built with VitePress and ships machine-readable bundles for AI tools, generated automatically on every docs build:

• llms.txt — a curated index of the docs (camomillacms.github.io/camomilla-core/llms.txt)
• llms-full.txt — the entire documentation concatenated into one file (…/llms-full.txt)

Point any llms.txt-aware tool (Claude Code, Cursor, Windsurf, …) at those URLs. To expose the docs to an MCP client, run the community mcpdoc server against the hosted llms.txt — no extra hosting required:

uvx --from mcpdoc mcpdoc --urls "Camomilla:https://camomillacms.github.io/camomilla-core/llms.txt" --transport stdio

Working on camomilla with Claude Code? The repo also ships two skills under .claude/skills/ — camomilla-usage (building on top of camomilla) and camomilla-internal-architecture (editing camomilla's source). They load automatically; no MCP needed.

🧑‍💻 How to Contribute

We welcome contributions to Camomilla! If you want to contribute, please read our contributing guide for more information on how to get started.

🚀 Local Development (uv)

We use uv for fast dependency management and isolated environments.

1. Install uv (one time): macOS / Linux:

   curl -LsSf https://astral.sh/uv/install.sh | sh
   

   Homebrew:

   brew install uv
   

2. Create a new venv inside the project (one time):

   uv venv
   source .venv/bin/activate
   

3. Sync dependencies (runtime + dev):

   make install
   

4. Run tests:

   make test
   

5. Format & lint:

   make format lint
   

🤖 AI-assisted contributing (bring your own agent)

Camomilla ships a tool-agnostic agent setup so you can contribute with whatever AI coding assistant you prefer. The single source of truth is AGENTS.md at the repo root — the cross-editor standard that Cursor, OpenAI Codex, Aider, Gemini CLI, GitHub Copilot, Zed and others read automatically. It carries the dev commands, conventions, repository map, a "gotchas" section, and pointers to the deep references.

Per-tool entry points are thin adapters that defer to AGENTS.md (no duplicated, drift-prone instructions):

Tool	Reads	Notes
Most agents (Cursor, Codex, Aider, Gemini CLI, Zed, …)	AGENTS.md	Auto-detected; nothing to configure.
Claude Code	CLAUDE.md → imports AGENTS.md	Also auto-loads two skills under .claude/skills/ (camomilla-usage, camomilla-internal-architecture).
GitHub Copilot	.github/copilot-instructions.md → points to AGENTS.md	Recent Copilot reads AGENTS.md natively too.

The two deep references under .claude/skills/ are plain Markdown — open them with any agent or editor, not just Claude: camomilla-usage/SKILL.md (building on top of camomilla) and camomilla-internal-architecture/SKILL.md (editing camomilla's source). The published docs also expose an llms.txt for AI ingestion.

Using a tool that needs an explicit instructions path? Point it at AGENTS.md.