sovereigncloudstack / website Goto Github PK

The links to the release notes on github is broken in the announcement blogposts due to the repo moving.

In the old times (R), we built the web page by having a cron job on the web server, pulling (anonymously) from the public github repo, building the web page locally (if there was any change, otherwise the make command did nothing).
We could go back to this mechanisms, setting up a container with the jekyll build stuff on the web server.
Advantage is that we don't need to trust github with the credentials.
Disadvantage is that it's a pull mechanism, so we have 5min latency for publishing changes to the web page.
(We could trigger pulls from a github action of course ... could do this in an unauthenticated, rate-limited(!) way even, or using a port-knock scheme with a low-value secret.)
Or some middle ground where we store the github-action produced build results somewhere to pull them from the server.
(The server will need to trust the build result, so we need some trusted place for the build results.)

This should ont prevent us from merging this change though.

Originally posted by @garloff in #281 (comment)

As a group, I want to have multiple names and avatars shown in a commonly written blog post.

We should replace all occurrences of BMWi with BMWK. Moreover, the "funded by the BMWi"-Logo needs to be replaced by a newer version as soon as it gets released.

As a website maintainer, I want to know whether my branch builds successfully. Moreover, I want to be able to push my staging changes to GitHub pages.

We thus need to

• split the current build and deploy action to a
  • build action which commits and pushes the built website into the directory /_site,
  • (maybe some further Lighthouse checks),
  • deploy the main branch to our webserver (if build process and checks were successful).

Please don't forget to create a symlink in the de subfolder. Otherwise, the article won't be displayed on the German website.

I would have overlooked this, thanks.
(Maybe we should have functionality to always link an English article when no German version is available?)

Originally posted by @garloff in #440 (comment)

This project seems to more or less public related, so I would like to suggest some improvements.

I suggest the following improvements for the menu/header:

• Add menu point naming, and don't rely on the tool-tip of the links.
  • Tool-tips are not visible on mobile devices.
  • They are only shown if you hold your mouse still for a while, which is a bad UX.
  • They cannot not be read out by text-to-voice programs, for instance for disabled humans.
• Behind the tel-href is no telephone number. Only in the tool-tip is the number visible.
• Separate internal links from external Links visually. Maybe open external links in _blank. Users usually want to stay on one website until they change to foreign linked sites eventually.
• On desktops, the logo seems to big, on mobile the logo is to small 😄

Here are some ideas for the rest of the page:

• Make the website more accessible for disabled people.
• Add the usage of the Cloudflare CDN to the Datenschutzerklärung/data privacy statement (important IMHO).

Cheers 🍺

We have collected the various talks our community is giving at the OpenInfra Summit 2022 on our blog: https://scs.community/2022/06/02/scs-at-oifsummit2022.

Please upload - if you like - your slides until Monday evening to our website repository and I will link them to the corresponding schedule item in our blog post. This will boost the traffic on our website and hopefully on our social media accounts.

It would be great if you create a huge QR code at the end of your presentation so that visitors can directly receive the shown slides deck. The deep links are already available.

Thank you for contributing to OIF Summit and being part of our joint actions at this exciting event. Looking forward to seeing you next week!

@fkr @berendt @horazont @garloff @matfechner

The deadline for VP09c ends tomorrow. We should close the tender on our website accordingly.

The header in the right column should read (German) ...

For ease of reference it would be great if https://scs.community/de/tenders/ could list the winning companies for each successful tender. Maybe also add their profiles to https://scs.community/de/partners/ or to a dedicated page.

In the list of German Press Releases
https://scs.community/de/press/
the following links lead to a 404
4.Juni 2020 Plusserver
9.Juli 2020 WDR5
7.September 2020 nerdzoom

Maybe it is useful to have a static website build and pipeline for the website, e.g https://gohugo.io ?

/cc: @garloff

See reference in

Originally posted by @itrich in #448 (comment)

We should improve the website performance and gain a performance index of at least >90 at https://web.dev/measure/.

Some ideas to accelerate page load:

• Reduce image size with a corresponding jekyll plugin (e.g. valerijaspasojevic/jekyll-compress-images or envygeeks/jekyll-assets)
• Minify documents and text-based assets
• Make extensive use of lazy-load (especially on long pages!)
• Investigate benefits of using a CDN (see discussion #300)

Any further suggestions?

As the number of social icons grows, the navigation menu looks quite dense on mobile phones. I suggest to move the social icons to the menu.

Twitter:

LinkedIn:

We want to lead as many users as possible to subscribe to our announce mailing list. We thus should have a form or highlighted button on the landing page redirecting users to the subscription page of this mailing list.

I already tried to implement a simple form in the footer but struggled with the CSRF-Token check implemented by Django, see https://lists.mailman3.org/archives/list/[email protected]/thread/KAPI35V45PJQ7ORS6HJQVS3VTP4ZI5RE/

We should add an icon next to Twitter, LinkedIn and GitHub linking to our new Matrix Community space.

We should not order the press articles alphabetically, but put the newest first and oldest last.
This way, returning readers can actually see what's new.
We could prefix a release date as well ...

We should care more about the accessibility of our project's website and have automated a11y checks within our pipeline: https://github.com/A11yWatch/github-action

At the moment, we're creating multiple files to generate an output like https://scs.community/itrich. We should rather switch to collections to only have one file per employee/partner/etc.

The link on the German jobs page for Cloud Monitoring and PO Standards is invalid.

When I'm in the contact details of a person, I can only copy the link but not the text.

How to reproduce:

1. go to https://scs.community/kronlage-dammers
2. try to copy the phone number BUT not the link, just the number ;)

