Email or username:

Password:

Forgot your password?
Top-level
mikkel

@bw Another thing: Illustrations, even tiny ones that can be understood at a glance, help a lot. Example: A simple “this is the file extension” arrow pointing to the file extension of a file name.
Going without illustrations requires a lot of confidence that you understand what the author is writing about, and faith that it will work. The less “faith” and more “proof” (e.g. visuals) there is, the easier it is to follow along. Seeing is believing etc.

3 comments
mikkel

@bw Sorry for the maybe unprompted criticism… know that I’m writing all this because I think you are on the right track and want this to succeed!

I really wish I found this resource when I was 15 and learning to host my first shitty js calculator. Neocities and the other recommendations are 10 times better than what I stumbled into when I googled “free html host” and now I have a good article series to recommend to normal people :^)

mikkel

@bw I also read it again, and I think you did actually tackle some of my points somewhat in the article (e.g. you mention where a file extension is for a file), but I think really hammering stuff like this home for people who are “not in tech” is important if their accessibility specifically is what you’re aiming for.

Blake Watson :prami:

@mikkelens I appreciate this feedback. Yeah I mentioned briefly in the introduction that knowledge of using a computer and ability to create files and folders were prerequisites of the book. That being said, I agree that some more discussion it would help. I'm not sure if I want to write something and host it myself, or maybe just point people to some kind of primer on creating files and folders.

Go Up