Documentation belongs in the evaluation, not only in support.
Each concept has a guide available before installation: placement, prerequisites, permissions, data, configuration, interactive walkthrough, limitations, and diagnostics.
Concept documentation
The steps describe expected behavior. They do not replace a real listing, manifest, or published installation.
Open the documentation for the product you are evaluating.
Readiness for JiraJira · Issue panel
Decide whether a release is ready without leaving the issue.Read the guidePortfolio InsightsJira · Project page
Read risks, decisions, and dependencies across the project.Read the guidePage SummaryConfluence · Content macro
Turn a dense page into readable decisions and actions.Read the guideContext LinkerConfluence · Context panel
Find related projects and decisions without leaving the page.Read the guideFour recipes to move from reading to testing.
Copy a configuration, interact with its scenario, then keep the result in your evaluation packet.
The contract for every guide.
The page should answer questions before the first support request and stay aligned with the product that is actually published.
- 01Name the host, placement, and covered versions.
- 02List prerequisites before any installation step.
- 03Justify permissions and link the data flow.
- 04Provide a minimal, verifiable configuration.
- 05Document empty states, errors, limitations, and uninstallation.
- 06Link the changelog, status, and support without dead ends.
Good documentation reduces risk before it reduces tickets.
Choose an app, follow its verification path, and record the gaps still marked as concepts.