Repo context. accensa-app is the off-chain half of Accensa — the merchant back-office for x402 sellers on Stellar. This issue concerns apps/docs, the Docusaurus 3.10 documentation site published to https://accensa.github.io/accensa-app/. It documents all three Accensa repositories, so a defect here is the first thing a new integrator sees.
🟢 Unblocked. Small configuration cleanup; decide the intent first.
Problem
apps/docs/docusaurus.config.ts configures the blog preset in detail:
blog: {
showReadingTime: true,
feedOptions: { type: ['rss', 'atom'], xslt: true },
editUrl: 'https://github.com/accensa/accensa-app/tree/main/apps/docs/',
onInlineTags: 'warn',
onInlineAuthors: 'warn',
onUntruncatedBlogPosts: 'warn',
},
There is no apps/docs/blog/ directory. The plugin is fully configured for a blog that does not exist — so the build generates empty RSS and Atom feeds, and a /blog route with no content.
Empty feeds are the real cost: they are discoverable, and a reader who subscribes gets a feed that will never deliver anything, with no indication it was never intended to.
What to build
Decide whether Accensa wants a blog, then make the config say so.
- If no blog is planned: disable the preset (
blog: false) and confirm the /blog route and both feeds disappear from the build output.
- If a blog is planned: keep the configuration and add a first post, so the feeds are not empty. Do not leave it configured-but-absent, which is the current state and the actual problem.
- Check the navbar and footer for links to
/blog either way.
Ask in the community channels before choosing — this is a product question, not a technical one, and guessing wrong means the work is reverted.
Out of scope: writing blog content beyond a single placeholder post, if that path is chosen.
Acceptance criteria
Contact & Support
Problem
apps/docs/docusaurus.config.tsconfigures the blog preset in detail:There is no
apps/docs/blog/directory. The plugin is fully configured for a blog that does not exist — so the build generates empty RSS and Atom feeds, and a/blogroute with no content.Empty feeds are the real cost: they are discoverable, and a reader who subscribes gets a feed that will never deliver anything, with no indication it was never intended to.
What to build
Decide whether Accensa wants a blog, then make the config say so.
blog: false) and confirm the/blogroute and both feeds disappear from the build output./blogeither way.Ask in the community channels before choosing — this is a product question, not a technical one, and guessing wrong means the work is reverted.
Out of scope: writing blog content beyond a single placeholder post, if that path is chosen.
Acceptance criteria
/blogroute and no feed files appear inapps/docs/build.pnpm buildsucceeds forapps/docs(onBrokenLinksis set tothrow, so a broken link fails the build).pnpm typecheckpasses inapps/docs.Closes #<this issue>.Contact & Support
SUPPORT.md— contribution help, Wave process, and the full list of channels