# Veliose

> Change Intelligence Platform


## Posts

- [Hello world!](https://veliose.com/hello-world/): Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

## Pages

- [QA Test Scenarios](https://veliose.com/help/qa-test-scenarios/): Manual test scenarios generated from tracked changes. Pass/Fail and Notes are filled in by a tester while actually running each test.
- [v0.10.0](https://veliose.com/help/release-notes/v0-10-0/): Each product's help hub links to its release notes, QA test scenarios and help articles, with an optional introduction set on the Config page.
- [Release Notes](https://veliose.com/help/release-notes/): What changed in each release of the product.
- [Setting Up a Product's Help Hub](https://veliose.com/help/setting-up-a-products-help-hub/): Each product has a help hub of its own: a page that introduces the product and gathers its published content in one place.
- [Setting Up a Product](https://veliose.com/help/setting-up-a-product/): The Config page holds each product's settings: where its changes come from and where its drafts are published.
- [Reviewing Drafts](https://veliose.com/help/reviewing-drafts/): Every draft the platform writes waits on the Review page until a person decides what happens to it.
- [Publishing Approved Drafts](https://veliose.com/help/publishing-approved-drafts/): Publishing sends approved drafts to the destinations the product has chosen on the Config page.
- [Generating Drafts](https://veliose.com/help/generating-drafts/): Once a release's changes have been brought in, the platform drafts three kinds of content from them.
- [Finding Your Way Around the Control Plane](https://veliose.com/help/finding-your-way-around-the-control-plane/): The control plane is the dashboard where a team turns its software changes into release notes, documentation and QA test scenarios.
- [Connecting Your Tools](https://veliose.com/help/connecting-your-tools/): The platform signs in to other services to do its work: one to read the product's code and pull requests, one to read its tickets, and one for each destination it publishes to.
- [Choosing a Product's Settings](https://veliose.com/help/choosing-a-products-settings/): On the Config page, a product's Jira project, Confluence space, WordPress hub page and GitHub repositories are chosen from lists read from the product's own connections.
- [Bringing in Changes](https://veliose.com/help/bringing-in-changes/): Every draft the platform writes is based on evidence: the pull requests that changed the code and the tickets that explain why.
- [Veliose Help Center](https://veliose.com/help/): Help articles, release notes and QA scenarios for Veliose.
- [Privacy](https://veliose.com/privacy/): This page lists what this website and the Veliose dashboard collect, and why. Neither uses analytics, advertising or tracking cookies.
- [Live Demo](https://veliose.com/live-demo/): The live demo runs a sample point-of-sale product, Retail POS, through Veliose.
- [How It Works](https://veliose.com/how-it-works/): Veliose gathers the evidence of each software change once, drafts from it in three workflows, and publishes only what a person approves.
- [Home](https://veliose.com/): Veliose turns each software change into release notes, help-article updates and test scenarios, drafted from the pull request and its ticket.


[comment]: # (Generated by Hostinger Tools Plugin)