Rebranding - Summary

[pengyin-shan]

@isawil , the Alliance team discussed rebranding DMP Assisant, including tasks such as changing the page style to adopt a new color theme and new logo, changing the 'support@portage' email address, changing the current URL, etc. This project got interrupted because of the 3.1.0 migration. You can pick it up in the future. I have built https://portagenetwork.github.io/ for anyone to taste the new style.

I have finished rebranding dev work based on the 3.0.4 version of DMP Assistant, at the rebranding branch (https://github.com/portagenetwork/roadmap/tree/rebranding) before 3.1.0 upgrade, thus this branch needs to migrate 3.1.0 changes before continuing. I understand that the re-upgrade could be tough, so I'll let the future developer decide if it should be totally redone.

Lee used to send me the new branding style guide and image/logo files. I attached it here:
DMP-PGD_LOGO_FILES.zip
DMP-PGD_brand_guide_v1.2.pdf
I'll also forward the email to you.

For your reference, these are the tickets we have created for re-branding:

• Rebrand template names #297
• Rebrand support email address #270
• Accessibility Check after Rebranding #197
• New Terms of Use Page & Migration of Documentation from Portage website #152
• PENDING after v3/v4 migration: Alliance email migration #291
  I suggested you confirm their status at the service team meeting before the process. If you have any questions about rebranding, you can consult Lee and Omar.

[lagoan]

This work is looking great. I like the Digital-GREY re-branding better.

Here are a couple of things that we need to address:

• The link colour of #00DBA7 over #FFF needs to change so we can have higher contrast. At this point, however, I don't know what colour we can use.
• On the dropdown menu for organization selection the text colour is white with a white background. A darker font colour will work best:
  
• The "Write plan" button on the plan creation tabs is out of place. This may be a change from upstream though:
  
• In each plan section the "Save" button has an animation. This is a great way to attract a user's attention for something that requires immediate attention, but it is not necessary for this "Save" button.
  

[200455939-yashu]

Click on 'My Dashboard' then click on any other tabs quickly back and forth. The blue text colour shows up.

[lagoan]

The drop down menu for selecting language is too far apart from the Language button:

We get the same error for the profile dropdown menu:

[shilowil]

The new link color looks much better, but we should check to ensure it still meets contrast requirements. FRDR uses a blue/green color for their links, but it is much darker -- linking so you can take a look and see if it might be suitable, but I like the yellow as well.

I'd also like to see the DMP Assistant logo in the heading spaced similarly to the logo we have in the current design -- so, brought in towards the right a bit. In my browser (Firefox) it's showing at the far left of the screen.

[shilowil]

The "Notice: signed in successfully." alert is displaying in blue. Wondering if it's possible to update these colors as well?

Also noticing that the "Privacy statement" footer link isn't underlined while the other links are. The link still works, but it'd be best to underline it to bring it into cohesion with the other links.

[lagoan]

@200455939-yashu to change links to blue and yellow on hover as in https://www.frdr-dfdr.ca/repo/

[lagoan]

I found the logo for DMP Assistant has a large border on mouse hover.

The current production version also has a hover border but it is not as large.

The organization header overlaps the DMP Assistant logo border as shown here:

@isawil @200455939-yashu Should we decrease the size of the border? What other actions can we take to change this?

[200455939-yashu]

These borders needs to be reduced.

[closenma]

I'll be taking over this ticket to complete the remaining work on the rebrand over the next few weeks

[closenma]

We've completed all work except the final parts of email migration (where we're sending email from). Closing this issue and leaving #270 open and scheduling work for next cycle