[GH-ISSUE #257] areWeEmbeddedYet.rs? #520

New Issue

GiteaMirror · 2026-04-15T06:12:20-05:00

GiteaMirror commented

2026-04-15 06:12:20 -05:00

Originally created by @tanekere on GitHub (Feb 24, 2020).
Original GitHub issue: https://github.com/rust-embedded/awesome-embedded-rust/issues/257

Just a suggestion. Let’s make this a arewe_yet website.

It would be a more “pragmatic rust” way of doing this. Generating markdown-based website from the readme won’t be hard and I am willing to do it. Forking another arewe_yet website that already has the ci setup would be good too.

Also the title is like that just for readability. I know snake case is better.

Originally created by @tanekere on GitHub (Feb 24, 2020). Original GitHub issue: https://github.com/rust-embedded/awesome-embedded-rust/issues/257 Just a suggestion. Let’s make this a arewe_yet website. It would be a more “pragmatic rust” way of doing this. Generating markdown-based website from the readme won’t be hard and I am willing to do it. Forking another arewe_yet website that already has the ci setup would be good too. Also the title is like that just for readability. I know snake case is better.

GiteaMirror closed this issue

2026-04-15 06:12:20 -05:00

GiteaMirror commented

2026-04-15 06:12:21 -05:00

@jamesmunns commented on GitHub (Apr 12, 2020):

If you're interested in building this, I'd be happy to take a look!

@jamesmunns commented on GitHub (Apr 12, 2020): If you're interested in building this, I'd be happy to take a look!

GiteaMirror commented

2026-04-15 06:12:21 -05:00

@niclashoyer commented on GitHub (Dec 9, 2020):

I had a go at it and forked arewewebyet: https://github.com/niclashoyer/areweembeddedyet

Two major problems arose:

the structure behind arewewebyet pulls all informations from crates.io, so the build failed for each package that was not yet published
parsing the readme was more difficult than I thought, so I just started with two topics, copying sections by hand: board support and hal implementations

The getting started section on the front page needs work, it still references the links related to web. But at least it's something 🌈

https://niclashoyer.github.io/areweembeddedyet/

Edit: I'm archiving this for now. While it would be nice to have a website like that, I think it is too complicated to get this in sync to the markdown file right now.

@niclashoyer commented on GitHub (Dec 9, 2020): I had a go at it and forked arewewebyet: https://github.com/niclashoyer/areweembeddedyet Two major problems arose: - the structure behind arewewebyet pulls all informations from crates.io, so the build failed for each package that was not yet published - parsing the readme was more difficult than I thought, so I just started with two topics, copying sections by hand: board support and hal implementations The getting started section on the front page needs work, it still references the links related to web. But at least `it's something` :rainbow: https://niclashoyer.github.io/areweembeddedyet/ Edit: I'm archiving this for now. While it would be nice to have a website like that, I think it is too complicated to get this in sync to the markdown file right now.

GiteaMirror commented

2026-04-15 06:12:22 -05:00

@berkus commented on GitHub (Nov 22, 2024):

A simpler way would be to use the website as either redirect or just renderer for the readme, although the value for such approach is greatly diminished.

@berkus commented on GitHub (Nov 22, 2024): A simpler way would be to use the website as either redirect or just renderer for the readme, although the value for such approach is greatly diminished.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-embedded-rust#520