-
Notifications
You must be signed in to change notification settings - Fork 385
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
General review and testing #55
Comments
Nice to have: which pages should be changed in LB 3.x docs? |
@davidcheung Let me know if you have questions. We're launching the site next week, so please have a look ASAP. |
@crandmck will get on it today |
Suggestion
Fixables
Content missing
|
That was just a glitch... fixed.
[http://loopback.io/doc/en/lb2/Create-a-simple-API.html](Create a simple API) basically covers that territory. (BTW, Issac wanted to call it "create an API" and not "create an app"). In contrast, Creating an application is more of a general task-oriented article vs. a tutorial.
Created #60 to fix this.
Yes, it used to be under "Reference" but it really got lost there. I wanted to make it more prominent, and that was the best place I could find.
Fixed the link, and changed wording a bit.
Which article?
This comes from the MySQL connector README; need to fix it there. Same with Informix. Re: the nav bar glitches, I'm still working those out. I'll need to rework the navbar a bit, because Sequoia reimplemented the widget and it works a bit differently. Will comment on those once I get 'er done. |
As @crandmck mentioned, we discussed the possibilities for side-nav "container"/folder items and the following seemed to be the options:
Confluence allowed for option 3 above. I argue(d) that this behavior is confusing as it makes menu clicks less predictable (will this send me to a page? to the child? no page?). Option 1 and option 2 require more or less equal reworking of content organization: either move all "folder" pages to "folder> first child page" for solution 1, or ensure that all "folder" menu items have their own page they link to, overview of the section e.g. I went with option 2 above, which will require those "folder" items with no page to have one created for them to point to. None of the solutions is perfect but that one seemed to create the most intuitive, predictable UX (click menu link, it takes you to a page, 100% of the time) so that's what we went with! It's certainly changeable but to my mind it's the sort of bike-shed issue that's best to just pick a solution & go with it. 😸 |
Actually, on the old Confluence site https://docs.strongloop.com/ every "leaf" in the navigation "tree" corresponds to a page (which may or may not have children). If you click on the This is also how it's currently working on loopback.io, which is great and exactly what I asked for. However, there are still a few problems with how second-level containers work, that I suspect come from the server-side (Jekyll/Liquid) behavior. And I would really like to be able to have one more level of nesting.... but I'll open a separate issue for these. |
In this scenario to be specific, because right now on http://loopback.io/doc/en/lb2/Model-property-reference.html, when you click on basically this #64 |
@davidcheung Yes, there are quite a few examples of similar problems. I'm working on the sidebar right now to address these. Will let you know when I'm done so you can check it out. |
So, I've fixed the sidebar (David pointed out one issue I missed, and I fixed it). So, I think we can close this, since we're essentially "launching" the site tomorrow with the blog post, etc.. Thanks for your help @davidcheung! |
Before launch, it would be good to go through the content in http://loopback.io/doc/en/lb2/ and do thorough review for accuracy, completeness, formatting, etc.
The text was updated successfully, but these errors were encountered: