-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't use flat lists of links in container topics #7661
Comments
Hi Laura- Ive rewritten this topic to make it less like a KC-style container topic: Initially, I rewrote it to have the three alternatives in a single paragraph with inline links. But I think since there are three specific frameworks that are summarized relevant to OL, the bulleted list improves readability and is also more succinct. I understand this isnt that different than what I had before but it is also no longer just a flat list of topic links. The only other container topic we have that uses this pattern is the Observability parent topic, which Im going to rework per #7659. |
I think that's much clearer. At risk of being a pain, I wonder if it's a bit too negative about REST? Also, I wondered if the GraphQL one could be framed more in terms of what it can do rather than just what problem it resolves (eg "returns just the data required, which addresses the under-/over-fetching problem" - badly worded I know). |
I guess we dont want to throw REST under the bus :) I added a clear value prop for REST, and also for graphQL in the updated draft: https://docs-draft-openlibertyio.mqj6zf7jocq.us-south.codeengine.appdomain.cloud/docs/latest/rest-alternatives.html |
This isn't helpful because it implies all are equal (less an issue in this particular container topic but more a problem in, say, the Observability container topic and not a style we should be adopting). It also leads with the topic then gives some info about why you might want to know about it, assuming that the reader will read each in turn. Just give the link to more info after explaining why the technology is a useful alternative in the context of what's been said above it.
The text was updated successfully, but these errors were encountered: