Appearance
Documentation Verification Checklist
Every feature guide should have a clear evidence trail before it is treated as final customer-facing documentation.
Review status key
- Foundation: page exists but is not a verified product manual.
- Needs validation: steps or feature statements require testing against the actual UI/API.
- Verified: product owner or technical reviewer has confirmed the page against a recorded version and date.
Required review items
- [ ] Product feature and user role confirmed
- [ ] Current navigation labels verified
- [ ] Screenshots captured from IntarvAS (no unrelated products)
- [ ] Sensitive and personal data removed
- [ ] Turkish-to-English wording reviewed by domain specialist
- [ ] API examples executed against appropriate test environment
- [ ] Internal and external links checked
- [ ] Desktop and mobile layout reviewed
- [ ] Reviewer, date, and product version recorded
Screenshot conventions
Store verified screenshots under docs/public/screenshots/<module>/, use descriptive filenames, and include meaningful alt text. Do not fabricate UI images and label them as actual screenshots.
Verification note
Maintain a short changelog when module names, endpoints, or workflow behavior change.
AIO VPBX API source
Confirm the correct AIO VPBX API specification before publishing endpoint guidance. The previously linked vpbx.intarvas.com API URL has not been established as an AIO reference and is no longer presented as authoritative in the customer guides.
