Repository navigation
docs(readme): add the OpenTAMS product logo - #23
Merged
Merged
Conversation
Akshay-Narayan-Pai
force-pushed
the
docs/product-logo
branch
2 times, most recently
from
September 25, 2026 13:51
d03f308 to
dc24776
Compare
Adds the product logo as docs/assets/logo.png and renders it centred at the top of README.md, in place of the "# OpenTAMS" heading. The logo carries the wordmark, so the heading was repeating it. The tagline and the badge row move up under it and are centred to match. The badges stay as Markdown inside a <div align="center">. GitHub parses Markdown inside an HTML block when a blank line separates them, so the badge list does not have to be rewritten as raw HTML to be centred. The file is a 1200x500 PNG with an opaque white background, displayed at 420px wide. The white background is deliberate: the wordmark is dark navy, so a transparent version would disappear against GitHub's dark theme. Use of the logo stays governed by the trademark section of NOTICE - the Apache-2.0 grant on this repository does not extend to it.
Akshay-Narayan-Pai
force-pushed
the
docs/product-logo
branch
from
September 25, 2026 13:53
dc24776 to
632fbaa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the product logo to the repository and makes it the top of the README.
What changed
docs/assets/logo.png— new file, the 1200x500 product logo.README.md— a centred<img>replaces the# OpenTAMSheading. The logo already carries the wordmark, so the heading was saying the name twice. The tagline moves up directly under the logo and is centred to match.Badges stay left-aligned Markdown. Centring them would mean rewriting all seven as raw HTML anchors, because GitHub does not parse Markdown inside an HTML block — not worth the maintenance cost.
The README now has no
<h1>This is a deliberate trade, not an oversight. The cost: anywhere the file is read without rendering the image —
cat README.md, a plain-text mirror, a search indexer — the document no longer states its own title. Thealttext covers screen readers and HTML contexts only.Nothing in the repository links to the
README.md#opentamsanchor (verified by grep), so no internal link breaks. External links to that anchor, if any exist, will land at the top of the page instead of at the heading.On the white background
The source file is opaque RGB with no alpha channel. That is deliberate: the wordmark is dark navy, so making the background transparent would render the lower half of the logo invisible against GitHub's dark theme. The white block reads as a card in dark mode, which is the lesser problem.
A dark-theme variant would be a
<picture>element withprefers-color-schemesources, which needs a second artwork file with a light wordmark. The file is namedlogo.pngrather thanopentams-logo.pngto leavelogo-dark.pngavailable beside it.Trademark
The logo is an Amagi mark. The trademark section of
NOTICEalready states that no rights to Amagi marks are granted under the software licence, so checking the file into an Apache-2.0 repository does not license it. No change toNOTICEis needed.