You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
check if herbsjs.github.io or the original repo has the most updated doc
create a folder ./doc/herbsjs.org/ on each glue repo with the doc files to be used (ex: .md files).
replace the current README.md doc with a simple link to the corresponing doc on herbsjs.org in 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.
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.io
or the original repo has the most updated doc./doc/herbsjs.org/
on each glue repo with the doc files to be used (ex:.md
files).README.md
doc with a simple link to the corresponing doc onherbsjs.org
in 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:
The text was updated successfully, but these errors were encountered: