Lexicon Community is commissioning a logo. This is a paid engagement, sponsored by the AT Community Fund. It follows the discussion in this forum thread.
What we’re looking for
A logo for lexicon.community that works as the project’s visual identity across platforms: GitHub and Bluesky avatars, favicon, and similar small-format uses. The website already has an identity we like, so this is not a rebrand. We need a mark that reads well at small sizes and represents the project on social platforms.
Optionally, you may also quote for a Bluesky banner / social cover image. This is a nice-to-have. The logo is what we’re really after.
We’re looking for designers with brand or logo design experience.
Timeline
-
Applications open: Wednesday, July 8, 2026
-
Applications close: Wednesday, July 15, 2026 at 11:59 PM EDT (Thursday, July 16 at 6:00 AM CEST)
-
Selection starts Thursday, July 16. The decision will be made by the project lead, a co-lead (if one is found by then), and the Lexicon Community steering committee.
How to apply
Post your application as a comment on this GitHub issue or as a reply on the forum thread. Include:
-
A portfolio, ideally showing logo or brand identity work
-
A quote for the logo, including feedback rounds and final polish
-
Optionally, a separate quote for a social banner
-
Your availability and how long the work would take
-
Confirmation you can deliver final files as vector source plus SVG/PNG exports suitable for avatars and favicons
Applications are public, but if you prefer not to share pricing publicly, apply publicly and send your quote by DM to @there-hugo.dev on Bluesky.
Process notes
-
This is not a design contest. No spec work. We select one designer based on portfolio, quote, and availability, and that designer is paid to do the work.
-
Usage rights: the final logo will be used freely by the Lexicon Community project; exact licensing terms will be agreed with the selected designer.
-
Applications are centralized on the GitHub issue: lexicon-community/lexicon #79
Questions welcome in the comments.
Thanks!