fix(docs): build-time plugin count on the docs index
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Read src/contents/docs/index.mdx and src/components/content/PluginCount.vue, then trace fetchTotalPluginsCount() before adding the Astro component named in the issue. Build the docs and inspect dist/client/docs/index.html; done means it contains the real plugin count and the /docs Markdown no longer contains 0+.
Written by the indexing model from the issue text.
Description
Part of the Markdown for Agents Phase 1 epic (see #5652). kestra.io has Cloudflare Markdown for Agents enabled: Accept: text/markdown converts the SSR HTML at the edge, so defects in the HTML end up in what AI agents read. Cloudflare strips nav/header/footer/scripts/styles/inline SVG, ignores aria-hidden and empty alt, keeps .visually-hidden text and display:none content, and renders <dl> as separate lines (all verified on production).
Problem
src/contents/docs/index.mdx uses <PluginCount client:idle /> (src/components/content/PluginCount.vue), whose usePluginsCount() starts at 0+ and fetches on the client. SSR ships <span>0+</span>, so /docs reads "Thanks to 0+ plugins" in HTML and in the converted Markdown. Not covered by #5446, which fixed /enterprise and /1-0.
Scope
- Add
src/components/content/PluginCount.astrothat awaitsfetchTotalPluginsCount()and renders the formatted value; use it fromindex.mdx(Astro components work in MDX). - Delete
PluginCount.vueandsrc/composables/usePluginsCount.tsin the same PR.index.mdxis the only consumer of the component, and the component is the only consumer of the composable (verified by grep on 2026-09-20); there are nosubgroupscallers.
Done when
dist/client/docs/index.htmlcontains the real count; no0+in/docsMarkdown.
- Dominant language
- Astro
- Stars
- 155
- Forks
- 177
- Avg merge
- 23h 17m
- Merged PRs (30d)
- 191
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from kestra-io/docs
-
area/devops area/qa kind/cooldown kind/performance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/frontend kind/website
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area/docs area/frontend kind/website
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
area/frontend kind/website
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area/frontend kind/website
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100