Samuel
@samuel.fm
10 31 226 10 31 226
Henry Phillipsone must imagine developers happy
4
(dialupready)how i read docs
If it’s a GNU-style doc with a single page option: open the page and search for keywords
if there is any kind of navigation whatsoever: go to some LLM and ask it the keywords and then find the section of the doc
every doc should be forced to have a keyword glossary section
1 2(dialupready)tailwind docs are an example, i don’t even use tailwind, i just want to see the css they used and I can’t even use their search to immediately get at the answer because they shove their actual class list into another box with internal scroll i have to look at
tailwindcss.com/docs/flex-ba...
flex-basis - Flexbox & Grid
Utilities for controlling the initial size of flex items.
tailwindcss.com
Robeleader🏴☠️More like "writing the documentation for a service that's been in use by production for years but has never been documented
1
Maciek ChmuraAlways 😅
Now reading: https://inertiajs.com/forms
1Maciek ChmuraI was there 🥹