Hi,
Sorry for spamming again with a screenshot of another site. But some UX in this API doc is so much better and I believe we can get some design ideas from them to increase the readability of Rust API docs.
Unfortunately I am not a front-end dev and bit busy with the current job(even on some weekends) to contribute on this. I shared my idea here because I believe it's worth to share this to improve the readability of Rust API docs.
Also I am not an employee/ user or any other person who relates to that editor and have no intention to share it or market it. Also I know that a new suggestion has a less value without having a proper implementation road map :( But please check the screenshot and the link if it's okay.
I found they are using open source project https://hexo.io/ and https://www.npmjs.com/package/umberto to map contents from different repos, but don't know that their website code is open source(It will not be mostly)
Make a blog with existing methods with static site generator, where you can host them on gh-pages; many of them have free themes. Start writing about what you've learned, or you can teach others or whatever you think is worth a post. Perhaps make a "project" category for all the projects you've contributed to, and highlight the ones you're proud of.
Hi,
I would like to suggest to add a "Table of contents" section for each page on doc(book). It might be helpful to increase the accessibility and easier to identify the contents of the page.
ex:
All are open source projects. Unfortunately I am not a front-end dev and bit busy with the current job :(
[] call ski renter shop
[] contact customer service for shirts
[] contact customer service for battery
[] contact customer service for pants
[X] pick up dry cleaning
[X] basketball training
[] install hexo
[] uninstall jekyll
[] start reading programming book ch2
rest:
[X] watch tv show
habits:
[] meditate
[] recovery exercises
I had friends over for wine and movies, and I didn't do much else. It was really fun, so I think it was worth it. Try to catch up on work over the weekend (although unlikely). Maybe I'll stay up a little later and work on this stuff
I recently created my static blog site using hexo.io. It’s command line driven and Markdown based. One comnand to add a new Markdown file, one to build, one to deploy to DreamHost.
> PHP na który byś mógł sobie wrzucić WordPressa
jezu, a kysz
zaproponuję rozwiązanie tańsze, łatwiejsze w utrzymaniu (aczkolwiek wymagające zapoznania się z gitem - ale skoro typ wyjeżdża tu z PHP i bazą danych to powiedziałbym że mniejsze zło), to GitHub Pages (bonus: wspierają podpięcie do jakiejś proper domeny) i ewentualnie jakiś generator statycznych stron, np pelican albo hexo jeśli chcesz postawić blogasek
The runtime is exactly why I dismissed Gatsby on initial examination — most public-facing websites (the niche that's occupied by WordPress et al.) probably don't need a full-blown framework. Not that 60kb is huge, I just feel it's not necessary.
To be fair, there's also a bunch of node-based SSGs — https://hexo.io/ is one example. And fetching data is not that hard without generator-specific code.
I do this using Hexo. Mainly because it is written in JS and I like that about it.
You just run the init script, put all posts in a folder (maybe add some meta data as a yml frontmatter) and run the generator.
It is a reasonable amount of work to set up a Travis CI integration for GitHub pages if you have never done it and super easy to set it up for Gitlabs pages. They even have a repo you can fork/clone to get started with a Hexo based blog.
> I prefer it because I am one of those people who have enormous trouble getting Ruby to run properly.
What OS, if you don't mind me asking? Windows? I've always had troubles with Ruby on Windows, but on Mac it's always been pretty easy through things like brew.
Another JS/Node based static site generator is Hexo. When I was picking them a while ago I went for the most popular one, and at the time I think Hexo had that position on lockdown. Not sure what it's like now.