feat: reorganize community page

[SebastianBezold]

Description

This PR is a complete reorg of our community page. It is changing it from being a Docusaurus page to docs.

This comes with the advantage, that we can have a sidebar and structure the community section into multiple pages, making it easier to find content.

The PR introduces the following structure

Community:

• Intro -> Communication rules and contact channels
• Open Meetings -> List of all open meetings with info to schedule and how to join (new component)
• Meeting Minutes -> A link to a blog similar to News
• Products -> This is the product overview, that we already know, but as a separate page

Considerations / Discussion

As mentioned in the corresponding discussion, it could be useful to add downloadable .ics files for the open meetings. This is not yet included, but could be added.

Using the Docusaurus blog plugin for meeting minutes has a lot of advantages, like feed options, authors, sorting by date and so on. But is also comes with a drawback, that the blog does have its own sidebar. This somewhat breaks the navigation of the community section. A possible mitigation could be, to list it as last menu item in my opinion.

Related issue

fixes #523

Screenshots

Community section:

Open Meetings overview:

Meeting Minute Blog:

[FaGru3n]

Hi @SebastianBezold really great work!

one thing i regognized after rebuild form your branch on my local side... it seems that "Meeting Minute Blog" does not have the navigation sidebar on the left... or was that your plan?

[SebastianBezold]

Hi @SebastianBezold really great work!

one thing i regognized after rebuild form your branch on my local side... it seems that "Meeting Minute Blog" does not have the navigation sidebar on the left... or was that your plan?

Hi @FaGru3n,

yes, that is what I meant in the PR description under "consideration". Unfortunately, this is how the blog plugin works. So far, I haven't found a solution, where we can use the plugin, but keep the docs sidebar.
We could think about re-ordering the menu items, that it's at least shown in the end, or maybe move the meeting minutes to a completely separate top-level menu item

[FaGru3n]

We could think about re-ordering the menu items, that it's at least shown in the end, or maybe move the meeting minutes to a completely separate top-level menu item

i like the idea for completely separate top-level menu item "Open Meeting Blog" or "Open Office Meeting Minutes" something like that... 👍🏼

[stephanbcbauer]

i like the idea/poc ... will build it locally tomorrow and would like to give feedback afterwards. Thanks for your effort

[stephanbcbauer]

Thumbs up @SebastianBezold just built it locally and the new structure looks really great. I also like the tags in the meeting minutes. For the open meetings it would be cool to provide an ics file, or the meeting link.

Again. The new structure rocks.

[SebastianBezold]

Thumbs up @SebastianBezold just built it locally and the new structure looks really great. I also like the tags in the meeting minutes. For the open meetings it would be cool to provide an ics file, or the meeting link.

Again. The new structure rocks.

Cool thanks for having a look. I just pushed some last changes, that I wanted to do for this PR:

• Moving the meeting minutes to be the last navigation item -> I think this mitigates the disappearing navigation
• Moving community content to it's own directory -> not hidden in docs and URL is now /community instead of /docs/community
• Creating a dedicated sidebar config for /community
• Adding a client-side redirect from /community to /community/intro -> if you view the meeting minutes and just delete the last part of the URL, you'll be redirected to an existing page

What do you think: If enough people agree, I would merge this PR and work on integrating the Release Information and Changelog from "Versions" to the community section in a new PR

[stephanbcbauer]

Thumbs up @SebastianBezold just built it locally and the new structure looks really great. I also like the tags in the meeting minutes. For the open meetings it would be cool to provide an ics file, or the meeting link.
Again. The new structure rocks.

Cool thanks for having a look. I just pushed some last changes, that I wanted to do for this PR:

• Moving the meeting minutes to be the last navigation item -> I think this mitigates the disappearing navigation
• Moving community content to it's own directory -> not hidden in docs and URL is now /community instead of /docs/community
• Creating a dedicated sidebar config for /community
• Adding a client-side redirect from /community to /community/intro -> if you view the meeting minutes and just delete the last part of the URL, you'll be redirected to an existing page

What do you think: If enough people agree, I would merge this PR and work on integrating the Release Information and Changelog from "Versions" to the community section in a new PR

Last question. For the open meetings section, it looks right now more like documenting “regular” meetings. Could I also use this page to promote my (every 3 month meetings)? Refinement, Guardrails...

So what i mean for one year i would have something like 4 Guardrails, 4 Refinements... with the ics file to download and a meeting link :)

[stephanbcbauer]

LGTM ...

... Last question. For the open meetings section, it looks right now more like documenting “regular” meetings. Could I also use this page to promote my (every 3 month meetings)? Refinement, Guardrails...

So what I mean for one year I would have about 4 Guardrails, 4 Refinements... with the ICS file to download and a meeting link :)

[SebastianBezold]

LGTM ...

... Last question. For the open meetings section, it looks right now more like documenting “regular” meetings. Could I also use this page to promote my (every 3 month meetings)? Refinement, Guardrails...

So what I mean for one year I would have about 4 Guardrails, 4 Refinements... with the ICS file to download and a meeting link :)

I could think of two possible solutions:

• easy: Just add the appointments with the MeetingInfo component when you need them to be visible and remove them, when you think they are no longer needed. Potentially a lot of updates to the page, but nothing critical
• Enhance the component or create a wrapper, that takes a complete list of meetings and interprets the date, to only render the ones that are either regular, or in a specified time range (i.e. 3 months before it takes place and two weeks after it was held)

Can definitely work on that the next year 😁

[carslen]

LGTM. Reasonable changes

[FaGru3n]

LGTM