Originally created by @tanekere on GitHub (Feb 24, 2020).
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).
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.
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🌈
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tanekere on GitHub (Feb 24, 2020).
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.
@jamesmunns commented on GitHub (Apr 12, 2020):
If you're interested in building this, I'd be happy to take a look!
@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 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.
@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.