Skip to content

Use case based tutorial #3824

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

Open
watilde opened this issue Nov 26, 2021 · 0 comments
Open

Use case based tutorial #3824

watilde opened this issue Nov 26, 2021 · 0 comments
Labels

Comments

@watilde
Copy link
Contributor

watilde commented Nov 26, 2021

Is your feature request related to a problem? Please describe.
As a new developer to Amplify, I'd like to learn how to build an app by an experiential learning so that I can gradually make the app my own app.

Describe the solution you'd like
Having use case driven tutorial with example code that can be pulled via git clone and Video guide or FAQ to answer to pitfalls developers may face. Let me list in details in the below:

  1. Use case needs to be put first as the new developer craft tutorial app and their own idea at the same time.
  2. Git clone based tutorial helps new developers to kick off their tutorial
  3. Video guide to answer to questions that the new developers may have.

As an example, GraphQL has the great tutorial docs that covers the above points.
https://odyssey.apollographql.com/

React also has the great tutorial with trouble shooting links that developers may face during tutorial
https://reactjs.org/tutorial/tutorial.html

Describe alternatives you've considered
The solution can be implemented one by one and totally fine to make subtasks.

Additional context
Some front-end developers who use AWS started learning Amplify to build their app on AWS quickly and I heard the above pain points.

@offlineprogrammer offlineprogrammer added feature-request Request a new feature guides labels Nov 27, 2021
@mauerbac mauerbac added the p4 guide needed/net new info label May 8, 2022
@timngyn timngyn added the amplify/docs-engineering Issues with the docs site itself, NOT its content label Feb 10, 2023
@reesscot reesscot added amplify/content and removed amplify/docs-engineering Issues with the docs site itself, NOT its content labels Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants