Skip to content

Commit c4908e8

Browse files
committed
Renove old dummy. Add link. Improve wording.
Signed-off-by: Kurt Garloff <kurt@garloff.de>
1 parent c87c122 commit c4908e8

3 files changed

Lines changed: 17 additions & 21 deletions

File tree

blog/2022-10-28-first-blog-post.md

Lines changed: 0 additions & 8 deletions
This file was deleted.

blog/2026-01-22-introducing-docs-blog.md

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,31 +11,35 @@ Previously, we had [a project web site](https://scs.community/) that covered man
1111
areas of work that was done in the SCS project until it was successfully completed
1212
at the end of 2024. It covered the standardization work as well as the development
1313
of the reference implementation and also had a vast collection of links and technical
14-
content, most of which was related to the reference implementation. For newcomers,
15-
it was somewhat hard to distill the various aspects and goals.
14+
content, a lot of which was related to the reference implementation. For newcomers,
15+
it was somewhat hard to distill the various aspects and goals of SCS though.
1616

1717
With the end of the funded project, we split the activities into different organizations
1818
with distinct goals:
1919

2020
1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/network/) is
21-
responsible for governing the standardization process. While it pull significant input
22-
from the various software projects that belong to the SCS universe, it is neutral towards
21+
responsible for governing the standardization process. While it pulls significant input
22+
from the various software projects that belong to the SCS ecosystem, it is neutral towards
2323
them beyond the preference for standards compliance. This reflects that there can and
2424
ideally should be several implementations for a standard.
2525
The [new website](https://sovereigncloudstack.org/) focuses on the standardization.
2626
2. The SCS community consists of individuals and organizations that develop, support,
2727
test, use, or otherwise contribute to the software and standards that implement and
2828
codify SCS. The community elects a [project board](https://docs.scs.community/standards/scs-0005-v2-project-governance)
29-
that organizes and motivates contributions.
29+
that organizes and motivates contributions. The work of the community is mainly visible
30+
on the [Documentation web site](https://docs.scs.community) and the
31+
[github site](https://github.com/SovereignCloudStack/).
3032

3133
## Blog articles
3234

3335
Blog articles with technical content relating to a specific implementation (or a set
34-
of implmentations) are not a great fit for Forum's web site.
35-
The good news is that the SCS project also has a rich
36-
[Documentation site](https://docs.scs.community/) which is architected in a way that
36+
of implementations) are not a great fit for Forum's web site.
37+
The good news is that the SCS project's rich
38+
[Documentation site](https://docs.scs.community/) is architected in a way that
3739
it assembles documentation from various places. Unlike the Forum, it does not need
3840
to prioritize neutrality as top priority, but benefits and prefers those projects
3941
that contribute useful content to it.
4042

41-
We have decided to use docusaurus' blog feature to publish blog articles here.
43+
We have decided to use docusaurus' blog feature to publish blog articles
44+
[here](https://docs.scs.community/blog/). We will migrate some content over
45+
and appreciate contributions.

docusaurus.config.js

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -199,10 +199,10 @@ const config = {
199199
{
200200
title: 'More',
201201
items: [
202-
// {
203-
// label: 'Blog',
204-
// to: '/blog'
205-
// },
202+
{
203+
label: 'Blog',
204+
to: '/blog'
205+
},
206206
{
207207
label: 'GitHub',
208208
href: 'https://github.com/SovereignCloudStack/docs'

0 commit comments

Comments
 (0)