-
Notifications
You must be signed in to change notification settings - Fork 21
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
[Design] Design brand pattern #32
Comments
Hello, I want to contribute on this. Can I be assigned this issue. |
Hi @Nabhel great to have your interest! Please work closely with @andersonjeccel on this! Could you please join #tt-ux_ui on Slack (get an invite at https://mautic.org/slack)? |
@Nabhel After getting the invite for the Mautic Slack, you can find my DM searching for Thanks for taking the task! |
@RCheesley Thanks for assigning me the issue. yes I just join the slack channel and will start working on this issue. |
Current brands have some patterns that can be used across the application in elements like cards and other kinds of backgrounds, but Mautic still doesn’t have something similar to allow developers to improve in-app visual features.
This task is about creating a design pattern and many variations to expand Mautic’s brand.
Example of what I’m talking about:
You can see some organic shapes on the background of each card. I took this example from Dribbble.
These shapes should be somewhat aligned with the brand we have now (it has to make sense, maybe trying to imply a meaning, that’s up to you).
Feel free to apply your magic.
There are some generators across the Internet that might help generating some shapes, which can be a positive aspect if we’re able to generate a lot of variations from something similar. This would give developers, education team, and marketers the necessary resources to work better with the brand.
It would also be appreciated if you could maybe write some paragraphs later to explain how they work, how to use/apply or their meaning, so we can add to the brand documentation.
The text was updated successfully, but these errors were encountered: