OurBigBook Docs
Browser URLs use
/-/ to separate a user or article ID from page actions:- global pages:
/-/users,/-/articles,/-/files - user pages:
/username/-/articles,/username/-/files,/username/-/settings - article pages:
/username/my/article/-/discussions,/username/my/article/-/edit - individual discussions:
/username/my/article/-/discussion/1
For the user's home article, discussions and comments use
/username/-/home/discussions and /username/-/home/comments. This distinguishes them from /username/-/discussions and /username/-/comments, which list content authored by that user. The previous /username/-/article/discussions and /username/-/article/comments URLs permanently redirect to these home article URLs.The
- path component is a reserved ID in both article IDs and uploaded file paths, to prevent ambiguity. go remains a reserved username. Old /go/ URLs permanently redirect to their new locations, preserving query parameters. Ordinary article URLs and /api routes keep their existing forms.File URLs use the same namespace on static websites and OurBigBook Web:Static runtime assets and the standalone editor use the
/-/file/path: file preview page; on web,/username/-/file/path/-/raw/path: original file bytes; on web,/username/-/raw/path/-/dir/path: directory listing; on web,/username/-/dir/path
/-/obb/ directory. Static file preview pages retain their usual .html extension when enabled. Temporary element anchors use #-/1, #-/2 and so on. Named page anchors use the same namespace: #-/toc, #-/ancestors, #-/incoming-links, #-/synonyms, #-/tagged, #-/comments, #-/comment-1, and #-/metadata.The web migration
21000101000041-reserved-path-namespace.js updates stored file article IDs, references, cached AST paths and local profile image URLs. It preserves uploaded bytes, storage paths, source text and rendered HTML. It runs through the normal deployment migration setup; locally, run cd web && ./bin/sync-db.js. Legacy web /_file/, /_raw/ and /_dir/ URLs redirect permanently to the new paths.After migrating, rerender articles, discussions and comments to regenerate their links and anchors from source:See web/bin/rerender-articles.js for rerender options. Named anchors and comment scopes need no database transformation;
web/bin/rerender-articles.js
web/bin/rerender-issues.js
web/bin/rerender-comments.js21000101000042-named-anchor-namespace.js is retained as a no-op for migration history compatibility.Regenerate static websites with the updated OurBigBook CLI and
--force-render to publish the new paths and temporary anchors. If you keep .bigb sources under _file/, move that source directory to the -/file/ directory before rebuilding. The CLI invalidates cached legacy file IDs automatically, and existing \x[_file/path] source references still resolve. Old static URLs require redirects configured on the host if they must remain available.