Introducing a new way to review your PRs.

Read the announcement

opencut-app / opencut

The open-source CapCut alternative

View on GitHub

12 documents · Updated Nov 16, 2026

docs / brand-and-changelog

Brand assets and changelog organization

Coverage: brand/**, changelog/**, LICENSE

Overview

This area holds non-runtime project identity and release-note assets. brand/marks/ contains checked-in SVG brand marks: full wordmarks in brand/…/logo-dark.svg and brand/…/logo-light.svg, standalone symbols in brand/…/symbol-dark.svg and brand/…/symbol-light.svg, and a rounded app icon in brand/…/icon.svg. The dark/light filenames describe the intended background treatment through the mark fill color: the *-dark.svg wordmark and symbol use black mark paths, while the *-light.svg versions use white mark paths. brand/…/icon.svg is different from the monochrome marks: it is a 512×512 rounded-square icon with pastel radial-gradient background fills and a black OpenCut symbol in front.

Release notes are organized as one markdown file per version in changelog/. The files are data-first markdown documents whose content is YAML front matter bounded by ---; there is no prose body after the front matter in changelog/0.1.0.md, changelog/0.2.0.md, or changelog/0.3.0.md. Each release entry records version, date, published, title, description, summary, and a changes array. Each item in changes has a type such as new, improved, fixed, or technical, plus a user-facing text string. The sequence currently tracks published releases from 0.1.0 on 2026-02-23 through 0.3.0 on 2026-04-15, with later files carrying longer technical migration notes alongside product-facing changes.

LICENSE is the root project license notice for OpenCut. It grants MIT-style permission to use, copy, modify, merge, publish, distribute, sublicense, and sell the software, requires preserving the copyright and permission notice, and disclaims warranties and liability. Because it sits at the repository root rather than under brand/ or changelog/, it is the legal identity document that applies across these checked-in assets as part of the repository contents.

Coupling

  • If adding or renaming brand marks under brand/marks/, keep the light/dark naming semantics consistent with the existing SVG fills in brand/…/logo-dark.svg, brand/…/logo-light.svg, brand/…/symbol-dark.svg, and brand/…/symbol-light.svg; callers or download pages can infer contrast behavior from the filename without inspecting path colors.
  • If a changelog file is added under changelog/, follow the existing front-matter schema used by changelog/0.1.0.md, changelog/0.2.0.md, and changelog/0.3.0.md: version metadata plus a changes list of { type, text } entries. A missing closing --- or a body-style rewrite would break consumers that expect these files to parse as structured release metadata.
  • If release-note categories change, update all changelog consumers to understand the new changes[].type values; current data already uses new, improved, fixed, and technical, with technical appearing in changelog/0.3.0.md for migration and architecture notes.
  • If redistributing brand SVGs or changelog text outside the repository, preserve the root notice from LICENSE; its permission grant is conditioned on including the copyright and permission notice in copies or substantial portions of the software.

Risks

  • changelog/0.2.0.md contains the public release-note text Entirely new efects system. with a spelling error in efects; if the changelog is rendered directly from this data, the typo will appear in published release notes unless corrected in the source file.