Now that Codeberg is officially launched, I think it should get a corporate identity and a more recognizable design - in my opinion, this isn’t only for the looks, but is required to become a well-known open-source platform for open source software instead of just another Gitea host.
A full corporate identity is of course something that needs to grow over the years, but I think a visual identity would be a great start in the right direction. We do have a logo already (I guess it’s final?), so if this is something we can all agree to, I’d really like to contribute to a design.
I absolutely agree - a visual identity is really needed. This includes colors we use, which should be shared among the gitea instance, blog, etc.
The logo is something I did in a few minutes. It is svg and could be refined/improved, for now I quite like it, looks calm and friendly. ;)
Help and discussion on a visual identity is greatly appreciated.
We are cleaning up the build scripts right now, they contain templates and visual assets; and shall become a dedicated repo here in Codeberg/org, every change could then conveniently documented and discussed as traditional version-controlled pull request.
@momar : can you please have a look on build-deploy?
(currently private, will go public in a day or two after we did some more testing.)
Thank you. Should I just create a PR there? I guess the concept (in text form) belongs to Codeberg/org?
Yes, please go on. All UI related work can go there, conceptual (wiki?), discussions (issues?), proposals (pull requests).
Change proposals for bylaws, terms etc, to /org/.
Please post issues as they arise, if we feel confident that the repo will suit the purpose, the build process works and no sensitive data (deployment keys etc) is leaked, we like to switch it public
Hey there. I reached out on Twitter but haven’t heard back yet. I’m a dev who used to be a designer. I’d be more than happy to help with identity/branding/styling/etc.
Perhaps having a dark theme would be a good idea.
I am already using a user-style to have it dark, would be great if it was dark by design/default.
I can’t seem to update my previous comment. So here’s the image referenced.
@Scott-joe : can you please have a look on build-deploy? (currently private, will go public in a day or two after we did some more testing.)
Generally I think it is more important now to have some recognizable color scheme/style than replacing the icon. People should see immediately that they browse Codeberg and not their own/another Gitea instance.
I am not sure if I want dark by default - but a setting sure would be nice.
Mind sharing your theme/settings?
@ashimokawa, I am using this: https://userstyles.org/styles/147278/gitea-io-dark
I will have a look on how to integrate that into Gitea - so that it runs without hacks. Forcing this on all users is probably not good, because some like black on white.
@ashimokawa yeah. It was just some idle fun when I saw Teahub wasn’t dead. I’m happy to work on general branding, colors, styles, etc.
@hw If the “core team” would like me to work on that, I’d like to get together on a call to establish some expectations and get a better feel for what you’d like in the way of branding/styles.
An optional dark style would be nice indeed ;)
I’m between projects at work, so I tried out a tool I’d been wanting to look at. Here’s what it came up with. https://www.dropbox.com/sh/7li2weead0u2zmg/AADvtPhGyHAzkGKDTLUXvLjda?dl=0
I can begin work on a white base, blue accent light theme and accompanying dark theme if you’d like.
Ideally, we would have discussed all proposals jointly, and in public. Albeit of course every one has his private preferences, it would be unfortunate to impose those.
A possible workflow I could imagine would be to create git branches for each proposal, and merge those which get consensus into mainline (that is deploy them).
Regarding the timeline, I could see multiple non-interfering goals:
refine current style and templates gradually, without applying radical changes (one branch for each change; merged as soon enough votes accumulated), and independently
start working on refresh branches in git, with the goal to deploy in 3-6-12 months, here we can work on increasingly radical changes.
What do you think?
In my experience, design by committee is a nearly impossible task. When it does come to a conclusion, it’s results are less than ideal, built on concessions rather than ideas. The adage goes “a camel is a horse built by committee.”
We can achieve the immediate goal of distinguishing ourselves from other Gitea implementations with some minor, but visually clear changes to the imported Gitea styles.
Then later, going through a full branding/identity process, any number of designers can propose a similar set of assets (perhaps filling out a set style guide) for easy comparison during the discussion phase. We can then vote or otherwise whittle down our options with community involvement; eventually arriving at a brand/identity with the majority buy-in from the community.
My biggest concern was in how urgently you needed a new visual identity that would be ready for whatever media launch you may be planning. If you’re comfortable with a slower approach to the branding, we can certainly work on a community-focused process.
@Scott-joe : there is definitely no committee involved … just smaller bites are easy to integrate whereas bigger chunks may or may not need significant testing involved …
Okay. I’ll need to take some screenshots and do some basic design work before figuring out what needs changing in the styles. And of course, dig into the source to figure out where to start making changes.
In regard to the dark-mode requests, there’s apparently a built-in style available after gitea 1.6 https://docs.gitea.io/en-us/customizing-gitea/. It appears to be a global setting in app.ini rather than a user setting. But it’s a start.
Nice, thanks for pointing that out. I tried it on my local instance, works.
Should be not too complicated to make it user switchable (at least for logged-in users)
A dark and light Codeberg theme would be even better ;)
I’ve got a lot of work to do on the house this weekend, but I’ll see if I can cut out some time to work on the beginnings of a dynamic stylesheet or scrape something together from the gitea source.
Finally I’ve got a bit of time on my hands again to respond. I’ll create a draft until mid February, too, so we can get a few different ideas to compare of how Codeberg could look like.
There’s one question that arises to me: should we really start right with design ideas and vote on that, or should we plan what we want to convey with the design first, and base the design on that?
I think that the latter approach makes the design fit the community more - maybe we actually want a camel as a community, but that way we at least get a horse of the right size.
Obviously this can be discussed to no end, but let’s just make this a voting comment: how do you want to use/see your favourite git hosting platform? ???? as a playful and fun community; ???? just as a tool that doesn’t get in your way.
In my opinion, that question is the very first step of creating a brand identity, and will make design ideas a lot more specific.
I can’t edit my comment for some reason, and it seems like Unicode Emoji are not supported, so here’s the question again:
How do you want to use/see your favourite git hosting platform?
:tada: as a playful and fun community
:confused: just as a tool that doesn’t get in your way.**
;) I would hope the two go hand in hand ;)
@momar I see you’re in Germany, so the time of day would make it restrictive, but would you want to collaborate on the visual identity’s 1st public draft(s)?
Regarding user selected theme, just when I wanted to start working on that I saw that gitea has that in the master branch now :+1:
So Codeberg will have that real soon.
Nice. dark theme is a must. I still think it should be default. If it not default, one needs to save cookies, which is a bother.
I don’t think it should be the default. At this point in web-app design best practices, a light theme with a very easy to find dark/night theme option is the best practice.
Do you think creating a group/org “Codeberg-Design” would be a good place for such design development? Having two repos, one for short-term improvements, and one for refresh-cycle (targeting maybe the one-year anniversary?)?
What do you think? Would you like to own this?
Yeah, the work involved with that may muddy the project if it’s left here. And yeah, I can certainly drive that effort.
@momar @scott-joe @mmf please go on!
Let us know if you need help or support. Looking forward to see the first drafts and changes!
@hw would you prefer it be it’s own unique org rather than creating a repo and user group within this org?
Both are fine, a dedicated org gives creators and members more control; please let us know what you prefer.
Merging and integrating PRs between groups and collaborating users is a no-brainer.
What are your thoughts?
I have no preference. It’s just a matter of who has to do the administrative work of setting it up and whether you want it immediately discoverable as part of this org, or whether we’re going to have to find a way to push people over in that direction.
I kind of like the idea of a repo here, that way it’s easier to find.
found our new logo lol
Commit to Codeberg/Design ;)
The registration code for join.codeberg.org is public now. Please check out https://codeberg.org/Codeberg/build-deploy-reg-server.
For consistency, the build-deploy repo for gitea has been renamed to https://codeberg.org/Codeberg/build-deploy-gitea.
Reviews, translations, improvements, and PRs very welcome!
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?