You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "getting started" section starts with a huge chunk of text (open on your phone for feels-like-endless scrolling experience). I like that text, but when i go to getting started, i want to get started, not read history. I might not have that 5 minutes and the patience to brew a cup of coffee first, i want to see how it works. So I suggest to move that text to its own section entitled "The story so far", "Once upon a time" or the like. It would also be nice to have some visual in that "Bleiwüste".
The Github link should be in the footer.
The support section should be linked. There is no hint there on how to actually get to the listed stuff.
Static info which is not generated from inline documentation like getting started should be in markdown because editing content in html is pain. that introduces some styling constraints, but with documentation i'd say easy contributing goes first.
it might help to seperate raw content and build into different branches or repositories so people can contribute fixes to the content without having to run the build process.
it looks like some of the content was originally written in markdown and then pasted into the html:
okay, that's it for now. let me know where to start and where you disagree.
The text was updated successfully, but these errors were encountered:
Hey @filtercake,
thanks for helping out on a topic, people (including me) try to avoid most of the time.
Here are my thoughts, I´m happy to get some help, so yeah, lets discuss :)
Totally agree with the 1st point, lets replace the merch section with TSSF or so & link it from a small prelude section out of get started.
Do you think the link needs to be in the footer, I mean it's present on the homepage?!
The support section should be linked. Agreed. Go go go ;)
Static info which, tough one. Wouldn't touch that yet, maybe later (build chain is unstable enough)
it might help to seperate raw content; I would rather add more & more concrete docs on how to get to the content
it looks like some of the content; yep, if you feel like you would be able to help with that. Please go ahead!
some notes:
okay, that's it for now. let me know where to start and where you disagree.
The text was updated successfully, but these errors were encountered: