thinking about to integrate this web page additionally into riot-os.org, some black lines would be shown on black background. can we find a way to maximize reuse of the content?

thinking about to integrate this web page additionally into riot-os.org, some black lines would be shown on black background. can we find a way to maximize reuse of the content?

Given that we need to restructure the website anyways, if we want to integrate this Markdown into the website---currently the vision part there is a 1/3 page card type paragraph, this text would need something larger: couldn't we just use a white background for the vision section on the website? Would also symbolize a brighter future ;-).

couldn't we just use a white background for the vision section on the website?

right, the body part of the text could be in white bg color

then consider the comment as a reminder that we should reuse structured data as much as possible ;).

then consider the comment as a reminder that we should reuse structured data as much as possible ;).

I can add classes so that the style may be overwritten with external CSS. Have to think however, how to integrate this in the doxygen.

I added some minimal CSS and classes. However, how to change that externally (without doing a sed on the SVG) is anyone's guess. Most current browsers neither seem to support importing external CSS for imported SVGs or using the HTML's CSS for imported SVGs. :-/

Most current browsers neither seem to support importing external CSS for imported SVGs or using the HTML's CSS for imported SVGs. :-/

(And Doxygen's usage of XHTML doesn't make the situation any better)

Murdock results

✔️ PASSED

0dc04f6 doc: add graphic to vision page

Artifacts

Quoting @chrysn from matrix discussion:

Maybe even throw in a Zephyr and/or a FreeRTOS in as well? (it's 5 RIOTs, we'd still have 3/5 and thus the absolute majority in the embedded space)

I'd second this to emphasize on IoT interoperability, but it might need some highlighting/explanation in the text, too.

Quoting @chrysn from matrix discussion:

Maybe even throw in a Zephyr and/or a FreeRTOS in as well? (it's 5 RIOTs, we'd still have 3/5 and thus the absolute majority in the embedded space)

I'd second this to emphasize on IoT interoperability, but it might need some highlighting/explanation in the text, too.

I steered away from this, mainly because using foreign logos might raise some trademark issues (at least the Zephyr logo is a registered trademark, did not look up FreeRTOS). For the android logo, it does not seem to be the official one (see here, for Tux we might need to add a Copyright notice, if not already provided (will have a look).

Maybe it would even underline the intended message better to not pick zephyr/FreeRTOS/other concrete OS, but rather add some generic "other OS using standard internet protocols" node.

Maybe it would even underline the intended message better to not pick zephyr/FreeRTOS/other concrete OS, but rather add some generic "other OS using standard internet protocols" node.

If you provide me with a design for that: Can do! 😁

In the act of attributing the foreign logos correctly, I restructured the whole graphic to be more structural (any clipart is now its own defined path which then is only <use>'d in the graphic) and used only classes for styling. A “dark background” version of the graphic can be rendered by changing the stroke colors in #vision-division-line and .vision-house-line to white and the fill color for .vision-text to white. Just while writing this, I noticed that Tux might disappear with black background. Will provide a fixup for that!

Done, there is now a thin white border around tux.