loopbackio / loopbackio/loopback.io
Fix: loopback.io website - Proofread, Edit and Fix Links
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 276
- Forks
- 382
- Avg merge
- 6h 17m
- Merged PRs (30d)
- 18
Description
URL of the page
Nature of the issue
I have used LoopBack versions 1.x to 3.x in the past as a consumer and have yet to use 4.x in a project. I want to give back and start by getting up to speed since this is the first time I have looked at something related to StrongLoop or LoopBack in over two years.
I can be a set of fresh eyes. I want to start by reviewing the landing page and incrementally navigating the site.
On the landing page, we can start with low-hanging fruit and address the following issues:
Current Open Issues
- https://github.com/loopbackio/loopback.io/issues/1580
- https://github.com/loopbackio/loopback.io/issues/1569
- https://github.com/loopbackio/loopback.io/issues/1338
- https://github.com/loopbackio/loopback.io/issues/1390
- https://github.com/loopbackio/loopback.io/issues/1390 (Recommending it be closed)
- https://github.com/loopbackio/loopback.io/issues/1507
- https://github.com/loopbackio/loopback.io/issues/1432
@dhmlau, Can we set the label to doc for the above-mentioned issue?
Currently, I'm limited to spending 4 to 8 hours a week addressing this issue, and I plan to address the first issue the upcoming Monday, if not sooner.
I look forward to working with you all. Please let me know how I can support this project. Thanks, P-)
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
Start with the loopback.io landing page, then read the still-open linked issues 1580, 1338, 1390, 1507, and 1432 to establish each requested change. Done means the listed proofreading and link fixes are addressed and the relevant issue states are updated.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100