[ReenigneArcher]

Description

The organization profile still describes the Themerr repository transfers and website as upcoming. Update both READMEs to describe the current repositories, keep the archived integrations clearly marked, and link to the live product page, database, releases, and documentation.

Match LizardByte's centered logo, title, and subtitle heading style using the existing Themerr logo. Add a centered footer below a divider: “A [LizardByte logo and wordmark] project,” followed by “Explore Projects · Get Support.” Consolidate the profile's community links into this footer and align the repository table's Markdown pipes.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

• Confirmed the four repository owners and active/archived status through GitHub's API.
• Checked the logo, product page, database, documentation, and releases URLs; all returned HTTP 200.
• Verified both heading layouts, removal of future-migration copy, and aligned table pipe positions.
• Rendered both READMEs through GitHub's GFM API and verified the divider, centered footer, inline 132 × 32 logo-and-wordmark alignment, attribution, and project/support links. The horizontal brand asset returned HTTP 200.
• Verified that rendered logo links contain only the image, with surrounding spacing outside the link to prevent stray underlines.
• Checked both rendered footers in Chrome using GitHub's current stylesheets, in light/dark themes at 320px and 760px. The wordmark is raised into line with the surrounding text and neither layout overflows.
• git diff --check passed.
• Documentation-only change; no application tests were added or needed.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

• AI tools were used while preparing this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud