Appearance
lt-docs
needs verificationPurpose
lt-docs is the public help site for researchers using the mobile app. This internal site links to that help rather than duplicating its tutorials.
What it does
It covers profile setup, account management, recording, video formats, sharing, coordinator accounts, payment and support. Its tutorials address researchers and coordinators using the app.
Its names need care. “Video Publication” describes a video about a paper and resembles engineering's Publication. The brief suggests mapping “Expert Video” to Publication Plus, but the help source describes a three-chapter professional introduction, resembling Profile Video. Do not treat either mapping as client-approved.
For maintainers: technology
VitePress 1.3 builds the static site. Pages CMS, a content management system, edits Markdown pages and associated media.
How it connects
Authorized maintainers use Pages CMS to edit the help pages. This is documentation about the app, not the system of record for app workflow. Public help currently describes editorial quality checks and fees, which require reconciliation with the current minimum viable product (MVP).
Who can do what
Yes means the public-help role is intended to support the action. No means that LT business role grants no editing access. Partial means separately granted editing access is required and the owners are unrecorded. The deployed public URL is still unknown.
| Action | Anonymous | Researcher | Coordinator | Administrator | Editor |
|---|---|---|---|---|---|
| Read public help | Yes | Yes | Yes | Yes | Yes |
| Edit help through an LT account role | No | No | No | No | No |
| Maintain help with separately granted access | No | No | No | Partial | Partial |
A Strapi Editor account does not establish Pages CMS access. The people authorized to maintain the help site still need to be confirmed.
Environments and links
Public helpAsk the team lead for the current link; its published location needs confirmation.
Until the team provides that link, use the explanations and installation steps in this guide.
Where to read more
Use the mobile app guide for orientation here. Ask the team lead for the current public-help link; its published location still needs confirmation.
Known gaps
The deployment URL and help owners are unrecorded. The home page contains placeholder feature cards and hero links missing the /help/ prefix. The client must reconcile video terminology and confirm which older quality-review and payment instructions remain valid. See open questions.
For maintainers: source references
These references require repository access. Everything needed to understand this page is explained above.