feat: switch Ragmir CLI to rgr and refresh landing#53
Merged
Conversation
Move the public domain to ragmir.com and rebuild the landing around a sectioned architecture: - domain: wrangler routes and deploy URLs target ragmir.com (primary) and www.ragmir.com, drop ragmir.jcode.works from production routes (kept only for staging); astro.config and README links follow - landing: split the single page into reusable section components (hero, use-cases, privacy, strengths, agents, desktop, faq, closing-cta, footer) with a new logo, navbar, command-copy block and library section - hero: rewrite the value proposition, shrink the title and description typography, add an accessible scroll-to-next-section button, and rework the terminal demo (play-once animation, tone-based output coloring, narrative grounded in a gitignored cahier des charges) - i18n: align EN/FR copy across hero, demo and use-cases around the three indexed source types (confidential documents, repository files, docs) - seo: add llms.txt, ai.txt, IndexNow key and submit script, dynamic robots.txt, and structured-data organization/software/faq schema
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Expose rgr and rgr-tts as the public command names. Keep ragmir, kb, and ragmir-tts as deprecated compatibility bins. Those aliases warn users to migrate to the new commands. Add deterministic prompt routing through rgr route-prompt and MCP ragmir_route_prompt.
Add the build-time npm downloads counter. Refine the hero and use-case copy in both locales. Keep product branding as Ragmir while command examples use rgr. Move local Astro dev and preview to dedicated ports.
Update the canonical README, package READMEs, skills, and references. Document the rgr command migration and deprecated compatibility bins. Cover prompt routing, configuration, and the ragmir.com landing release path.
jb-thery
force-pushed
the
feature/landing-ragmir-domain
branch
from
dcbec3c to
edc7e08
Compare
Parse the configured landing URL and compare the hostname exactly. This prevents ragmir.com-prefixed arbitrary hosts from receiving production robots rules.
|
🎉 This PR is included in version 2.4.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
2 participants
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.
Summary
rgr/rgr-ttswhile keepingragmir,kb, andragmir-ttsas deprecated compatibility bins with migration warnings.rgr route-promptand MCPragmir_route_prompt.ragmir.comproduction positioning.Validation
pnpm validategit diff --checkdcbec3c8094b0fbc8c1e294c53d6f7acd0fd3ce4Release Notes
Users should migrate commands from
ragmir ...torgr .... Existingragmirandkbbins remain available as deprecated compatibility aliases and print a warning that points users torgr. The TTS command follows the same pattern: usergr-tts;ragmir-ttsremains as a deprecated compatibility alias.