Helpful (?) diagram on landing page #70

Open
Firobe wants to merge 1 commits from diagram into main
Firobe commented 2025-01-25 19:32:21 -05:00 (Migrated from gitlab.com)

It was a bit hard to wrap my head around all of the terminology at first, so here's a little diagram I would've loved to have 😁

diagram.svg

It might only make sense to me, feel free to ignore the PR if so. This PR puts it on the landing page, but of course it could be somewhere less visible too.

It's made with Excalidraw, so you can just drop the SVG there and edit it if any modification is needed. Seeing that this renders pretty bad with a dark theme, we could also do away with the transparency and just export to PNG.

It was a bit hard to wrap my head around all of the terminology at first, so here's a little diagram I would've loved to have :grin: ![diagram.svg](/uploads/b19aaf5383ca663b7cb2949cecb08bf9/diagram.svg) It might only make sense to me, feel free to ignore the PR if so. This PR puts it on the landing page, but of course it could be somewhere less visible too. It's made with [Excalidraw](https://excalidraw.com), so you can just drop the SVG there and edit it if any modification is needed. Seeing that this renders pretty bad with a dark theme, we could also do away with the transparency and just export to PNG.
hypevhs commented 2025-02-11 15:58:34 -05:00 (Migrated from gitlab.com)

I like the idea of a diagram. Do you think we could leverage hugo-book's MermaidJS support here, so that we don't have to deal with separately maintaining an SVG?

Of course, we'd use the markdown-compatible shortcode notation {{% %}} instead of the {{< >}} as in the linked example.

I'd also like to see if we can't link to this diagram, if not embed it directly:
https://gist.github.com/TayouVR/a48b37bbc45765b8f9ec8a231c9f101c

I like the idea of a diagram. Do you think we could leverage [hugo-book's MermaidJS support here](https://hugo-book-demo.netlify.app/docs/shortcodes/mermaid/), so that we don't have to deal with separately maintaining an SVG? Of course, we'd use the markdown-compatible shortcode notation `{{% %}}` instead of the `{{< >}}` as in the linked example. I'd also like to see if we can't link to this diagram, if not embed it directly: https://gist.github.com/TayouVR/a48b37bbc45765b8f9ec8a231c9f101c
hypevhs commented 2025-02-11 16:18:20 -05:00 (Migrated from gitlab.com)

The big diagram is licensed under CC0, so we should use it. Needs updating to include XRizer.

The big diagram is licensed under CC0, so we should use it. Needs updating to include XRizer.
hypevhs commented 2025-04-10 22:24:20 -04:00 (Migrated from gitlab.com)

Coming back to this. I tested out the big diagram. It can render on the wiki fine but it's difficult to read, both in terms of tiny text, and the sheer size/complexity of it. Putting it aside for now. I would like to use OP's diagram but rewritten in Mermaid so we can easily update it.

Coming back to this. I tested out the big diagram. It can render on the wiki fine but it's difficult to read, both in terms of tiny text, and the sheer size/complexity of it. Putting it aside for now. I would like to use OP's diagram but rewritten in Mermaid so we can easily update it.
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin diagram:diagram
git checkout diagram
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LinuxVR_Adventure/lvra.gitlab.io#70