Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • cerbero cerbero
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 99
    • Issues 99
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • cerberocerbero
  • Issues
  • #101

Closed
Open
Created Dec 17, 2018 by Andoni Morales Alastruey@ylatuyaDeveloper

Cerbero documentation

I would like to starting writing documentation for each new feature we are backporting from Fluendo's repository, so that new features are correctly documented and this documentation lives beyond the Merge Request.

I would also like the docs to live withing cerbero's repository so they can be reviewed in the MR's for new features or updates to existing features.

We could write docs directly in markdown in a docs/ subfolder or start using Hexo which generates beautiful static website for documentation using markdown and very easy to maintain, which combined with GitLab pages can setup a web site for the docs self-maintained.

Edited Dec 17, 2018 by Andoni Morales Alastruey
Assignee
Assign to
Time tracking