OCG is intended to run inside the repository that already owns your ontology. Install the `ontology-companion-generator` package; you do not need to clone or branch the OCG repository, and you do not need to move your source files into source/.

Recommended workflow:
1. Keep your ontology in its existing repository location using one of the supported formats: Turtle (.ttl/.turtle), RDF/XML (.rdf/.rdfxml/.owl), JSON-LD (.jsonld), or N-Triples (.nt/.ntriples).
2. Use Node.js 24.x. Run `npm install --save-dev ontology-companion-generator`, then initialize the project with `npx ocg init --ontology path/to/ontology.ttl`. The command creates the config, schema, workflow, and OCG npm scripts.
3. Update `ocg.config.json` so the source paths, ontology format override, project metadata, feature toggles, hero text, theme, and featured terms match your ontology. Set `sources.ontologyFormat` to `turtle`, `rdfxml`, `jsonld`, or `ntriples` when auto-detection is not appropriate. If `curation.featuredTerms` is empty, OCG selects terms automatically; leave `curation.viewerTabs` empty to show every configured source asset. OCG does not scan arbitrary directories, so add extra files under `sources.artifacts`. Config, schema, workflow, and guide files are not included in the raw viewer. Set `features.specPage` to true to publish the ReSpec document at `spec/index.html`. Optionally set `site.branding.headerImage` to a repository-relative `.png`, `.jpg`, `.jpeg`, `.webp`, `.gif`, or `.svg` to replace the header abbreviation square, and `site.branding.favicon` to a `.ico`, `.png`, or `.svg` browser favicon. Set the twelve `theme.colors` tokens to change the site-wide palette; use hex or `rgb(...)` values for reliable graph highlights. Use `graph.colors` separately for ontology node and relationship semantics.
   For an optional high-level ontology overview above `Classes` on the Reference page, set `features.hierarchyOverview` to true and customize the `hierarchy` block. OCG summarizes selected `subClassOf`/`broader` branches and capped domain/range links rather than rendering the whole ontology; use `rootTerms`, `maxDepth`, `maxChildrenPerNode`, and `maxNodes` to control scope.
4. Run `npm run ocg:check`, then `npm run ocg:build` from the repository root. The build vendors the Sigma.js and Graphology browser bundles into `site/assets/vendor/`.
5. Configure GitHub Pages to use GitHub Actions and push the ontology repository's `main` branch. Feature branches should be validated locally or with build-only CI rather than deployed to the live Pages site.

The OCG repository also contains a complete forkable example, but installing the package into your existing ontology repository is the recommended workflow.