RIOT-OS / riot-os.org

Sources of the RIOT website https://riot-os.org/.
4 stars 16 forks source link

community.html: update vision link #124

Closed maribu closed 7 months ago

maribu commented 7 months ago

Now that the vision is in the official home of doc, let's update the links.

github-actions[bot] commented 7 months ago

🚀 PR preview deployed to https://RIOT-OS-riot-os-org-preview-124.surge.sh

waehlisch commented 7 months ago

i think we can improve the integratoin. as the vision is now a md file, we can directly integrate the file into the website, e.g., by dynamically fetching from the git repo.

chrysn commented 7 months ago

An inclusion can be a good next step, although given the current drive to collect documentation centrally from the previously spread-out sources, that should go with some clear indication on where that "sits". (Like, a "view this as part of the documentation, or edit on GitHub" style link).

At any rate, this is a good fix.

maribu commented 7 months ago

I wonder if from a technical point of view it would make more sense to just move the markdown into this repo, then. Otherwise we would have to make sure that the website stays in sync with main repository.

Note that moving the markdown for the vision in this repo would have to be carefully synchronized with https://github.com/RIOT-OS/RIOT/pull/20498.

Maybe it would make sense to update the vision link as an intermediate step to doc.riot-os.org? IMO the RIOT wiki looks like it is on life-support and has been for quite some time, which is not an ideal first impression. Hence, I'd rather move the attention towards the Doxygen doc and away from the Wiki :)

miri64 commented 7 months ago

Otherwise we would have to make sure that the website stays in sync with main repository.

That is already the case, AFAIK, because of the CPU/boards lists.

waehlisch commented 7 months ago

Otherwise we would have to make sure that the website stays in sync with main repository.

That is already the case, AFAIK, because of the CPU/boards lists.

i don't understand this discussion. the content is automatically synchronized. and yes, we need to ensure that this tool chain work, but this is also true for the website infrastructure (or any other infrastructure) in general. the only important thing: automatic sync.

miri64 commented 7 months ago

i don't understand this discussion.

From my side, there is no discussion. I just wanted to clarify, that there is already a sync.

miri64 commented 7 months ago

So, shall we update the link for now and then update the page as suggested by @waehlisch in a follow-up?

maribu commented 7 months ago

Given that the vision on Doxygen has already been diverged from the one in the Wiki, how about updating this? I would also like to remove the copy from the Wiki once the links there are dropped.

miri64 commented 7 months ago

See #126