The following pages are tagged with
|Documentation style guide
|This style guide is intended to ensure that LoopBack documentation has a consistent, clear, and unified style. It is intended to be prescriptive but not one...
|The LoopBack project governance model follows the spirit and tradition of open source by embracing consensus, forking, and individual ownership.
|Including READMEs from other repositories
|The LoopBack documentation includes a number of README files from related repositories, including examples, data source connectors, and components.
|Markdown style guide
|Important: Follow the rules outlined here to ensure that Markdown displays consistently and accurately on this site, GitHub, and npmjs.com (where applicable). Introduction Github uses Redcarpet to parse READMEs and other markdown files. It is, generally speaking, more permissive/forgiving than...
|Follow the procedure outlined here when reporting issues with the LoopBack project.
|Contributing code in LoopBack 2.x and 3.x
|This article explains the process and guidelines for contributing code to the LoopBack 2.x and 3.x projects.
|This article explains the process and guidelines for contributing code to the LoopBack project.
|Contributing to LoopBack documentation
|We welcome contributions to LoopBack documentation!
|Using ESLint with LoopBack repositories
|Contributing to LoopBack
|Contributions to the LoopBack project are welcome!
|Code style guide (2.x/ES5)
|These are LoopBack's general coding style guidelines for pre-ES6 branches, e.g. 2.x release lines.
|Code style guide (3.x/ES6)
|These are LoopBack's general coding style guidelines for ES6 branches, e.g. 3.x release lines.
|Code style guide
|These are LoopBack's general coding style guidelines.
|Tags provide another means of navigation for your content. Unlike the table of contents, tags can show the content in a variety of arrangements and groupings.