32
41
Fork
You've already forked website
52

Change "News" section to "Blog"? #65

Closed
opened 2023年01月15日 15:16:25 +01:00 by circlebuilder · 9 comments

@dachary brought up the question if a Woodpecker instruction is fitting for the News section.

Valid question.

My opinion is that the website better has a "Blog" section for both News and other informative articles. This makes it more relevant for people to check regularly or add the RSS feed.

And if we refer to the website theme, once we enable more sections now not visible, there's one that displays some blog posts on the landing page. This might filter exclusively to News-type blog entries.

@dachary brought up the question if a [Woodpecker instruction](https://codeberg.org/forgejo/website/pulls/55#issuecomment-772371) is fitting for the News section. Valid question. My opinion is that the website better has a "Blog" section for both News and other informative articles. This makes it more relevant for people to check regularly or add the RSS feed. And if we refer to the website theme, once we enable more sections now not visible, there's one that displays some blog posts on the landing page. This might filter exclusively to News-type blog entries.

At least it is a broader category than News and we do not have a solution for instructions, discussions or any other kind of content.

At least it is a broader category than News and we do not have a solution for instructions, discussions or any other kind of content.

I think the News section is fine as it is.

I think the **News** section is fine as it is.

In that case an additional Blog section can be added.

In that case an additional **Blog** section can be added.

I created forgejo/meta#116 detailing how for this kind of informative articles a dedicated Forgejo Lemmy community might serve the purpose for guest authors.

I created https://codeberg.org/forgejo/meta/issues/116 detailing how for this kind of informative articles a dedicated Forgejo Lemmy community might serve the purpose for guest authors.

Funnily the <title> of https://forgejo.org/news/ is Blog...

I think I initially used the term News since this section was meant to be used to inform about new releases as well as blog posts.

Current tags in use:

  • releases
  • security (always along releases)
  • federation
  • news

The "Woodpecker post" #55 could be posted under a guide or tutorial tag (since we don't have proper documentation yet).

Funnily the `<title>` of https://forgejo.org/news/ is `Blog`... --- I think I initially used the term `News` since this section was meant to be used to inform about new releases as well as blog posts. Current tags in use: - `releases` - `security` (always along `releases`) - `federation` - `news` The "Woodpecker post" #55 could be posted under a `guide` or `tutorial` tag (since we don't have proper documentation yet).
Member
Copy link

I'm in favor of renaming News to Blog in the nav menu and consistently keep Blog in the meta title.

I don't think a new Blog section or tag is necessary.

I think the body title should remain as-is.

I'm in favor of renaming *News* to *Blog* in the nav menu and consistently keep *Blog* in the meta title. I don't think a new *Blog* section or tag is necessary. I think the body title should remain as-is.
Contributor
Copy link

I feel like either we need to offer a separate RSS feeds for those that want to stay informed on new releases - and only those - or have another navigation item for a Blog.

Right now I think this decision is too early. There would be not enough regular content to fill a blog. Who's going to write it?

Therefore I vote for keeping things as they are now and revisit this issue in a few months.

I feel like either we need to offer a separate RSS feeds for those that want to stay informed on new releases - and only those - or have another navigation item for a Blog. Right now I think this decision is too early. There would be not enough regular content to fill a blog. Who's going to write it? Therefore I vote for keeping things as they are now and revisit this issue in a few months.

The original issue was about renaming "News" to "Blog" so that that would fit more regular articles as well as announcements. This simple rename would make it possible to publish the Woodpecker article by @earl-warren, which isn't News but informative and useful.

The original issue was about renaming "News" to "Blog" so that that would fit more regular articles as well as announcements. This simple rename would make it possible to publish the [Woodpecker article](https://codeberg.org/forgejo/website/pulls/55) by @earl-warren, which isn't News but informative and useful.

It seems that during the last two years, this wasn't a big issue. The scope of the news section is indeed news and blog articles seem to be out-of-scope of the current news section. If, in the future, there is interest in publishing blog posts (tutorials, etc.), we could still introduce "Blog" as an extra item.

It seems that during the last two years, this wasn't a big issue. The scope of the news section is indeed news and blog articles seem to be out-of-scope of the current news section. If, in the future, there is interest in publishing blog posts (tutorials, etc.), we could still introduce "Blog" as an extra item.
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
7 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#65
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?