You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
inspired by #5113 (comment)
A comparison between ours and RxJS: I like how they unfold and display some core concepts(each in one word) when page loads, to give readers an impression of what the framework does without looking into any details.
(I don't find a good candidate in the root level menu to unfold: "behind the scene" has a long list, others don't list sub-sections in a certain order. But the items in "Inside a LoopBack Application" is close to what I am looking for. )
Here is a list of the most basic concepts I could think of that makes at least REST API developers understand what this framework offers:
App --> Model --> Datasource --> Repository --> Controller --> API Explorer --> Relation --> Security --> Deploy
(Just an example)
Maybe we can refactor "Inside a LoopBack Application" to display ^ in the menu?
I see how it can be useful to be able to get an impression of what the framework does at high level. However, I am not convinced though that the sidebar is the right place for this kind of information. IMO, we should provide such overview on one of the introductory pages, e.g. "Inside a LoopBack Application" you mentioned or perhaps on the landing page (see Overview).
This discussion was converted from issue #5788 on March 11, 2021 13:40.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Quoting from #5718 (comment)
I see how it can be useful to be able to get an impression of what the framework does at high level. However, I am not convinced though that the sidebar is the right place for this kind of information. IMO, we should provide such overview on one of the introductory pages, e.g. "Inside a LoopBack Application" you mentioned or perhaps on the landing page (see Overview).
Let's discuss this idea and find a good solution.
This is a follow-up to #5718, see also #5549.
Beta Was this translation helpful? Give feedback.
All reactions