Since the technical feasibility of having the documentation of each glue in its own repository has been demonstrated (issue: #111 / PR: #143) , we need a project to move the documentation to the appropriate repositories, following a pre-defined standards.
For each glue repo we must:
This issue will keep track of the issues and PRs among this repo (herbsjs.org) and glues' repos.
Repos to move:
Since the technical feasibility of having the documentation of each glue in its own repository has been demonstrated (issue: #111 / PR: #143) , we need a project to move the documentation to the appropriate repositories, following a pre-defined standards.
For each glue repo we must:
herbsjs.github.ioor the original repo has the most updated doc./doc/herbsjs.org/on each glue repo with the doc files to be used (ex:.mdfiles).README.mddoc with a simple link to the corresponing doc onherbsjs.orgin order to avoid having multiples source of information.This issue will keep track of the issues and PRs among this repo (herbsjs.org) and glues' repos.
Repos to move: