ubclaunchpad / LP-website

UBC Launch Pad knowledge base
https://www.ubclaunchpad.com
8 stars 6 forks source link

Add documentation for MERN stack #131

Closed nandanmen closed 4 years ago

nandanmen commented 4 years ago

Related Tickets

Closes #127

Changes

Add documentation for MERN stack as per https://docs.google.com/document/d/1ZyX8MtEF7v_ka6EvxtyrTnYZv_0YCwVAyygOQmzARYY/edit

Checklist

nandanmen commented 4 years ago

@no-or @andrewzulaybar I've made a draft PR for this task and copied over the documentation that rob wrote. Feel free to clone and push some commits in this branch!

netlify[bot] commented 4 years ago

Deploy preview is ready!

Built with commit 88849054a652f2e3d2c90569eb39ca56ad71ae8e

https://deploy-preview-131--ubclaunchpad-docs.netlify.app

bobheadxi commented 4 years ago

Thanks for getting this set up @narendrasss! Let me know if y'all need anything :)

Also just a heads up that there is a blank template available in the markdown comments: https://sourcegraph.com/github.com/ubclaunchpad/docs@7e9c64e/-/blob/resources/groundwork/web.md#L15-48

andrewzulaybar commented 4 years ago

I'm thinking that there will probably be considerable overlap with the sync stack documentation, particularly because the only difference between the stacks is the datastore. Should we think about this redundancy?

nandanmen commented 4 years ago

I'm thinking that there will probably be considerable overlap with the sync stack documentation, particularly because the only difference between the stacks is the datastore. Should we think about this redundancy?

@bobheadxi Any thoughts on this?

no-or commented 4 years ago

I'm thinking that there will probably be considerable overlap with the sync stack documentation, particularly because the only difference between the stacks is the datastore. Should we think about this redundancy?

Some repetition is expected among different stacks as many of them use the same technologies/languages. So that's fine in my opinion unless we want to change the structure of the page by going with technologies/languages instead of stacks! Looking forward to hearing from @bobheadxi

bobheadxi commented 4 years ago

Some repetition is expected among different stacks as many of them use the same technologies/languages. So that's fine in my opinion unless we want to change the structure of the page by going with technologies/languages instead of stacks!

I agree with this! If you feel like there's too much repetition, also feel free to say "refer to ...."

Also, could focus writing on why X technology works particularly well with Y and Z :)