Codeberg/Documentation
42
199
Fork
You've already forked Documentation
161

Graphical summary of the infrastructure of codeberg #201

Closed
opened 2022年02月11日 00:06:40 +01:00 by renaissance · 7 comments
Contributor
Copy link
No description provided.
Author
Contributor
Copy link

@fnetX what do you think of this representation


Project Overview
Project Type Language Maintained by
Gitea Main Project Go Codeberg*/Gitea
Woodpecker CI Main Project Go Codeberg-CI*/Woodpecker-CI
Pages Server Main Project Go Codeberg
Moderation Tool Side Project Go Codeberg
Codeberg Design Public Relations HTML/CSS/JS Codeberg

*This is only a fork for codeberg specific patches - PRs are accepted but they are prefered upstream

@fnetX what do you think of this representation --- <table> <tr> <th colspan="4">Project Overview</th> </tr> <tr> <th>Project</th> <th>Type</th> <th>Language</th> <th>Maintained by</th> </tr> <tr> <th>Gitea</th> <td>Main Project</td> <td>Go</td> <td>Codeberg*/Gitea</td> </tr> <tr> <th>Woodpecker CI</th> <td>Main Project</td> <td>Go</td> <td>Codeberg-CI*/Woodpecker-CI</td> </tr> <tr> <th>Pages Server</th> <td>Main Project</td> <td>Go</td> <td>Codeberg</td> </tr> <tr> <th>Moderation Tool</th> <td>Side Project</td> <td>Go</td> <td>Codeberg</td> </tr> <tr> <th>Codeberg Design</th> <td>Public Relations</td> <td>HTML/CSS/JS</td> <td>Codeberg</td> </tr> </table> \*This is only a fork for codeberg specific patches - PRs are accepted but they are prefered upstream
Author
Contributor
Copy link

The above table will be completed with all codeberg projects. This table is meant for newcomers to get a overview of the projects on codeberg.

In additions to that we will create a diagram for the internal infrastructure for each core project.

The above table will be completed with all codeberg projects. This table is meant for newcomers to get a overview of the projects on codeberg. In additions to that we will create a diagram for the internal infrastructure for each core project.
Owner
Copy link

I like the table, it's probably also simpler to implement in the Docs than an image (and can still look nice).

All Go projects also have a UI part, you could mention this, too. Maybe write something liek "Stack", this would be like

"Backend: Go / Frontend: Less, Fomantic, JS"
and maybe mention JS frameworks like the Design kit uses Vue AFAIK.

I suppose you want to list more projects and Codebrg Design was just listed as one thing next to the main projects?

I like the table, it's probably also simpler to implement in the Docs than an image (and can still look nice). All Go projects also have a UI part, you could mention this, too. Maybe write something liek "Stack", this would be like "Backend: Go / Frontend: Less, Fomantic, JS" and maybe mention JS frameworks like the Design kit uses Vue AFAIK. I suppose you want to list more projects and Codebrg Design was just listed as one thing next to the main projects?
Author
Contributor
Copy link

I suppose you want to list more projects and Codebrg Design was just listed as one thing next to the main projects?

I wanted to let you review the priciple before I add all the projects

Maybe write something liek "Stack", this would be like

I am not quite sure what you are meaning with "Stack"

"Backend: Go / Frontend: Less, Fomantic, JS"

Less and Fomantic instead of HTML/CSS right?

> I suppose you want to list more projects and Codebrg Design was just listed as one thing next to the main projects? I wanted to let you review the priciple before I add all the projects > Maybe write something liek "Stack", this would be like I am not quite sure what you are meaning with "Stack" > "Backend: Go / Frontend: Less, Fomantic, JS" Less and Fomantic instead of HTML/CSS right?
Owner
Copy link

meaning with "Stack"

yeah, something that gives people a better impression of what's needed. Not only backend developers, but also frontend guys. Not sure how to express this best, always writing "HTML, CSS, Javascript" sounds a bit silly ... maybe we can just say "Frontend".

> meaning with "Stack" yeah, something that gives people a better impression of what's needed. Not only backend developers, but also frontend guys. Not sure how to express this best, always writing "HTML, CSS, Javascript" sounds a bit silly ... maybe we can just say "Frontend".
Author
Contributor
Copy link

Should the language tab stay or should we replace it with frontend/backend/fullstack

Should the language tab stay or should we replace it with frontend/backend/fullstack
Author
Contributor
Copy link

This is the current approach from the PR. Also the projects are now links directing to the repositories

image

This is the current approach from the PR. Also the projects are now links directing to the repositories ![image](/attachments/eab8135b-554f-4c46-a71e-1aa4c7718792)
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/major-cspell-monorepo
renovate/mstruebing-editorconfig-checker-3.x
renovate/lycheeverse-lychee-0.x
renovate/font-awesome
renovate/prettier-3.x
renovate/markdownlint-cli2-0.x
renovate/markdown-it-14.x
renovate/davidanson-markdownlint-cli2-0.x
renovate/pipelinecomponents-yamllint-0.x
renovate/11ty-eleventy-3.x
renovate/node-lts-slim
renovate/npm-pnpm-vulnerability
ci_pr_close_no_preview
pr-554
pr/554
gitea-icons-shortcode
No results found.
Labels
Clear labels
Codeberg Pages
Issues affecting Codeberg Pages
Documentation Usability
Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator
This is related to the generation of the documentation, not to the content itself
Priority: High
The priority is high
Priority: Low
The priority is low
Priority: Medium
The priority is medium
Reviewed: Confirmed
Something has been confirmed
Reviewed: Duplicate
Something exists already
Reviewed: Invalid
Something was marked as invalid
Reviewed: Wontfix
Something won't be fixed
Status: Blocked
Status: Help wanted
Contributions are welcome!
Status: In progress
Work is in progress
Status: Needs feedback
Feedback is needed
Status: Ready for Review
Work is completed
Status: Review
Review is in progress / Reviewers wanted
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Total time spent: 3 hours
renaissance
3 hours
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Documentation#201
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?