Rename and rebrand
The addresses
| What | Where |
|---|---|
| The three host names, Let's Encrypt's contact | APP_DOMAIN, IDENTITY_DOMAIN, API_DOMAIN, ACME_EMAIL in .env |
| The application's link to the documentation | docsUrl in front/application/src/environments/environment.prod.ts |
| The landing page's links | front/landing/src/environments/environment.ts (docsUrl, demoUrl, and repositoryUrl / licenseUrl, which add the footer's links when set) |
| The landing page's canonical URL, Open Graph and JSON-LD | front/landing/src/index.html, plus front/landing/public/robots.txt and sitemap.xml |
| The documentation site's name, addresses and home page | front/docs/content/_site.json — see front/docs/README.md |
The name, the logo and the favicon
| What | Where |
|---|---|
| The product name in the application | the strings of front/application/src/assets/i18n/<lang>.json — git grep Blouppy there |
| The logo | the logo components of @blouppy/ui (front/libs/ui/src/brand/) |
| The favicon | each app's favicon.ico |
| The sign-in pages | back/Blouppy.Identity/Pages/ — the shared layout is Pages/Shared/_AuthLayout.cshtml, each page's headline in Pages/AuthHero.cs |
| The e-mails | Email__FromName (the name in each e-mail's header and copyright line), and the templates under back/Blouppy.Infrastructure.Email*/ — see E-mail |
The identity host's stylesheet is compiled from the design system's tokens and committed:
after a change to the tokens, rebuild it (cd back/Blouppy.Identity && npm ci && npm run build:css).
StylesheetTests fails while the committed file is behind.
The example content
| What | Where |
|---|---|
| The landing page | front/landing/src/app/features/ |
| The product documentation for your users | front/docs/content/ — or a folder of your own, with DOCS_CONTENT_DIR |
The marketing copy of the /pricing page | front/application/src/app/features/pricing/ (pricing.data.ts holds translation keys, never text) |
The example domain
Workspaces and teams are an example. Keep them as the base of your product, or replace
them: the tutorial shows how a domain is built, which is also how
you would take one out — its projects, its registration in AddDomainServices(), its row in
DomainBoundaryTests, its routes, its migrations.