-
Notifications
You must be signed in to change notification settings - Fork 75
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 header menu element for library in Studio #14203
Comments
I think we should include the image section in the library, so it’s clear that more is coming. After all, it’s a beta. My suggestion: Should we add the beta tag to the library itself as well, for example here? @Ildest Have you gone through all the texts in the library, or would you like to review how it looks in dev regarding the content? We could create a task for that if needed |
First, you suggested text above is good to go @Annikenkbrathen :-). Second, yes I would like to review it with you in dev, so I am sure - it´s been a while since these texts were created, and things may have changed. Also, I will be easier fro me to contribute a news text that @standeren asked for in another task, if we look at this first. |
News snippet suggestion: Vi har lagd et nytt bibliotek! Her finner du nå kodelistene dine. Vi jobber med å utvide biblioteket slik at du også kan finne og lagre andre ting der, for eksempel bilder og tekster. |
Description
Add a new menu element in the Studio header for accessing the library. The menu element should enable the beta tag.
Here is the config to add to
headerMenuUtils.ts
:In order to announce the library as releaseable we should also either:
AppContentLibrary.tsx
, orThis question is probably something @Annikenkbrathen can answer? 😊
We also need a news section for this release. Maybe @Ildest can contribute to formulating one? 🙏
To consideration
Should we call the menu element
Appbibliotek
as this implementation of the library is only in app context and not for organizations, or is this intuitive?Additional Information
⚠ Currently the
beta
functionality is a bit buggy after removingasChild
property from theStudioHeaderMenu
elements. This should be fixable by exploiting pure css;:after
on the class andcontent: Beta
in the class, in addition to the other css needed to maintain the design (remember to use css variables from DS Tag component to maintain same css) . This css class should only be be set when the menu element hasisBeta
prop set.Tasks
No response
Acceptance Criterias
No response
The text was updated successfully, but these errors were encountered: