[Concept Entry] PyTorch autograd

[codecademy-docs]

Reason/inspiration (optional)

We would like a new entry on the autograd concept under PyTorch. The entry should go in a new file under docs/content/pytorch/concepts/autograd/autograd.md.

The entry should include:

• An introduction to the concept
• A ‘Syntax’ section that provides the syntax for the concept (if applicable)
• An ‘Example’ section that provides an example demonstrating the concept in use
• A ‘Codebyte Example’ section that provides a codebyte example demonstrating the concept in use

Please refer to the concept entry template, content standards, and markdown style guide when working on the PR for this issue.

Entry Type (select all that apply)

New Concept Entrty for Existing Topic

Code of Conduct

• By submitting this issue, I agree to follow Codecademy Doc's Code of Conduct.

For Maintainers

• Labels added
• Issue is assigned

[Linchihj]

I'd like to be assigned this issue.

[sethaferd]

I volunteer as second in line to @Linchihj

[mamtawardhani]

Since @Linchihj commented first, will assign it to her. @sethaferd you can look through the available issues and let me know if anything interests you 😃

[mamtawardhani]

@Linchihj You're assigned!🎉 You can look through the Contribution Guide to know more about contributing to Codecademy Docs. Check out the Content Standards and Style Guide, they’ll help you with creating your entry.

I see this is your first time contributing to Codecademy Docs. How did you find out about us?

[Linchihj]

Hi @mamtawardhani,
This one will take me more research to finish, so it may take me a week. I'll let you know when the draft is ready for review and include references I've used to write the concept.

[Linchihj]

Hi @mamtawardhani,
I've submitted the pull request for the first draft yesterday.

[github-actions]

🌸 Thanks for closing this Issue!
Please head over to the Docs Forum if you have any questions about Docs, or reply to the thread on Possible Content Discussion to share ideas and collaborate with other contributors, maintainers, or super users to determine good future issues that will help expand Docs!