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
Teams are usually organized around containers ( apps ) so the container view is their "home" page. However, in the current implementation, this page is only accessible if the container defines components. Even then, container related documentation is in a separate page that is not linked to the container component page.
It would be nice to have a single landing page for all container related information. Maybe either:
Option 1:
always link a container to its components page, even if it doesn't define components.
show the container properties properties { a b } and the container description on the page
Add a link to ( or a TOC of ) the container documentation (if present) to the page
Option 2:
Always show the container docs page
show the container description and properties on the landing page of the docs
if defined, embed the component view at the beginning of the page
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
-
Teams are usually organized around containers ( apps ) so the container view is their "home" page. However, in the current implementation, this page is only accessible if the container defines components. Even then, container related documentation is in a separate page that is not linked to the container component page.
It would be nice to have a single landing page for all container related information. Maybe either:
Option 1:
properties { a b }
and the container description on the pageOption 2:
Beta Was this translation helpful? Give feedback.
All reactions