search

Flockingbird / roost

Proof of Concept for Eventsourced backend
https://flockingbird.social
MIT License
35 stars 4 forks source link

Create design system #57

Open stevefloyd opened 3 years ago

stevefloyd commented 3 years ago

image

Details

Before the UI can be fleshed out fully, it is recommended and best practice to create a preliminary design system with a set of branding guidelines. This is so that all design assets that are created are consistent and other people contributing to the project have clarity in how the Flockingbird core project communicates. The @penpot template and source files created can be made downloadable and used as a starting point for other instances to establish their own design system.

Deliverable

Five art boards will be created with corresponding panels and assets...

berkes commented 3 years ago

Great idea. We've had the logo made by a contractor on fiverr. I've attached all the deliveries; also fhe vector.

Please be aware that the logo is not licenced Open Source at this moment (If found nessecary or good for the project, it can always be open sourced). Font used is Montserrat by Google, an Open Source font.

delivery_flockingbird_logo.zip

stevefloyd commented 3 years ago

This will not take much time. Not trying to create a masterpiece, just establish some baseline design standards we agree on so we can iterate more quickly and get all those silly little questions (that often distract from actual work) out of the way up front.

I’m more of a design thinker than purely an engineer, so it helps me (and others like me) to have this in place.

Just like you need an SRS in order to accurately scope and understand a software project, a Design System / Branding guide helps me quickly make design decisions and avoid revisions that are preferential in nature.