Skip to content

HerbalUG docsframe the docs-i18n issue in that context while maintaining all HerbalUG conversation context and keeping the same tag: & localisation — add to F-Stack/f-stack repository #1075

@Nakatorema

Description

@Nakatorema

Move HerbalUG documentation and localization artifacts into the F-Stack/f-stack repository.

Scope:

  • Create a /docs folder with: developer README, architecture diagram, API docs (OpenAPI), local and production setup guides, and contributor guide.
  • Prepare user-facing materials: quickstart, privacy policy, terms of service, consent text, troubleshooting, and translation placeholders for English, Luganda, Acholi, and Runyankole.
  • Draft launch collateral: marketing checklist, demo script, and stakeholder brief tailored for MOH/NDA/NFA pilot reviews.
  • Link to repository security checklist and required secret scopes; include guidance to review GitHub security settings (e.g. https://github.com/settings/security_analysis).

Acceptance criteria:

  • A clear /docs layout committed in F-Stack/f-stack with files and translation placeholders.
  • Privacy and consent text integrated for registration flow and surfaced for legal review.
  • Contributor and reviewer guidance enabling handoff to ops and government partners.

Notes: If the target repository contains an issue template for documentation, apply it; otherwise create standard markdown docs. Maintain translation placeholders for downstream localization work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions