Add more information to README #85

n0toose commented 2023年07月28日 15:48:51 +02:00

No description provided.

mray commented 2023年07月29日 11:46:42 +02:00

Could you describe what your overall goal with those changes are?

Could you describe what your overall goal with those changes are?

n0toose commented 2023年07月29日 12:19:16 +02:00

• design.codeberg.org is not documented anywhere, I figured this might be the place to do this as people creating applications could probably also use that as a point of reference executing the guidelines present in this repository.
• A small introduction for casual "onlookers" explaining what is essentially going on over here might help slightly reduce the contribution barrier to Codeberg Projects.

- design.codeberg.org is not documented anywhere, I figured this might be the place to do this as people creating applications could probably also use that as a point of reference executing the guidelines present in this repository. - A small introduction for casual "onlookers" explaining what is essentially going on over here might help slightly reduce the contribution barrier to Codeberg Projects.

mray commented 2023年07月29日 18:33:53 +02:00

Thank you for the clarification. I see you probably had something different in mind when thinking about the content of the page.

My main goal with that page was to reach people outside the project that look for resources to represent Codeberg and help them do so correctly.

That's why I like to keep it simple and as short as possible.

In that sense the added text provides misleading information and the addition of the "demo" section should not be used as a representation of any design standards at all (at least not from my perspective).

Aiming for, or even remotely maintaining design consistency across related projects is really hard task and encompasses so much more work being done. I'd even go so far and say it is currently an impossible dream. Even the most superficial requests on changing the main project remain wishful thinking, let alone change different sub-projects. I'd rather keep the ball low by successfully providing simple solutions for external parties on that site only.

So please don't feel discouraged to create another resource that gathers information for another audience. You probably have more insight of what could possibly be helpful from a Codeberg developer perspective.

Thank you for the clarification. I see you probably had something different in mind when thinking about the content of the page. My main goal with that page was to reach people outside the project that look for resources to represent Codeberg and help them do so correctly. That's why I like to keep it simple and as short as possible. In that sense the added text provides misleading information and the addition of the "demo" section should not be used as a representation of any design standards **at all** (at least not from my perspective). Aiming for, or even remotely maintaining design consistency across related projects is really hard task and encompasses so much more work being done. I'd even go so far and say it is currently an impossible dream. Even the most superficial requests on changing the main project remain wishful thinking, let alone change different sub-projects. I'd rather keep the ball low by successfully providing simple solutions for external parties on that site only. So please don't feel discouraged to create another resource that gathers information for another audience. You probably have more insight of what could possibly be helpful from a Codeberg developer perspective.

n0toose commented 2023年07月29日 18:58:14 +02:00

In that sense the added text provides misleading information and the addition of the "demo" section should not be used as a representation of any design standards at all (at least not from my perspective).

You call the shots here. If you don't think this represents what you're building, then I can't persist on merging a change that essentially states the opposite.

Is the introductory paragraph alright, though? I think that throwing people straight into the Logo-Kit may be cutting to the chase too much.

> In that sense the added text provides misleading information and the addition of the "demo" section should not be used as a representation of any design standards at all (at least not from my perspective). You call the shots here. If you don't think this represents what you're building, then I can't persist on merging a change that essentially states the opposite. Is the introductory paragraph alright, though? I think that throwing people straight into the Logo-Kit may be cutting to the chase too much.

mray commented 2023年07月29日 22:39:44 +02:00

Is the introductory paragraph alright, though?

No, sorry :(

This repository contains some information behind Codeberg's design and is mostly
there to help people working on Codeberg make their applications look
consistent and beautiful.

Here is why: So far it contains all relevant design information, and it is mainly made for people working outside Codeberg. It also won't help to making things beautiful either – it just does what simple branding does.

That's what I meant with "misleading".

>Is the introductory paragraph alright, though? No, sorry :( >This repository contains some information behind Codeberg's design and is mostly there to help people working on Codeberg make their applications look consistent and beautiful. Here is why: So far it contains *all* relevant design information, and it is mainly made for people working outside Codeberg. It also won't help to making things beautiful either – it just does what simple branding does. That's what I meant with "misleading".