3 ms·

There's a concept called "Every Page Is Page One": https://idratherbewriting.com/trends/trends-to-follow-or-forget-every-page-is-page-one.html https://idrather

There's a concept called "Every Page Is Page One": https://idratherbewriting.com/trends/trends-to-follow-or-forget-every-page-is-page-one.html https://idratherbewriting.com/trends/trends-to-follow-or-for... An attempt to meet the needs of people following search engine links right into the middle of documentation. This is where I wonder if an A.I. could provide missing introductory context, based on the conversation that got you to the doc.

hinkley 2y ago
That was effectively the problem. There are pages that describe concepts but search engines take you right to the API which introduces related jargon words that are neither defined nor hypertext. But I fear this is a bridge too far for a domain that didn’t bother making DevEx a thing until a few years ago.
- euroderf 2y ago
  Good point about jargon. So every page needs a link to (or a listbox of) glossary.
  - hinkley 2y ago
    Or just use industry standard words and introduce the jargon deeper down. Like in function arguments.