[BRAND] Add visual identity: icons, logo, palette, theme, redesign UI — fixes #94#106
Conversation
|
Thank you @saadbhattii for the great work! I really enjoyed the new design! I will finish reviewing the PR in more details, but so far I am quite satisfied. Although, 3 points I am still unsure, namely: the background colors and the logo. If you are up to, we can have a synchronized chat on Discord this Thursday (Feb 19th) either 11am UTC or 5pm UTC. |
|
@Doomsk I'd love to chat. 5 PM UTC works great for me. See you on Discord! |
|
@saadbhattii you should now also be able to independently set light and dark themes for the code highlighting: |
|
@Doomsk Thanks for flagging this! I'm still working on finalizing the logo and designs, so I'll circle back to the syntax highlighting once that's done. Happy to tackle it as a follow-up! |
c1c36a4 to
95daeaf
Compare
|
Hey! @Doomsk, I have addressed the appropriate changes. Here's a summary of what's been updated:
|
Great! Thanks @saadbhattii for addressing them. Everybody seems to love the new logo! I'm glad we spent some time trying out many ones. We are ready to proceed to what's left. |


Closes #94
Summary
Hi again! I initially started to design your icon, logo, color palette & fonts simultaneously when I soon found myself needing to verify if all of it really looked unique collectively. As I turned to your documentation, no combinations really satisfied me, hence I found myself completely changing your documentation UI even though it wasn't asked! So I did that to verify my designs, and after reworking & redesigning the UI, I arrived at my final result as well! Everything is designed individually to fit collectively for H-hat's unique visual identity. Moreover, I designed everything to fit in with both of the themes: light and dark. The logo has been designed carefully to satisfy both themes as well!
File Changes (Overview)
UI Screenshots (Before)
UI Screenshots (After)
The final look of the documentation would be based on how someone writes the documentation. The logo placement is for the visual verification with the documentation, the one who writes the documentation may present it in a better format!
I recommend running
mkdocs servelocally to truly experience overall 'feel' of the UI!What's included (Details)
Brand Assets (all CC BY-SA 4.0, my original Figma designs — not AI generated)
icon_light.svg— icon for light theme headericon_dark.svg— icon for dark theme header (CSS-swapped automatically)logo_dual_theme_no_bg.png— transparent background logo for docs homepagelogo_white_bg.png— logo on white backgroundlogo_black_bg.png— logo on black backgroundfavicon-16.ico,favicon-32-a.ico,favicon-48.ico,favicon-64.ico,favicon-128.ico— multi-size favicons, verified visible at 32px in browser tabLICENSE-CC-BY-SA— CC BY-SA 4.0 license file covering all above assetsTheme & Design
#efeded), orange primary (#E99E08), no pure white or black used#1e1e1e), orange accent (#de9905), no pure white or black usedDocumentation
index.mdhomepage via centered image tagindex.mdmkdocs.yml changes
primary: customandaccent: customto allow full CSS variable controlprivacyplugin, it was causing local build failures by timing out on external font downloads (pre-existing issue, unrelated to this PR).Notes
mkdocs serveand verified across Chrome, Firefox, Edge, and Braveprivacyplugin was commented out as it was causing pre-existing build issues unrelated to this PR. The maintainers may want to restore this separately once the underlying issue is resolved.