Skip to content

Follow up/color corrections

MS requested to merge FollowUp/color-corrections into master

What does this MR do?

This MR includes, changes to improve the colors on some areas and some minor tweaks.

CSS tweaks:

  • Reverted emails.css
  • Renamed --fs-color-border to --fs-border-default to make it easier adding new border-colors
  • Improved the dashboard pickup field, the pickup status (slots)
  • Added some new defaults to bootstrap (hr, blockquote, mark, code)
  • The success color added in the color variables generation
  • Store team role colors adjusted to match the old ones (ambassador, red danger → warning, storemanager, warning → secondary, foodsaver, secondary → primary, jumper are primary too) (Closes #1051 (closed))
  • Store team page info box changed to info color
  • Improved the chat color to be more colorful
  • Removed some inline PHP style and moved it to CSS
  • Improved the pickup slot status on a store page
  • When I saw a bootstrap class, I removed it
  • Changed all info boxes to match alert alert-info color
  • foodsharing is no longer bold
  • Word wrapping for p (Closes #1315 (closed), Closes #1316 (closed))

Minor tweaks:

  • Search bar should now focus when shown
  • corrected a translation error

How confident are you it won't break things if deployed?

💯

How to test

Screenshots (if applicable)

Checklist

  • [?] added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • set a "for:" label to indicate who will be affected by this change
  • added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label)
  • added an entry to CHANGELOG.md
  • added a short text that can be used in the release notes
  • Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/?page=bezirk&bid=734&sub=forum. Please change the MRs label to "state:Beta testing".
    • Consider writing a detailed description in German.
    • Describe in a few sentences, what should be tested from a user perspective.
    • Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
    • Be aware, that also non technical people should understand.

Release notes text in German

Edited by MS

Merge request reports