guide.elm-lang.org VS devdocs

If you look at the repo for that guide (https://github.com/evancz/guide.elm-lang.org), the description and README clearly state that this is his book on learning Elm, so for me it makes complete sense that it is in the I-form. Maybe the fact that it's linked from the official Elm page without any mention of that causes a feeling of disconnect for you.

An Introduction to Elm (HTML)

I am continually perplexed how poor the official documentation is for Elm (https://guide.elm-lang.org). I love the language, I really enjoy working with it, but where does one go to see the complete API? In particular right now I'm trying to find more on setting various events and accessibility attributes in forms, and this is all I see on the official docs: https://guide.elm-lang.org/architecture/forms.html. Not even a label example on a form page? How is this considered good documentation for a language that has been around for a decade? Is there some secret handshake I need to learn to get access to more in-depth documentation of the language?

I think a good first step would be getting familiar with functional programming in general. I recommend working through the Elm Guide, which will get you acquainted with functional programming idioms and working with immutable data. Then, move on to an introductory Haskell resources, such as Write Yourself a Scheme in 48 Hours. After that, hit up CodeWars and start solving puzzles in Haskell.

I think The Elm Guide does a very good job.

Check out Elm. Page 4 of the intro guide I linked offers something close, which you could build upon to create what you want there.

My advice is to follow the elm official guide. Anyway, any doubt you may have, ping me (gabber) on Elm official slack or write to #beginners channel!

This guide will help you learn and migrate to Elm with assumption you already know the basics of React. The Elm guide is great and will give you a thorough understanding of everything you need to know, in a good order.

Elm Introduction: https://guide.elm-lang.org/

The official Elm guide

> I've started to preface all python searches with 'site:python.org'

You might find DevDocs to be useful: https://devdocs.io/

DevDocs - Aggregates documentation from various sources into a single, easy-to-navigate interface, covering frontend and backend technologies. DevDocs

DevDocs, an offline API documentation browser, supports multilingual, offering developers a quick and efficient way to access tech docs. From front-end to back-end and mobile development, it integrates official documentation, providing a sleek, user-friendly interface.

Environmental lighting conditions rule the day! I have astigmatism and I prefer bright backgrounds; #000 text on #fff backgrounds works great for me, but that's because I work in a room lit by a 250W 30,000 lumen corn-cob LED bulb[0] that makes my small office as bright on the inside as the shaded ground from a tree on an overcast day (which is quite bright compared to usual indoor lighting). In a room that bright, high contrast text works great and is highly readable, with "dark mode" often looking washed out and muddy. Even small reductions in contrast (such as what https://devdocs.io does with text of #333 in light mode) can make me notice and wish for greater contrast.

[0] - https://www.benkuhn.net/lux/

Here's how to add a new scraper: https://github.com/freeCodeCamp/devdocs/blob/main/.github/CO...

Or open an issue and wait for somebody else to implement the scraper.

Imagine a single, intuitive platform where you can access comprehensive documentation for a vast array of programming languages, frameworks, libraries, and tools. That's the magic of DevDocs. This exceptional resource eliminates the frustration of juggling multiple tabs and websites in your quest for information. DevDocs brings everything together into one easy-to-use interface.

Mosh for a stable connection, Offline documentation such as msdn, wikipedia (via kiwi etc), zeal for local access to https://devdocs.io/; Self host tabby for ai autocompletion. For many shell programs check what mulinux was using back then, and what are the modern replacements such as elinks instead of links. Mutt for mail, for irc doesn't matter much, use a desktop one but setup a bouncher on a vps, I used to have one on a raspberry pi 1, you can use rss reader for reddit (not sure if still works) and blogs

1.DEVDOCS.IO: -- DevDocs.IO