[Term Entry] Javascript Method : .parseInt()

[ULTRAPAIN]

Reason/inspiration (optional)

We would like a new term entry for JavaScript Numbers Methods about the .parseInt() method. The entry should go in a new file in docs/content/javascript/concepts/number-methods/terms/parseInt/parseInt.md.

The entry should:

• Have an Introductory paragraph about what the method is and does.
• Have a syntax section illustrating the function in a ```pseudo code block.
• An example showing the function in a ```js code block.
• A runnable codebyte example in a ```codebyte/javascript block.

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

Entry Type (select all that apply)

New Term Entry 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

[andersooi]

Hi, I’m interested in taking on this issue!

[Desolateeeooo]

Hello! I want to contribute on this issue!

[ULTRAPAIN]

Hi @mamtawardhani can you assign this Issue to them - I am not able to assign since I am the author of the Issue

[mamtawardhani]

@ishg-153
Can I assign this issue to the contributor? This issue was raised by @ULTRAPAIN (a contributor at Codecademy).
Let me know!

[ishg-153]

@mamtawardhani Yep this looks good to be assigned!

@ULTRAPAIN Thank you for suggesting this issue.

[ishg-153]

@andersooi 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.

[ishg-153]

@Desolateeeooo, @andersooi was here first. Please look through available issues, and ask to be assigned to an issue of your interest.

[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!