@jensimmons

Thanks so much for all your work!

For me, clear, concise docs that assume nothing and tutorials that are focused going step-by-step including all setup commands.

There’s nothing worse than following examples in the docs that don’t work.

Start with the basics but have really complete detailed docs when I’m ready to dive in further.

@jensimmons Good and tough questions for me to answer, as a 100% self-taught in the aughts coder who wears most of the hats at my company and rarely has time to do more than, e.g., search Stack Overflow for answers to problems I face when maintaining and improving our PHP+MySQL-based products.

I try to keep up with RSS feeds on sites where I see interesting and helpful topics (and that don’t make me feel inferior for not having a complicated build process with ten different plugins for the JavaScript-first/only approach du jour). I like *reading* articles with plenty of concise content. Tips & tricks that work broadly on modern browsers are the best; articles that require in-depth knowledge of the JS-library-du-jour are intensely frustrating. Developers dismissive of others lacking Wizard-level abilities make me curse, and their pervasiveness never seems to abate :(

Wave a magic wand and make documentation accessible and my life would be brightened immeasurably.

@jensimmons A compact introduction to CSS for people who specialize in non-CSS programming:
* How to organize CSS
* Everything that’s needed for writing solid user interfaces
* Much of the advanced stuff (e.g. animations) can be omitted

I find much of the CSS content too high-level and too low-level at the same time.

@jensimmons First, I could use a podcast about what's ahead in the web.

Other stuff includes
1. I dig videos, I have a kid, and 40+ hours of work, stuff I can watch while doing dishes, would be rad.
2. I super dig @astro's blog, I also https://bradfrost.com/, and @shoptalkshow .
3. It's hard to build things offline first. Workbox is great, but there's not a great integration for Astro or Wordpress that I know of.
4. A Safari youtube/podcast channel that I hear what your devs are working on.

@jensimmons I mostly hear about new stuff because @Meyerweb boosted something (like this post).

For the very latest I like to read the readme/explainer in the spec suggestion repo, and the resulting PR/issue(s). The real spec feels like it's more for browser vendors, but nice to have as a reference.

For existing stuff I go to MDN.