The live demo runs a sample point-of-sale product, Retail POS, through Veliose. It has its own code repository, Jira project and WordPress help site, all filled with sample data.
What the demo is
Retail POS stands in for a team’s product. Its WordPress site plays the team’s own help center, on a site of its own: Veliose publishes into it the way it would into any team’s existing site. The internal version of each release note goes to a Confluence space, which stays internal.
What to look at
The demo help site
Customer release notes with a page for each release, the help articles Veliose drafted and updated, and the QA test scenarios.
Open the demo site →The dashboard
Generate, Review and Publish, with every draft shown beside the pull requests and tickets it came from. Anyone can look around; making changes needs an authorized sign-in.
Open the dashboard →The Help Center
How each part of Veliose works. Its articles are drafted, reviewed and published through Veliose itself.
Read the Help Center →A path through it
- On the demo help site, open Release Notes and read one release.
- Open the dashboard and go to Review. Choose the same release to see its drafts, each with the pull requests and tickets it came from.
- Compare a release note’s internal and customer versions: the customer version leaves out internal changes and ticket links.
- Go to Publish to see where each kind of output goes for this product.
Everything in the demo is sample data: the product, its code, its tickets and its help site. No customer records are involved.