Code Releases

Frontity keeps the docs updated with the latest features released in the source code.

This is the community discussion regarding this topic: Code <-> Documentation workflow

For every new feature, bug fixing or code update that requires a change in the docs, this is the workflow to follow on both the code repository (code PR) and the docs repostitory (docs Issue):

• The Pull Request with the Feature is merged
• The Feature Discussion is updated with a Section "Final Implementation" where the details to understand and use the feature are explained
• An issue for documenting the feature is created in the API Reference repository with the following info:
  • Related code PR link
  • Related Final Implementation link
  • Related community forum posts or feature discussions links
  • Any other info that can help in the documentation task
  • Labels
    • priority: p1 high → This should be the default priority but the developer can assign another one from the ones available. The DevRel team will take this priority into account but will decide the final priority for the task
    • type: code release → This label will help the DevRel team to discriminate those issues generated from a code PR
    • any other label that can help to understand better the scope of the issue (max 2 more labels). Example: topic: cache, topic: packages

Every time an issue is created, a quick notification to the DevRel team (via quick message in the #documentation channel) would be appreciated

The DevRel will review these tasks, prioritize them, and work on some of them on every sprint.

Documentation changes before code releases

• To simplify the process we'll work directly against the master branch and no documentation task will be merged until the related feature has been released