32
41
Fork
You've already forked website
53

Discussing the content of the website #2

Closed
opened 2022年11月06日 11:16:55 +01:00 by Ghost · 22 comments

image

image

- [x] [tagline](https://codeberg.org/forgejo/meta/issues/42) Beyond Coding. We Forge. - [x] [logo](https://codeberg.org/forgejo/meta/src/branch/readme/logo) - [x] mascotte - [x] [home page](https://codeberg.org/forgejo/website/src/branch/main/src/pages/index.astro) - [x] [about](https://codeberg.org/forgejo/website/src/branch/main/src/pages/about.md) - [x] [legal/imprint](https://codeberg.org/forgejo/website/src/branch/main/src/pages/imprint.md) - [x] [privacy](https://codeberg.org/forgejo/website/src/branch/main/src/pages/privacy-policy.md) - [x] [Code of Conduct / well being / moderation](https://codeberg.org/forgejo/website/src/branch/main/src/pages/well-being.md) - [x] FAQ https://codeberg.org/forgejo/website/pulls/33 - [x] announcement blog post https://codeberg.org/forgejo/website/pulls/34 ![image](/attachments/337197b1-1d2a-407e-8c7b-961d236efa9d) ![image](/attachments/2cb08ea8-e7e6-4a47-b60d-eee70b57295d)
Ghost changed title from (削除) Content (削除ここまで) to Discussing the content of the website 2022年11月06日 11:17:21 +01:00

The website should mention how the project differs from Gitea. I like the HedgeDoc timeline which describes how it came into existence.

The website should mention how the project differs from Gitea. I like the [HedgeDoc timeline](https://hedgedoc.org/history/) which describes how it came into existence.
Contributor
Copy link

@circlebuilder suggested to aim at launching on 14th November 2022.

@circlebuilder suggested to aim at launching on 14th November 2022.
Contributor
Copy link

@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.

@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.
Contributor
Copy link

@fnetX suggested to take a look at https://codeberg.org/about for inspiration

@fnetX suggested to take a look at https://codeberg.org/about for inspiration
  • code of conduct
  • matrix rooms
- 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.

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...

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).

> 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](https://garudalinux.org/about.html) (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

> The website should mention how the project differs from Gitea. I like the [HedgeDoc timeline](https://hedgedoc.org/history/) 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".

> 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).

I would also like to see an FAQ, this was something discussed by @dachary and me in [the forgefriends online coworking session](https://forum.forgefriends.org/t/forgefriends-online-coworking-november-7th-2pm-utc-1/941), 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).
Contributor
Copy link
  • 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.
+ 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?)
I added [a pad for collaborative editing](https://pad.gusted.xyz/6e40KhdMSwOZxDAZihzInA#) and propose we discuss the bare minimal content the website must have [at the date of the launch](https://codeberg.org/codename/meta/issues/9) 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?)
Ghost added this to the Launch milestone 2022年11月08日 11:46:02 +01:00
Contributor
Copy link
  • 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.

> * 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.

Do you have an example of what you mean? I think I'm only getting that idea vaguely.
Contributor
Copy link

For example, Wordpress allows you to have a main feed:

http://boffosocko.com/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.

For example, Wordpress allows you to have a main feed: http://boffosocko.com/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.
Added https://codename.codeberg.page/privacy-policy/ at https://codeberg.org/codename/website/commit/2c82fdf183d610653575ae11d9e14fd523960dd4

Chatroom discussion about the target audience at launch time to define what the homepage should contain.

And the corresponding pull request codename/website#15

Chatroom [discussion](https://pad.gusted.xyz/haW-va-8Tf60xBIkvfy_Vw#Audience-targeted) about the target audience at launch time to define what the homepage should contain. And the corresponding pull request https://codeberg.org/codename/website/pulls/15

I summarized what is done for the content of the website and what's left to do:

I [summarized what is done for the content of the website](https://codeberg.org/forgejo/website/issues/2#issue-198944) and what's left to do: - [x] FAQ - [ ] [announcement blog post](https://codeberg.org/forgejo/meta/issues/8) - [ ] Call for help with interview / survey to [build the roadmap](https://codeberg.org/forgejo/meta/issues/20)
Items [for the FAQ have been proposed](https://codeberg.org/forgejo/website/pulls/33)

The announcement blog post is discussed in this PR #34

A survey was drafted and is experimented with

The announcement blog post is discussed in this PR https://codeberg.org/forgejo/website/pulls/34 A survey was drafted [and is experimented with](https://codeberg.org/forgejo/meta/issues/20#issuecomment-704220)

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.

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.
Sign in to join this conversation.
No Branch/Tag specified
main
monthly-2026-05
mahlzahn-eslint-js
preview-link-status
nightfire
2022年12月14日-main
No results found.
Labels
Clear labels
404
Broken links or missing content
Accessibility
Accessibility
Blog post
Documentation
Forgejo Documentation
Internationalisation
i18n and l10n
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
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
forgejo/website#2
Reference in a new issue
forgejo/website
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?