[fix] added tips

[CBID2]

What type of PR is this? (check all applicable)

• [ ] 🍕 Feature
• [ ] 🐛 Bug Fix
• [X] 📝 Documentation Update
• [ ] 🎨 Style
• [ ] 🧑‍💻 Code Refactor
• [ ] 🔥 Performance Improvements
• [ ] ✅ Test
• [ ] 🤖 Build
• [ ] 🔁 CI
• [ ] 📦 Chore (Release)
• [ ] ⏩ Revert

Description

This PR adds more detail on how to create an Open Source on OpenSauced.

Related Tickets & Documents

Fixes #4

Mobile & Desktop Screenshots/Recordings

Added tests?

• [ ] 👍 yes
• [X] 🙅 no, because they aren't needed
• [ ] 🙋 no, because I need help

Added to documentation?

• [ ] 📜 README.md
• [X] 📓 docs.opensauced.pizza
• [ ] 🍕 dev.to/opensauced
• [ ] 📕 storybook
• [ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[BekahHW]

Hey @CBID2. Thanks for getting this up so fast! Looking through the file, I wonder if it makes more sense to reorganize a little bit so we can add more.

My thoughts are:

Develop Your Open Source Resume

Building a strong open source resume can help you showcase your skills, experience, and contributions to potential employers, collaborators, and the wider developer community.

Effectively Highlight Your Contributions

This would include the new material you created, but also include information on providing project details (tools, libraries, size and complexity), describing your contributions (type [bug fix, feature, performance, documentation, etc.]), details on collaboration.

Let me know if you're up for implementing this or want to talk through this some more. And thanks again for this idea!

[CBID2]

Hey @CBID2. Thanks for getting this up so fast! Looking through the file, I wonder if it makes more sense to reorganize a little bit so we can add more.

My thoughts are:

Develop Your Open Source Resume

Building a strong open source resume can help you showcase your skills, experience, and contributions to potential employers, collaborators, and the wider developer community.

Effectively Highlight Your Contributions

This would include the new material you created, but also include information on providing project details (tools, libraries, size and complexity), describing your contributions (type [bug fix, feature, performance, documentation, etc.]), details on collaboration.

Let me know if you're up for implementing this or want to talk through this some more. And thanks again for this idea!

Hi @BekahHW! :) I like this description. It'll help users understand the importance of describing their experiences. I think adding it within my paragraph about adding metrics when highlighting open source contributions will be helpful too.

[BekahHW]

@CBID2 do you want to add that update as part of your PR?

[CBID2]

@CBID2 do you want to add that update as part of your PR?

Sure @BekahHW!

[CBID2]

@CBID2 do you want to add that update as part of your PR?

Did it @BekahHW! :)

[BekahHW]

[BekahHW]

Thank you, @CBID2

[CBID2]

I love that meme @BekahHW! :) Please DM it to me on Twitter