Open srenault-meeds opened 2 weeks ago
Hi @margondicco , to check. I can't display any UI samples for now. Indeed, it seems I have no more access to adobe XD old files
Hello ok for me
For the font : can we have in the list these fonts Marianne + spectral + Arial + Georgia https://www.systeme-de-design.gouv.fr/elements-d-interface/fondamentaux-de-l-identite-de-l-etat/typographie/
I would like to add these two points in general branding :
Thank you
Ok I added these points to be studied.
Ready for tech review by DAO members (eXo @rdenarie )
Ok for me on tech side.
@boubaker have you evaluate if it will have an impact on our codebase and our portlets, to apply when merging the feature ?
Ok for me on tech side.
@boubaker have you evaluate if it will have an impact on our codebase and our portlets, to apply when merging the feature ?
Yes, there will be changes to do. But as usual, to help you receiving the feature, we will consider changes to propose on eXo side. But just keep in mind that the changes in the context of this MIP will be on some portlets only to prepare a framework, and all other portlets will be considered in Meeds-io/MIPs#135.
Top User Stories Precision: only content portlets (snv, link, image and newslit) will be tested during this implementation to test it out
FYI @margondicco, @rdenarie we won't make any change to newslist for now as it is currently being used by your team. For now, during this MIP, we will test our changes to following portlets:
Description updated + documentation link added
Feedbacks collected from exo-mips: < Only eXo >
Other items need to be worked but these are not blocker for now as another MIP will take care of app's cleanup. As for instance, few apps (tasks, agenda for exo, webconferencing, coediting admin pages don't get the style (background for example, we can custom)
Rationale
The Meeds Layout Manager enables different options to customize pages and portlets:
Considering it, we identified we needed to work on a global review of portlets (cf. MIP #135 )
Before working on such a cleanup, we suggest to implement a framework so we can variabilize such items to then apply it to each portlet. This will help other team to do the cleanup.
1. Functional Requirements
Top User Stories
Precision: only content portlets (snv, link, image) and portlets provided in the dashboard page (AKA overview) will be tested during this implementation to test it out
This framework must help us to manage:
Height for portlet:
Background for portlet:
text-style:
Hence, from the branding options (theme page), we would be able to:
And some specific style is applied for few items:
Impacts
Gamification
NA
Notifications
NA
Analytics
NA
Unified Search
NA
2. Technical Requirements
Expected Volume & Performance
N/A
Security
The Branding Options has to remain modifiable by Administrators only. The read/write of user's theme (dark/light) has to be accessible to current user only.
Extensibility
N/A
Configurability
The default branding options has to remain configurable through branding.less file.
Upgradability
No data upgrade should be necessary in order to benifit from this feature.
Existing Features
No change to apply on default branding primary, secondary and tertiary colors for now, which may not fit the dark mode.
Feature Flags
N/A
Other Non Functional Requirements
N/A
3. Software Architecture
Security
Access
application-body
. This class will define all customizable CSS branding properties, such as colors, heights, margins ...Services & processing
branding.less
has to be defined by theme to allow defining default colors in both modes: light and dark.:root
element, a new path parameter has to be added in order to specify which theme is usedBrandingService
has to be updated consequently in order to allow processing both themes at startup time.Data and persistence
Local Storage
only in order to allow choosing the preferred theme by Device and by Browser.