# Existing Project Use this path when the documentation should live next to your code, in the repository you already have open. ## Create from the tool window 1. Open the "Codocation" tool window. 2. Click "Create Documentation". 3. Fill in the documentation title, the site id, the type ("Docs" or "Blog"), and optionally a description, then confirm. The files are created in your project root, and the tool window switches to the new navigation tree. Nothing else in your project is touched: Codocation adds `codocation.yml`, the locale-owned `content//` directory, root `definitions/`, and the global `assets/media/`, `assets/fonts/`, `assets/css/`, and `assets/js/` namespaces as needed. Root `locales` is the canonical catalog of codes, order, and Titles; `sites..locales` records which variants this site publishes, and `sites..defaultLocale` owns its unprefixed routes and content fallback. Pages, images, attachments, site trees, sidecars, and translated definition payloads belong to the declared locale/site pairs. ## More than one site A project can host several documentations: for example, a docs site and a blog side by side, or separate manuals for separate products. Run "Create Documentation" again to add another site; each gets its own site id, locale trees and site files, and entry in `codocation.yml`. The "Codocation" tool window switches between sites, and build, export, and deploy act on the selected one. ## Existing locales and Free/Pro installation Every Create Documentation path, including an additional site, shows locale controls. Free creates the site's initial default locale and exposes only that effective default to ordinary IDE build, validation, and preview. Manage Locales remains available in Free for renaming, changing the default, and removing existing locales. Pro enables adding locale memberships and processing every declared membership in the IDE. A pair tree or sidecar is valid only when the locale is declared for that site; unknown locale directories and undeclared pairs are reported as ERROR and ignored. A pre-existing multi-locale project remains readable without Pro, and its existing locale catalog remains fully manageable. Ordinary Free IDE operations process only each site's effective default; the CLI continues to process the complete multilingual site. Free does not rewrite or remove locale data automatically. A repository installation of Pro resolves its mandatory Free dependency. Installing a local Pro ZIP requires Free to be installed already or discoverable from a configured repository.