Research and Creation of a VEDA Service Menu

[kyle-lesinger]

Summary

To improve the understanding and presentation of VEDA to stakeholders, a decision has been made to create a "VEDA Service" style menu which incorporates high level descriptions and summaries of the many different services that VEDA has to offer. To be decided on the final formatting and the location of this Menu.

TODO

• host meetings to gather information about high-level descriptions (solicit feedback from Team leads)
• send survey to narrow down the high level descriptions
• host meetings to gather information about service descriptions (solicit feedback from Team leads)
• determine User Personas and bundled services
• create initial prototype (vibe coded) which showcases the VEDA Services and the User Personas
• gather additional feedback from Team leads and others within VEDA

Documents

Initial Excel form for identifying services based on instance
VEDA-MENU.docx Initial high level summary and description
High level summary naming options
User Personas
Survey for high level descriptions - likely only accessible by Kyle who created it.

[smohiudd]

Following a discussion with @kyle-lesinger and @chelsea-aaron we've agreed to combine the current progress on the service menu with an overarching review and redesign of veda-docs. This work will involve:

Documentation Platform Evaluation

• assess if an alternative to Quarto (MKdocs, Sphinx, Jekyll site, etc.) is more appropriate for the veda-docs site - ADR required
• define evaluation criteria (Ease of contribution via GitHub, native support for Jupyter notebooks, theming, navigation, extensibility)

Review current state

• Audit existing docs, identify outdated, duplicate, or unused content
• Analyze usage patterns, what pages are most/least visited
• Common entry points (landing pages, search, external links)
• Gather qualitative feedback from users

Doc Redesign

• Propose a new documentation hierarchy based on user personas
• Evaluate and integrate service menu into the new structure