5 ms·

It's a bit puzzling that the GitHub readme has more information about how to use the tool than the website. I don't know what to take away from the single scree

It's a bit puzzling that the GitHub readme has more information about how to use the tool than the website. I don't know what to take away from the single screenshot. Maybe it would be helpful to record an animated GIF or a screencast to demonstrate it in action?

AdmiralAsshat 7y ago
The GH readme file is alot easier to fix than a website. It likely evolves naturally as people open issues to complain that a command doesn't work or that instructions for platform X are missing. The author reads the issues on GH, commits fixes on GH. It's easy to forget the website part.
- cloudhead 7y ago
  Pretty much this - I copy stuff over from the README once in a while. I guess the website could benefit from having some of the usage instructions though.
- yellowapple 7y ago
  > The GH readme file is alot easier to fix than a website. With a static site generator, the GH readme file can be the website.
jgtrosh 7y ago
> I don't know what to take away from the single screenshot. Maybe it would be helpful to record an animated GIF or a screencast to demonstrate it in action? Agreed. Vi-style editing of pixel art is a new concept that needs to be demonstrated first and foremost to drive this project. Kakoune is another software for which the uncommon editing paradigm is one of the main features, and it is presented rather well on their main page [0]. A set of animated demonstrations of the editing paradigm comes before a display of the general appearance of the software in realistic contexts. [0]: https://kakoune.org/ https://kakoune.org/
airstrike 7y ago
I immediately ctrl+f'd "doc" and was shocked to find no matches. How exactly are "advanced users" supposed to learn the "vi-like" commands?
curioussavage 7y ago
might still not be ideal but it a bit too hard to make the readme be the website too. Or embed it in the website

AdmiralAsshat 7y ago

The GH readme file is alot easier to fix than a website. It likely evolves naturally as people open issues to complain that a command doesn't work or that instructions for platform X are missing. The author reads the issues on GH, commits fixes on GH. It's easy to forget the website part.

cloudhead 7y ago
Pretty much this - I copy stuff over from the README once in a while. I guess the website could benefit from having some of the usage instructions though.
yellowapple 7y ago
> The GH readme file is alot easier to fix than a website. With a static site generator, the GH readme file can be the website.

jgtrosh 7y ago

> I don't know what to take away from the single screenshot. Maybe it would be helpful to record an animated GIF or a screencast to demonstrate it in action? Agreed. Vi-style editing of pixel art is a new concept that needs to be demonstrated first and foremost to drive this project. Kakoune is another software for which the uncommon editing paradigm is one of the main features, and it is presented rather well on their main page [0]. A set of animated demonstrations of the editing paradigm comes before a display of the general appearance of the software in realistic contexts. [0]: https://kakoune.org/ https://kakoune.org/

airstrike 7y ago

I immediately ctrl+f'd "doc" and was shocked to find no matches. How exactly are "advanced users" supposed to learn the "vi-like" commands?

curioussavage 7y ago

might still not be ideal but it a bit too hard to make the readme be the website too. Or embed it in the website