Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Add Node Handbook content #105

Merged
merged 9 commits into from
Nov 22, 2018
Merged

Add Node Handbook content #105

merged 9 commits into from
Nov 22, 2018

Conversation

flaviocopes
Copy link
Contributor

@flaviocopes flaviocopes commented Oct 22, 2018

After @amiller-gh got in touch I started moving content from nodehandbook.com to this PR, adapting the content to suit the Node.js website.

I removed some fancy banner images I used in the original content (not suitable here), removed internal links that pointed to my blog, removed opinionated things and some content not appropriate.

Let me know what you think!

@keywordnew
Copy link
Contributor

@flaviocopes Congratulations on your first PR to this initiative! 💥

We're super happy to have all the content to review. The review for this PR may take slightly more time than is typical, being a 5000+ line PR 👀

Thanks for starting to contribute here!

@amiller-gh
Copy link
Member

@flaviocopes you are amazing 🎉

I'll be sure to do a closer review over the weekend, but at cursory glance this is brilliant.

@mjordancodes, interested in siccing your army of new developers on this branch for content review as well? Have them comment on anything they're confused by, think could be re-structured, or just when they really like something! We can all work to integrate the feedback afterwords. Having the new-developer eyes on content targeted for them will be very helpful.

We'll also take a pass at identifying images that can be re-done in the new illustration style we're pursuing for the site. I'll have Joey (designer) take a look at that in the next week or so. This PR can land before that happens.

@keywordnew keywordnew self-requested a review October 25, 2018 14:57
@amiller-gh amiller-gh added wr-agenda Agenda items for the website redesign group getting-started-docs Getting started documentation page labels Oct 25, 2018
@mjordancodes
Copy link

@amiller-gh --> Just saw this. Sharing on the slack group now. Will bug students in person when I see them again on Wednesday

@keywordnew
Copy link
Contributor

@ZibbyKeaton This is the PR that contributes Getting Started content to the project. 🙌🏽

Thanks @flaviocopes! 💖

})
apples.forEach(fruit => {
console.count(fruit)
})
Copy link

@ghost ghost Nov 1, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think using semicolons at the end of each statement for at least the larger code blocks is in the best interest for a beginner going through these guides. Although there are no changes in the behavior here, I think it's best for a programmer to use semicolons while writing Js Code
@bnb Your thoughts on this

@ghost
Copy link

ghost commented Nov 1, 2018

@flaviocopes Brilliant job. Can't appreciate enough.
Thank you for your time and dedication (^_^)

@flaviocopes
Copy link
Contributor Author

Thanks @Flowkrad for all those suggestions!

@amiller-gh
Copy link
Member

@flaviocopes You are AMAZING 🎉

@flaviocopes
Copy link
Contributor Author

Thank you @amiller-gh, I'm super happy this was merged 😀 🎉

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
getting-started-docs Getting started documentation page wr-agenda Agenda items for the website redesign group
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants