Skip to content

[project] Glues - Doc files from glue repo #145

@dalssoft

Description

@dalssoft

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.

Repos to move:

  • Herbs Shelf - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )
  • GraphQL - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )
  • REST - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )
  • Knex - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )
  • Mongo - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )
  • REPL - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )
  • Error to Text - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )
  • Code Snippets - herbsjs.org: (issue: __ / PR: __ ) / glue repo: (issue: __ / PR: __ )

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Ready to code

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions