Content Architecture
wakalab.dev is the canonical Wakalab site. markdown-renderer.wakalab.dev is the Markdown Renderer for GitHub (GFMR) Live Lab: a place to run and inspect the product, not a second seller-wide site.
Ownership
| Content | Canonical owner | Lab treatment |
|---|---|---|
| Company information | Wakalab | Do not duplicate. Link to Wakalab when needed. |
| Shared Privacy, Terms, refund policy and Japanese SCTA notice | Wakalab Legal | Link to the canonical policy; do not publish a conflicting policy. |
| Product catalogue, sales page, price and license scope | Wakalab | Link to the product page or checkout. |
| Official documentation, roadmap and changelog | Wakalab | Link to the canonical page; a short release notice may summarize one release. |
| GFMR rendering examples, benchmarks, debugging and implementation notes | GFMR Live Lab | Canonical on the Lab when the page is a real, rendered product demonstration. |
| GFMR release news | Wakalab changelog | Lab posts are short notices and link to the canonical changelog. |
This makes the shared legal pages and the 30-day refund policy apply to every paid Wakalab product. A product-specific exception must be decided in an issue before sale, then reflected consistently in the product page, checkout, FAQ and legal material.
Publishing rules
- Publish company-wide announcements, long-lived product explanations and cross-product engineering posts on Wakalab.
- Publish only GFMR-specific rendered samples, validation reports, performance measurements and debugging notes on the Live Lab.
- Never publish the same full article on both sites. The secondary site uses a short summary with a link to the canonical page.
- A Lab page must not present itself as the authoritative source for seller-wide prices, licenses, legal terms or refunds.
- New product pages use the Product Launch Template.
URL migration policy
The implementation owner of the WordPress site maintains the following map before changing a URL. Do not delete a page merely to remove duplication: choose the response that preserves the intended visitor and search-engine behavior.
| Existing Lab URL | Wakalab canonical URL | Required treatment |
|---|---|---|
/legal/ | /legal/ | 301 after confirming the Lab page has no unique content. |
/pricing/ | /products/markdown-renderer-for-github/pro | 301. |
/license/ | /products/markdown-renderer-for-github/pro and /legal/terms-of-service | 301 to the product page; retain only a short Lab explanation if it is genuinely GFMR-specific. |
/documentation/ | /products/markdown-renderer-for-github/ | 301 or a noindex summary page that links to the canonical docs. |
/roadmap/ | /products/markdown-renderer-for-github/roadmap | 301. |
/markdown-renderer-for-github/roadmap/ | /products/markdown-renderer-for-github/roadmap | 301. |
/changelog/ | /products/markdown-renderer-for-github/changelog | 301; short release news remains indexable only when it has distinct content. |
/markdown-renderer/ | /products/markdown-renderer-for-github/ | 301. |
/examples/ | — | Keep on the Lab with a self-canonical URL when it is a working demonstration. |
For pages kept on the Lab, use a self-canonical URL only when their content is distinct. Use noindex,follow for navigational summaries that must remain available but add no search value. Do not use canonical as a substitute for a redirect when the old and new pages are substantively the same.
Migration verification
Before release, verify both language variants where they exist:
curl -sSI https://markdown-renderer.wakalab.dev/pricing/
curl -sSI https://wakalab.dev/products/markdown-renderer-for-github/proConfirm the old response is a single-hop 301, the destination is 200, and the destination's canonical and hreflang point to its Wakalab URL. Remove migrated URLs from the WordPress sitemap, submit the updated sitemap in Search Console, then check Coverage, Page indexing and URL Inspection after 7, 28 and 90 days. Run the tools/wp-abilities live head audit against any Lab URL before and after the change.
Release-content ownership
- The GFMR repository's release data is the source for version and change facts.
- Wakalab renders that data as the public roadmap and changelog. The release-sync workflow opens a reviewable Wakalab PR.
- The Lab may receive a short release news item that links to the relevant Wakalab product, roadmap and changelog pages. It must not mirror the full changelog.
See Issue #139, #140, #141, #142 and #144.