Browser: Firefox

/remind-me 2023-04-10 T12:00+01:00 Close SCS-VP03

When trying to build the website on a freshly cloned repository, make .dep exits with Error 1:

Makefile:17: .dep: No such file or directory
./scripts/collectdeps.py build/index.html.de build/index.html.en build/.htaccess build/robots.txt build/sitemap.xml build/blog/20200915-garloff-ovh.html.de build/blog/20200915-garloff-ovh.html.en build/test.html.de build/test.html.en >.dep
ERROR: tmp/logos.html not readable 
Makefile:15: recipe for target '.dep' failed
make: *** [.dep] Error 1 

Citynetwork is Cleura and ask for new logo at our website

Gaia-X is now the official wording.

Throughout the last year, numerous times people who tried to get an idea of what SCS is went to our website and did not understand the value proposition of SCS.
Imho we lack a tl;dr of what SCS (the project, the standard as well as the reference implementation) is and what it offers.

/remind-me 2023-03-22 T12:00+01:00 Close SCS-VP04

As the number of posts rises, we will certainly need Pagination for the news site.

General question: Would you prefer one pagination per section (announcements, blog posts, media coverage, etc.) or single pagination for the whole news page?

The telephone number in the footer needs to be replaced by the new number in Berlin.

Tel.: 030 300 149 3377

Our security advisory for log4j says
"Please contact the SCS project management team at project at scs dot sovereignit dot de to ask security questions or report security issues."
which is good, as we at least clearly communicate the communication channels.

Better would be to have a security-specific address (alias) that also offers encrypted contact options (PGP and maybe additional options). And to use a standardized way to advertize this using the security.txt standard.
See https://datatracker.ietf.org/doc/html/draft-foudil-securitytxt-12 and https://securitytxt.org/ .

A link within the bibliography of our last blog post on digital sovereignty breaks the overall design. This is probably related to inukshuk/jekyll-scholar#30

We should have a look at the different solutions by @mfenner et al.

Betacloud Solutions was renamed OSISM some time ago.

We should switch to German if the user's browser prefers German. See https://meumobi.github.io/jekyll/2019/06/05/multi-languages-with-jekyll.html#auto-switcher

While we have a very good definition of digital sovereignty (in our paper on the four dimension) and blogposts, it misses from our website in a clear and direct way. We should add it.

we need a short announcement that SCS R4 will be released on the 22.3.23

When we add a social media image in the blog post this should be displayed in the post itself as well.
Discussed with @itrich in #343

Please switch the primary branch to be 'main' instead of 'master'.

The navigation menu should collapse to a menu button on mobile devices for a cleaner look of the website.

I recommend to keep the most important social icons within the navigation menu, e.g. something like this:

We should fix the SEO tag for title and remove it completely from the jekyll-seo-tag template.

As project team, we want to highlight new blog posts on the landing page.

I suggest to

• add a boolean property featured to the front matter of blog posts and announcements,
• add a Carousel to the landing page in the upper third,
• and render the last 3 (or maybe 5?) featured posts and announcements in the Carousel with their related hero image.

    > > node_modules folder should be added to gitignore otherwise nice!

I'd disagree. In order to reduce build time in our GitHub Actions, we've pushed all node modules directly to the repository. Especially when running build tests with every push, this will shred our free quota of using GitHub Actions.

Ok I see, but isn't this an antipattern, especially if there are more modules being added overtime? The git history will be inflated with peer dependencies of dependencies which might led to security issues aswell as maintenance issues and potential bigger scale merge conflicts.

Originally posted by @maxwolfs in #417 (comment)

At the moment, the whole repository is licensed under MIT, which is still valid for the source code part of the containing files. However, we should release the creative content (especially our blog posts) under a CC license.

See the discussion at SovereignCloudStack/docs-page#4 for reference.

There is a new Gaia-X logo. This should be used from now on.

https://www.gaia-x.eu/img/logo.svg

We should update our third-party components (Bootstrap, jQuery, leaflet, etc.) and add Dependabot to this repository.