-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Connectors Reference" docs pages to LB4 docs #2598
Comments
+1 There is more content in LB3 that's applicable to LB4 too. For example, the documentation for |
FYI - @b-admike showed an example of how the content can be "copied" from the README of a repo to loopback.io: https://github.com/strongloop/loopback.io/blob/gh-pages/pages/en/lb3/Cloudant-connector.md. |
For |
@bschrammIBM, thanks for taking up this task. I'm assigning it to you now. Thanks. |
I moved the entire topic from LB3: https://loopback.io/doc/en/lb3/Connectors-reference.html to loopback-next repo and updated the sidebars and the headers. |
@b-admike Can you help trouble shoot this? |
Also, I wanted to point out that you maybe should add a |
As discussed with @bschrammIBM
|
Learning from @b-admike, the |
I'm good with either way.. to point to the |
From @b-admike : "I think I have a solution but it'd probably involve a PR on |
Status update: The doc work for this issue is complete and resides in the |
@b-admike was helping to land the PR but was running into some build issues. That's why this task is blocked. |
These two PRs need to be landed to close this issue. |
The PRs have landed. Closing this issue. |
Description / Steps to reproduce / Feature proposal
When working on #1766, I realized that the docs pages under Connectors references are still very relevant, and also because we're still using the existing connectors.
I'd like to propose to copy these docs pages to LB4 docs.
@strongloop/loopback-maintainers, what do you think?
Acceptance Criteria
References:
See Reporting Issues for more tips on writing good issues
The text was updated successfully, but these errors were encountered: