Documentation links should be generated

[cdcabrera]

Description

Recent updates to PF org documentation has busted the link references. They should be generated to avoid having to intermittently updated AND until an API is available

Acceptance criteria

• Create a short term fix (potentially integrates with a long term fallback) that resolves the current link issue

• Create Review a solution to generate links

• Review API integration from https://github.com/patternfly/patternfly-doc-core

  • JSON structure optimization
  • PF versions, what would it require
  • Expanding towards PatternFly org repo, currently only pointed at PF React and PF repos

Assumptions and questions

• related to Review integration with the PF AI tooling documentation #49 Add design tokens support for lookup/validation #114

• working under the premise that documentation should not be directly stored in the server and instead be generated either on release, an api, or carried in through resources

  • we may still have to make an allowance for fallbacks, resource limits, etc... it's becoming apparent it would be a little funny to hit a resource cutoff and the model starts flailing ... NPMs could be considered, at the least it would offset package size and maintenance. And there may be other use-cases yet to present for having an "offline mode"

• need to start considerations for multiple PatternFly versions. The API currently only provides v6.

---

Jira Issue: PF-3128