4 ms·

Please see my explanation here: https://news.ycombinator.com/item?id=22038862 https://news.ycombinator.com/item?id=22038862

danShumway 7y ago
Even without adding a build step, would you be willing to add a <noscript> tag to your index.html that just linked to the Github repo in general? It wouldn't even need to be specific to each individual post. While admittedly some readers here are purely focusing on the irony of supporting "the primitive, simple case", for the most part non-JS users are willing to meet sites halfway on this. I'm totally fine manually navigating a Github repo to get at posts, I wouldn't be irritated at all in that situation, I wouldn't have even commented. Right now, your site offers nothing. Even just the below markup would have been sufficient -- it wouldn't need to be customized per-page. <noscript> <div>This site requires Javascript to function. You can view the raw text of posts on <a href="https://github.com/anderspitman/anderspitman.net">Github</a>.</div> </noscript> Just give users something, literally anything they can use to recover when your expected use-case fails.
- anderspitman 7y ago
  > Even without adding a build step, would you be willing to add a <noscript> tag to your index.html that just linked to the Github repo in general Absolutely! Should be working now (or as soon as CloudFlare cache is purged). Thanks for the snippet.
  - danShumway 7y ago
    Thanks a ton! It's showing up perfectly on my end. As long as I know how to get to the text in some format, I'm usually fine with the rest, and markdown is a format that's very easy to read.
    - anderspitman 7y ago
      Even so, I'm going to put in some effort to make text-only a 1st-class citizen.
- zzo38computer 7y ago
  I agree; that is good. (It is easy enough to find the post wanted from that.) I suggested to have a link (or just instructions, if you don't want it to be customized per post) for accessing the Markdown code for the specific post. However, a link to the Github repository also works perfectly OK, so I am not complaining.

danShumway 7y ago

Even without adding a build step, would you be willing to add a <noscript> tag to your index.html that just linked to the Github repo in general? It wouldn't even need to be specific to each individual post. While admittedly some readers here are purely focusing on the irony of supporting "the primitive, simple case", for the most part non-JS users are willing to meet sites halfway on this. I'm totally fine manually navigating a Github repo to get at posts, I wouldn't be irritated at all in that situation, I wouldn't have even commented. Right now, your site offers nothing. Even just the below markup would have been sufficient -- it wouldn't need to be customized per-page. <noscript> <div>This site requires Javascript to function. You can view the raw text of posts on <a href="https://github.com/anderspitman/anderspitman.net">Github</a>.</div> </noscript> Just give users something, literally anything they can use to recover when your expected use-case fails.

anderspitman 7y ago
> Even without adding a build step, would you be willing to add a <noscript> tag to your index.html that just linked to the Github repo in general Absolutely! Should be working now (or as soon as CloudFlare cache is purged). Thanks for the snippet.
- danShumway 7y ago
  Thanks a ton! It's showing up perfectly on my end. As long as I know how to get to the text in some format, I'm usually fine with the rest, and markdown is a format that's very easy to read.
  - anderspitman 7y ago
    Even so, I'm going to put in some effort to make text-only a 1st-class citizen.
zzo38computer 7y ago
I agree; that is good. (It is easy enough to find the post wanted from that.) I suggested to have a link (or just instructions, if you don't want it to be customized per post) for accessing the Markdown code for the specific post. However, a link to the Github repository also works perfectly OK, so I am not complaining.