loopbackio / loopbackio/loopback-governance
awesome-loopback4 to gather videos, tutorials and articles about LoopBack
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
We have a community user did a great job in gathering connectors, tutorials, examples from the community in [awesome-loopback](https://github.com/pasindud/awesome-loopback). I'm wondering if it would be good to have a `awesome-loopback4` for similar purpose.
There seem to be more materials created by the community (I'm only listing a few):
- Videos
- LoopBack 4 Tutorial for beginners https://www.youtube.com/watch?v=cgBCRY169qg
- LoopBack 4 Explained - Introduction [Node.js/API Development] Lesson 1, https://www.youtube.com/watch?v=pDGWb-q65qM
- GraphQL Server in minutes using OpenAPI-to-GraphQL and LoopBack 4, https://www.youtube.com/watch?v=s2hScucNmaA&t=94s
- Tutorials
- LoopBack 4 Database Configuration https://itnext.io/loopback-4-database-configuration-8f085399268
- Mounting Loopback 4 Rest API in Express with Winston Logging https://karannagupta.com/mounting-loopback-4-rest-api-in-express-with-winston-logging/
- A Multi-tenant application with LoopBack 4 https://medium.com/@this.is.samy/https-medium-com-a-multi-tenant-application-with-loopback-4-b28d68dd0dd6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Review the existing awesome-loopback collection and the linked LoopBack 4 videos and tutorials first, then determine where a new collection should live and which resources belong in it; done means the proposed awesome-loopback4 list is organized and includes the relevant community materials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, node.js
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100