This PR removes content/blog/two-rule-sets-one-table/ (post and images) and leaves a redirect at the old URL.
The redirect
static/two-rule-sets-one-table/index.html is a small HTML page with a meta refresh to the new location, a rel="canonical" to the same, and noindex. Gatsby copies static/ to the root of public/, so the file is published at /two-rule-sets-one-table/index.html and served for /two-rule-sets-one-table/ - the same directory-index behaviour the removed Gatsby page relied on, so no server configuration is needed.
A static page is a client-side redirect rather than a 301. If the host can emit a server-side redirect for that path, that would be preferable for search engines; the canonical link covers the intent in the meantime.
Ordering
The docs PR should merge before or with this one, so the redirect target exists when the old URL starts pointing at it.
## What
Moves the **One Table, Two Rule Sets** post off the website and onto the docs site, as a page in the new Developer Guide section:
- new location: https://docs.datacontroller.io/developer-guide/two-rule-sets-one-table/
- docs PR: https://git.datacontroller.io/dc/docs.datacontroller.io/pulls/16
This PR removes `content/blog/two-rule-sets-one-table/` (post and images) and leaves a redirect at the old URL.
## The redirect
`static/two-rule-sets-one-table/index.html` is a small HTML page with a `meta refresh` to the new location, a `rel="canonical"` to the same, and `noindex`. Gatsby copies `static/` to the root of `public/`, so the file is published at `/two-rule-sets-one-table/index.html` and served for `/two-rule-sets-one-table/` - the same directory-index behaviour the removed Gatsby page relied on, so no server configuration is needed.
A static page is a client-side redirect rather than a 301. If the host can emit a server-side redirect for that path, that would be preferable for search engines; the canonical link covers the intent in the meantime.
## Ordering
The docs PR should merge before or with this one, so the redirect target exists when the old URL starts pointing at it.
The post has moved to the docs site as a Developer Guide page:
https://docs.datacontroller.io/developer-guide/two-rule-sets-one-table/
- content/blog/two-rule-sets-one-table/ is removed (the images moved to the
docs repo, where the page now lives).
- static/two-rule-sets-one-table/index.html keeps the old URL working with a
client-side redirect to the new page, plus a canonical link and noindex.
A static file at that path is served the same way the removed Gatsby page
was (both are index.html under a directory).
allan
merged commit db969f51b4 into main2026-10-15 16:26:50 +00:00
allan
deleted branch site/redirect-two-rule-sets2026-10-15 16:26:50 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Moves the One Table, Two Rule Sets post off the website and onto the docs site, as a page in the new Developer Guide section:
This PR removes
content/blog/two-rule-sets-one-table/(post and images) and leaves a redirect at the old URL.The redirect
static/two-rule-sets-one-table/index.htmlis a small HTML page with ameta refreshto the new location, arel="canonical"to the same, andnoindex. Gatsby copiesstatic/to the root ofpublic/, so the file is published at/two-rule-sets-one-table/index.htmland served for/two-rule-sets-one-table/- the same directory-index behaviour the removed Gatsby page relied on, so no server configuration is needed.A static page is a client-side redirect rather than a 301. If the host can emit a server-side redirect for that path, that would be preferable for search engines; the canonical link covers the intent in the meantime.
Ordering
The docs PR should merge before or with this one, so the redirect target exists when the old URL starts pointing at it.