Skip to content

docs: official branding in the READMEs; 1.3.0 is unreleased - #10

Merged
iitzSeriZdev merged 1 commit into
mainfrom
docs/v1.3.0-branding
Sep 27, 2026
Merged

iitzSeriZdev merged 1 commit into
mainfrom
docs/v1.3.0-branding

Conversation

@iitzSeriZdev

@iitzSeriZdev iitzSeriZdev commented Sep 27, 2026 •

Copy link
Copy Markdown
Owner

Official branding in the READMEs, and 1.3.0 marked as unreleased. Documentation and assets only — no application behaviour changes. No tag, no release.

Changes

  • README headers. The five READMEs open with the official Row-Template wordmark instead of the old banner. The banner showed a placeholder mark, "…page for 3X-UI" and "v1.1.0".
    • README.md, README.ar.md, README.ru.md and README.zh-CN.md use the English wordmark.
    • README.fa.md uses the Persian wordmark.
    • The wordmarks are black on a transparent background, which can't be read on GitHub's dark theme. In dark mode GitHub shows the official square logo (white on navy) instead, through <picture> with prefers-color-scheme. GitHub renders this as its own <themed-picture>, which I confirmed through GitHub's Markdown API.
  • docs/assets/branding/ holds three files:
    • row-template-wordmark-en.png and row-template-wordmark-fa.png: lossless re-encodes of the originals, pixel-identical and about 13% smaller;
    • row-template-logo.png: the square logo at 512 px.
  • CHANGELOG. 1.3.0 is marked Unreleased. The release date is added when the GitHub release is published.

The banner file itself is unchanged, because the documentation site's landing page still uses it.

Checks

  • node --test tests/panel-support.test.mjs: 9/9.
  • npm run verify: all checks passed.
  • The five READMEs still agree on code blocks, inline code, links and structure. The only difference is the intended Persian wordmark.

Not in this PR (found during the pass)

  • rebecca migrate-binary. The Rebecca refusal message in installer/panels/rebecca.sh, and the README, CHANGELOG and docs, say "Rebecca's own rebecca migrate-binary moves a Docker install to 1.x". In Rebecca's current scripts/rebecca/rebecca.sh and rebecca-binary.sh, migrate_docker_to_binary_command is defined, but dispatch_command has no migrate-binary case. The command would print the usage text instead. The installer message is application code, so it is left for a separate change. The documentation site (Web-Row-Template PR) already points to rebecca-binary.sh instead.
  • The docs-site banner (docs/assets/row-template-banner.png, used by docs/src/content/docs/index.mdx) still carries the old mark, "for 3X-UI" and "v1.1.0".

Documentation and assets only; no application behaviour changes.

- The READMEs open with the official Row-Template wordmark instead of the
  old banner (which showed a placeholder mark, "for 3X-UI" and v1.1.0).
  English, Arabic, Russian and Chinese use the English wordmark; Persian
  uses the Persian wordmark. The wordmarks are black on transparent, so
  GitHub's dark theme gets the official square logo (white on navy)
  through <picture> and prefers-color-scheme instead.
- docs/assets/branding/: the two wordmarks (lossless re-encodes of the
  originals, pixel-identical) and the square logo at 512 px.
- CHANGELOG: 1.3.0 is marked Unreleased; the date is added when the
  GitHub release is published.

The banner itself is unchanged and is still used by the documentation
site's landing page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@graphify-labs graphify-labs Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Graphify reviewed this change.

Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).


Graphify review — findings

Replaces the single banner image at the top of all five READMEs with a <picture> element that swaps in a dark-scheme logo and otherwise shows a language-appropriate wordmark (English for en/ru/zh-CN, Farsi for fa), adding the three new branding PNGs. Marks the 1.3.0 CHANGELOG entry as Unreleased instead of the 2026-09-26 date.

No blocking issues surfaced. 1 lower-confidence candidate did not survive cross-model review.

Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 121 functions depend on the 121 functions this change touches.

Health — grade A; no new coupling hotspots.

Verification — 121 functions in the blast radius were not formally verified this run (proofs are advisory here).

Gate & verification

graphify gate

PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.

Advisory (not blocking):

  • verification_scope: 121 function(s) in the blast radius were not formally verified this run

@iitzSeriZdev
iitzSeriZdev merged commit 117a951 into main Sep 27, 2026
3 checks passed
iitzSeriZdev pushed a commit that referenced this pull request Sep 27, 2026
main gained two commits that put the released date back on the 1.3.0
heading (`addd4df`, `13fb6c8`): v1.3.0 is published, tag `v1.3.0` ->
`e103f74`, and the heading had been changed to "Unreleased" by #10 after
the release. CHANGELOG.md conflicted, because this branch adds an
`## [Unreleased]` section of its own at the top of the file.

Resolved minimally: this branch's `## [Unreleased]` section (the
PasarGuard and Rebecca title fixes) stays at the top, and the 1.3.0
section keeps main's restored `## [1.3.0] - 2026-09-26` heading, so the
file matches the tagged release again. No other file conflicted and no
content was dropped from either side.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant