-
Notifications
You must be signed in to change notification settings - Fork 0
docs: Appsync Events #117
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
docs: Appsync Events #117
Conversation
Deploying localstack-docs with
|
Latest commit: |
9a20715
|
Status: | ✅ Deploy successful! |
Preview URL: | https://f0fc8110.localstack-docs.pages.dev |
Branch Preview URL: | https://appsync-event-docs.localstack-docs.pages.dev |
Preview latest draft here: cc @cloutierMat |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the structure update. I was trying to avoid going 4 "#" deep as we lose it in the TOC... but it might be unavoidable....
Going trough the order, I understand that you are trying to avoid 2 "Getting Started", but I feel it might be necessary since right now the docs jump from GraphQL to Events and back multiple times, and that also seems confusing.
What do you think of the following order?
- Introduction
- GraqhQL API
-
- Getting Started
-
- Resolvers
-
- Configuring Endpoints
-
- Resource Browser
-
- Example
- Events API
-
- Getting Started
-
- Code Handlers
-
- Configuring Endpoints
-
- Resource Browser
- Shared configurations
-
- Custom API IDs
-
- Data Sources
- Evaluation Endpoints
- API Coverage
In time we can add more information to Events API with example and some extra details. Since both APIs are solving a different problems for different users, I think that having the docs grouped by APIs will be more beneficial.
curious to hear @simonrw's opinion as well
Co-authored-by: Mathieu Cloutier <79954947+cloutierMat@users.noreply.github.com>
tyvm for your detailed feedback & outline suggestion, @cloutierMat (cc @simonrw)... i'll proceed to update this PR w/ your recommended outline |
This pr introduces AppSync Events API documentation. As we are sharing the page with AppSync GraphQL APIs, some restructure is also added in the pr to help keeping a clear and understandable view of the docs