Should be accessible at https://forgejo.codeberg.page/@wip-blog/
@ -9,1 +10,3 @@
<h1 class="pt-10 text-6xl">Forgejo - Beyond coding. We forge.</h1>
<div class="centered-content pt-10">
<h1 class="pt-10 text-6xl">Forgejo</h1>
<h2 class="text-5xl pt-2">Beyond coding. Let’s forge.</h2>
The tagline is "Beyond coding. We forge." see forgejo/meta#42
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
@ -13,3 +22,1 @@
<h2 class="text-2xl pb-10">What is Forgejo?</h2>
<p>
Forgejo is a self-hosted lightweight software forge, easy to install and low maintenance that just does the job. Brought to you by an inclusive community under the umbrella of <a href="https://docs.codeberg.org/getting-started/what-is-codeberg/#what-is-codeberg-e.v.%3F">Codeberg e.V.</a> a democratic non-profit organization, Forgejo can be trusted to be exclusively Free Software. It is a "soft" fork of Gitea with a focus on scaling, federation and privacy.
<section class="centered-content py-10 text-lg">
There has been discussions about the content of the home page which concluded that the current home page is right. Of course it could be improved or changed. In the context of this PR which is rather about presentation than content, could we not change the content at all?
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
should be accessible at https://forgejo.codeberg.page/@wip-blog/
- dedicated download page (with proeminent link)
- basic FAQ on the front page
- blog scaffold (with tags)
TODO: add xml feeds (for all news and per tag). This would allow anyone to subscribe to the releases and/or the updates.
the blog looks good :thumbs_up: I don't mind that it is named "news" instead of "blog". The home page content was decided already after one week of discussion and the FAQ should be moved to another page though.
Of course this will all evolve in the future, it is not set in stone. This is just ofr the sake of moving forward to get things right for the December 8th, 2022 deadline
I add rss feed support (for all news and for specific tag).
Since gitea does not offer a feed for new releases, the website can be used by users willing to be informed of new releases, by following the dedicated feed: https://forgejo.codeberg.page/@wip-blog/news/tagged/release.xml
Regarding the content, I strongly think that we should adapt the content of the front page to the discussions that have been raised on various platforms (ycombinator):
THB I didn't see any people asking "how to download". Being able to download is very important but it is not likely to be the first question that occurs to the visitors of the homepage.
Regarding the content, I strongly think that we should adapt the content of the front page to the discussions that have been raised on various platforms (ycombinator):
reason for the fork pronounciation of the name
Could you open another pull request with these changes? I'll comment there. I don't have strong opinions on the matter. But others might and it is unclear if the discussion can be concluded before the launch.
- reason for the fork
I agree this should be prominent. It's our whole reason for existing and people need to understand and be able to make an informed choice.
- pronounciation of the name
I think this can be in an FAQ, it doesn't need to be very prominent in my opinion. Maybe at the bottom of the home page if it's on that page at all.
THB I didn't see any people asking "how to download". Being able to download is very important but it is not likely to be the first question that occurs to the visitors of the homepage.
I agree, but I also think a "Get Started" or similar button doesn't take much space and is a helpful and important thing to have near the top of the page (ideally "above the fold").
I'll be offline most of today: I approve in advance whatever you decide because I trust your judgement. And because we're a few days from the deadline and I don't want to block anything here.
I have reverted the changed to the content of the homepage and put my additions into a dedicated page, so that this PR can focus on the blog (the CI seems stuck on "pending").
I hope I'm not too late.
@ -0,0 +1,20 @@
---
layout: '@layouts/Markdown.astro'
title: Download forgejo
Forgejo in Titlecase.
@ -0,0 +7,4 @@
```bash
wget -O forgejo-1.18.0-rc0 https://codeberg.org/attachments/071b3f92-0b6b-45a3-aa3a-6c11ae7fc91e
chmod +x forgejo-1.18.0-rc0
Personally, I'd advocate to u+x for security reasons.
@ -8,2 +10,2 @@
<div class="centered-content py-20">
<h1 class="pt-10 text-6xl">Forgejo - Beyond coding. We forge.</h1>
<div class="centered-content pt-10">
<h1 class="pt-10 text-6xl">Forgejo</h1>
I can't find the source, but I remember that h2 following h1 without text in between is discouraged by some typographic rule.
@ -30,0 +43,4 @@
</ul>
<p></p>
<a href="https://codeberg.org/forgejo/-/packages/container/forgejo/versions">Container image</a>.
<ul>
development (only a single p)
@ -0,0 +1,10 @@
---
layout: '@layouts/News.astro'
title: Hello world
pubDate: 2022年12月01日
Still Dec 1st?
That's a placeholder I assume.
@ -0,0 +2,4 @@
layout: '@layouts/News.astro'
title: Hello world
pubDate: 2022年12月01日
tags: ['blog', 'update']
We will likely revise these in the future.
@ -0,0 +3,4 @@
import FeedLink from '@components/FeedLink.astro';
const allPosts = await Astro.glob('./*.md');
function formatDate(s: string) {
Perhaps we should import the format object as well to ease maintenance?
@ -0,0 +5,4 @@
import type { MarkdownInstance } from 'astro';
export async function getStaticPaths({}) {
const allPosts = await Astro.glob('../*.md');
I would expect those to be filtered (could be just a reference to the same object. In Line 6).
The getStaticPaths is called by Astro to know which [tag] pages to generate.
When each page is generated, the Astro.params and Astro.props are populated with the fields returned line 20.
@ -0,0 +12,4 @@
const arr = acc.get(tag) || [];
arr.push(post);
acc.set(tag, arr);
});
unknown is preferred over any.
Yeah, I am sometimes unsure how to best handle typing. Could you open a PR with such better types?
I will do that when I come around looking at the repo locally.
I have some other tasks on my agenda before that can happen.
https://www.typescriptlang.org/docs/handbook/type-compatibility.html#any-unknown-object-void-undefined-null-and-never-assignability for reference.
@ -0,0 +34,4 @@
<main class="flex-auto">
<section class="centered-content py-12">
<h1 class="text-6xl font-extrabold">News tagged {tag} <FeedLink href={'../' + tag + '.xml'} /></h1>
<a href="../../" class="hover-underline">← all news</a>
Perhaps author as well?
In the future?
Can be easliy added as a frontmatter. Feel free to open a PR :)
I'll merge and address @Ryuno-Ki comments in a followup PR. My intention here is to allow @foxlet and other people willing to work on web design to move forward. It's a little cahotic but this is the last week-end and a few days from launch. That's my excuse 😊
@Ryuno-Ki I addressed your content related comments in #29
The code related best practices are still to be discussed. Would you be so kind as to copy/paste them in the relevant environment? (issue or another pull request or the chat or...).
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?