Goal: Transform the Portal into a comprehensive "Knowledge Hub" by mirroring selected GitHub tickets as indexable content. This strategy aims to capture long-tail SEO traffic (specific error messages/solutions), provide structured training data for AI, and demonstrate project velocity.
Strategic Value: "Own Your Knowledge". By hosting ticket content on neomjs.com, we create a coherent internal knowledge graph (Release Notes -> Ticket -> Docs) that is superior to disparate GitHub pages for both Googlebot and LLMs.
Key Objectives:
-
Data Pipeline (buildScripts/createTicketIndex.mjs):
- Parse
.github/ISSUE_ARCHIVE/ to generate a tickets.json index.
- Crucial Filter: Exclude noise. Only index tickets with high-value labels (e.g.,
bug, feature, enhancement, documentation). Exclude chore, task, agent-task.
- Structure the index for efficient loading (potentially paginated or grouped by Year/Milestone).
-
UI Implementation:
- Add a "Tickets" tab to the
NewsTabContainer in the Portal.
- Reuse the
apps/portal/view/shared/content/ architecture (TreeList + Markdown View) to display the tickets.
- Read-Only Design: Clearly position this as an archive/knowledge base. Include a prominent "View Discussion on GitHub" link for interaction.
-
Content Rendering:
- Leverage recent
Neo.component.Markdown enhancements (implicit readonly code blocks, automatic ticket linking) to render ticket bodies faithfully.
- Ensure ticket references (e.g.,
#123) within these pages link to the internal portal ticket page, keeping the user on-domain.
-
Integration:
- Add the new section to the Sitemap and
llms.txt generation scripts.
- Update Release Notes generation to optionally prefer internal ticket links over external GitHub links.
Goal: Transform the Portal into a comprehensive "Knowledge Hub" by mirroring selected GitHub tickets as indexable content. This strategy aims to capture long-tail SEO traffic (specific error messages/solutions), provide structured training data for AI, and demonstrate project velocity.
Strategic Value: "Own Your Knowledge". By hosting ticket content on
neomjs.com, we create a coherent internal knowledge graph (Release Notes -> Ticket -> Docs) that is superior to disparate GitHub pages for both Googlebot and LLMs.Key Objectives:
Data Pipeline (
buildScripts/createTicketIndex.mjs):.github/ISSUE_ARCHIVE/to generate atickets.jsonindex.bug,feature,enhancement,documentation). Excludechore,task,agent-task.UI Implementation:
NewsTabContainerin the Portal.apps/portal/view/shared/content/architecture (TreeList + Markdown View) to display the tickets.Content Rendering:
Neo.component.Markdownenhancements (implicit readonly code blocks, automatic ticket linking) to render ticket bodies faithfully.#123) within these pages link to the internal portal ticket page, keeping the user on-domain.Integration:
llms.txtgeneration scripts.