- tagline Beyond Coding. We Forge.
- logo
- mascotte
- home page
- about
- legal/imprint
- privacy
- Code of Conduct / well being / moderation
- FAQ #33
- announcement blog post #34
Discussing the content of the website #2
The website should mention how the project differs from Gitea. I like the HedgeDoc timeline which describes how it came into existence.
@circlebuilder suggested to aim at launching on 14th November 2022.
@dachary You suggested, that
As someone who heard of the fork and consider using [...] it because it gives them a Free Software guarantee that Gitea no longer provides, I would like to see single page that shows (i) what it is, (ii) where to get releases.
As a potential contributor (that's a tiny minority of the audience) I would also need a link „Contribute" that redirects to the repository.
@fnetX suggested to take a look at https://codeberg.org/about for inspiration
- code of conduct
- matrix rooms
I guess a small biography of the maintainers/contributors could be nice. To show the experience with codename as well as current responsabilities/focus.
Another content possibility would be a blog, but it need motivated people to regularly write posts...
I guess a small biography of the maintainers/contributors could be nice. To show the experience with codename as well as current responsabilities/focus.
Something like the Garuda Linux about page (this one was the first that came to my mind).
The website should mention how the project differs from Gitea. I like the HedgeDoc timeline which describes how it came into existence.
Something like:
Gogs -> Gitea -> codename
Another content possibility would be a blog, but it need motivated people to regularly write posts...
This is rare, very. It would be great that someone with that talent is inspired by "codename".
I would also like to see an FAQ, this was something discussed by @dachary and me in the forgefriends online coworking session, we might want to have a FAQ whereby one of the questions would be: "Why is this forked backed/supported/hosted by Codeberg" (needs different phrasing).
- release pages (with Changelog?) or at least links to the Release Page (in case Codeberg has that. Never seen it but never looked for it either). I would expect the valid GPG Key ID there.
I added a pad for collaborative editing and propose we discuss the bare minimal content the website must have at the date of the launch which is likely early december.
I factored in the pad the content of this discussion except for:
- the bio of maintainers because I think the "who" could simply be Codeberg as a community because it already has a good enough reputation
- the blog because I don't know that anyone is willing to commit to that (and the release notes could be a kind of techno blog at the beginning?)
- the blog because I don't know that anyone is willing to commit to that (and the release notes could be a kind of techno blog at the beginning?)
If we blog release notes they should be structured in a way, that it is possible to have a RSS / Atom feed just for them alone. Be it via category or tax or any other taxonomy.
Do you have an example of what you mean? I think I'm only getting that idea vaguely.
For example, Wordpress allows you to have a main feed:
as well as per category:
https://boffosocko.com/category/mathematics/feed/
(Taking a fellow IndieWeb person as example).
Since not everyone is interested in everything, releases would allow to notify those that are particular interested in this information.
Chatroom discussion about the target audience at launch time to define what the homepage should contain.
And the corresponding pull request codename/website#15
I summarized what is done for the content of the website and what's left to do:
- FAQ
- announcement blog post
- Call for help with interview / survey to build the roadmap
The announcement blog post is discussed in this PR #34
A survey was drafted and is experimented with
Closing this as the essential content for the website are present. The focus of this issue was to act as a checklist so nothing is missing.
No due date set.
No dependencies set.
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?