-
Notifications
You must be signed in to change notification settings - Fork 15
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
Referring sovity in MDS CaaS version #518
Comments
Details for the new Box on Dashboard. |
Let us use https://sovity.de/en/contact/ as this directly leads to english version |
@illfixit following consultation with SK, Option 3 is preferred because we understand that MDS would like to standardize across all their partners that proprietary logos (such as sovity's) appear at the bottom right. Furthermore it is more valuable for the sovity brand that we make the logo persistent at the bottom right instead of appearing at the end of the page only after scrolling. Do you have some proposal how we might achieve this result? |
@illfixit responding to your questions here. Option 3 should be displayed for all MDS profiles. What about the possibility make the logo persistent at the bottom right instead of appearing at the end of the page only after scrolling. Do you have some proposal how we might achieve this result? |
I would not go with an overlay, if we have no footer. Either we need a footer or we would have it at the end of each page IMO |
If footer is not possible or too complex, we could just go with option 1 rather than put logo at very button and user would need to scroll |
@sebk46 @SeBuSov Following alignments with @illfixit, decision is we go with Option 1. Reasoning:
|
Feature Request
Description
Add in hosted MDS Caas profile
Which Areas Would Be Affected?
EDC UI
Stakeholders
@sebk46
@AbdullahMuk
Work Breakdown
a new box in dashboard "Provided by sovity" with sovity logo and a short text with trigger that can be upgraded for more power.
Implemented as be green circled area on Dashboard UI
"Powered by sovity" branding
Option 1 is favoured for implementation.
Reasoning:
The text was updated successfully, but these errors were encountered: