Merge branch 'open-sauced:main' into main

Author: CBID2

.github/CODEOWNERS

@@ -1,2 +1 @@
-@open-sauced/triage
-@open-sauced/docs
+* @open-sauced/docs

static/.nojekyll .nojekyll

@@ -5,6 +5,62 @@
 
 > All notable changes to this project will be documented in this file
 
+### [1.67.1](https://github.com/open-sauced/docs/compare/v1.67.0...v1.67.1) (2024-03-12)
+
+
+### Bug Fixes
+
+* update workspace images based on latest UI ([#277](https://github.com/open-sauced/docs/issues/277)) ([12c8ffd](https://github.com/open-sauced/docs/commit/12c8ffdb69c36a74b073c1fe594c9adc3d6206e4))
+
+## [1.67.0](https://github.com/open-sauced/docs/compare/v1.66.3...v1.67.0) (2024-03-08)
+
+
+### Features
+
+* update workspace with more information on team plan ([#272](https://github.com/open-sauced/docs/issues/272)) ([2a82913](https://github.com/open-sauced/docs/commit/2a82913a1405875fd560cd24c22e22879f6f119d))
+
+### [1.66.3](https://github.com/open-sauced/docs/compare/v1.66.2...v1.66.3) (2024-03-06)
+
+
+### Bug Fixes
+
+* Update docs for 100 days of oss ([#271](https://github.com/open-sauced/docs/issues/271)) ([0a7f9aa](https://github.com/open-sauced/docs/commit/0a7f9aaa610e48b399775bcb1ac39c94caaf7f3c))
+
+### [1.66.2](https://github.com/open-sauced/docs/compare/v1.66.1...v1.66.2) (2024-03-05)
+
+
+### Bug Fixes
+
+* format and wording adjustments in workspaces, contributors and repo insights sections ([#262](https://github.com/open-sauced/docs/issues/262)) ([37bddac](https://github.com/open-sauced/docs/commit/37bddace074327542d12d164a4b61e42303c8548))
+
+### [1.66.1](https://github.com/open-sauced/docs/compare/v1.66.0...v1.66.1) (2024-03-04)
+
+
+### Bug Fixes
+
+* Issues Section ([#269](https://github.com/open-sauced/docs/issues/269)) ([785e75a](https://github.com/open-sauced/docs/commit/785e75a3285bf73fe4a81ec9432278998122a2ab))
+
+## [1.66.0](https://github.com/open-sauced/docs/compare/v1.65.0...v1.66.0) (2024-02-27)
+
+
+### Features
+
+* Add workspaces documentation ([#255](https://github.com/open-sauced/docs/issues/255)) ([103fda2](https://github.com/open-sauced/docs/commit/103fda209d0ed778db2e6534d8df17a62ffd1f3b))
+
+## [1.65.0](https://github.com/open-sauced/docs/compare/v1.64.0...v1.65.0) (2024-02-19)
+
+
+### Features
+
+* Add a Contributors guide ([#229](https://github.com/open-sauced/docs/issues/229)) ([ec79f59](https://github.com/open-sauced/docs/commit/ec79f5901d3df35612b6814b23ada2d213b0d6a5))
+
+## [1.64.0](https://github.com/open-sauced/docs/compare/v1.63.2...v1.64.0) (2024-02-16)
+
+
+### Documentation
+
+* Add information about PR with unassigned issue to the contributing guidelines ([#252](https://github.com/open-sauced/docs/issues/252)) ([4ccd758](https://github.com/open-sauced/docs/commit/4ccd758485474b44a793fbc9242b0161ae4eaf40)), closes [#251](https://github.com/open-sauced/docs/issues/251) [#251](https://github.com/open-sauced/docs/issues/251)
+
 ### [1.63.2](https://github.com/open-sauced/docs/compare/v1.63.1...v1.63.2) (2024-02-05)
 
 

CHANGELOG.md

@@ -71,19 +71,17 @@ Here's what you can do if you're ready to join this challenge:
 
 ## The Official Kickoff
 
-We started our first #100DaysOfOSS on July 23rd, 2023, and went to the end of [Hacktoberfest](https://hacktoberfest.com/), a month-long celebration of open source contributions.
-
-Don't worry if you didn't start then. The #100DaysOfOSS challenge is flexible; you can join whenever you're ready. Just jump in at any point and begin with day one of your personal challenge.
+ The #100DaysOfOSS challenge is flexible; you can join whenever you're ready. Just jump in at any point and begin with day one of your personal challenge.
 
 ## Support
 
 To make the most of your #100DaysOfOSS journey, here are some additional resources and events you can explore:
 
-1. **Weekly X Spaces:** Join our weekly X Spaces sessions, where we discuss open source topics, share insights, and connect with like-minded individuals. Follow us on [X](https://twitter.com/saucedopen) to stay updated on upcoming sessions.
+1. **Weekly X Spaces:** Join our X Spaces, where we discuss open source topics, share insights, and connect with like-minded individuals. Follow us on [X](https://twitter.com/saucedopen) to stay updated on upcoming sessions.
 
 2. **Community events:** Discover a wide range of events on our [community docs page](https://docs.opensauced.pizza/community/welcome-to-the-community). Whether hack days, workshops, or office hours, these events provide excellent opportunities to learn, collaborate, and find new projects to contribute to.
 
-3. **Weekly contribution opportunities:** If you're actively looking for open source projects to contribute to, check out the [weekly post](https://dev.to/bekahhw/series/23323) for new contribution opportunities.
+3. **Contribution opportunities:** If you're actively looking for open source projects to contribute to, check out the [post](https://dev.to/bekahhw/series/23323) for new contribution opportunities.
 
 4. **Weekly office hours:** Have questions or need help? Join us on [Discord](https://discord.gg/dXvGd8mz) during our office hours or post on our `#100DaysOfOSS` channel. We're here to help you succeed!
 
@@ -94,6 +92,7 @@ If you're ready to start your #100DaysOfOSS journey, here are some tips to help
 - **Find a project:** Explore the [OpenSauced](https://opensauced.pizza/) website to find a project that interests you. You can also check out the [weekly post](https://dev.to/bekahhw/series/) for exciting contribution opportunities.
 - **Take our Intro To Open Source course:** If you're new to open source, we recommend taking our [Intro to Open Source course](https://intro.opensauced.pizza/#/) to learn more about open source and how to get started.
 - **Record your journey:** You will learn a lot as you navigate this challenge, so we highly recommend using our [#100DaysOfOSS journal template](https://github.com/open-sauced/100-days-of-oss-template) on GitHub or [Notion](https://www.notion.so/a0m0rajab/100-Days-Of-Open-Source-2615e66772e14152897002e348c5f1bc?pvs=13) to help you reflect. Remember, this is _your_ journey, so feel free to customize them however you like.
+- **Check our Contributors Guide:** If you're new to contributing to open source, we recommend checking out our [Contributors Guide to OpenSauced](https://docs.opensauced.pizza/contributors/contributors-guide-to-open-sauced/) to learn more about the process and best practices.
 
 ## The Power of the #100DaysOfOSS Challenge
 
@@ -115,6 +114,6 @@ Our hope is that the community will provide a safe space to discuss challenges,
 
 ### Weekly Office Hours
 
-Have questions or need help? Join us on [Discord](https://discord.gg/opensauced) during our office hours every Tuesday at noon ET or post on our `#100DaysOfOSS` channel. We're here to help you succeed!
+Have questions or need help? Join us on [Discord](https://discord.gg/opensauced) and post on our `#100DaysOfOSS` channel. We're here to help you succeed!
 
 Happy contributing, and best of luck on your #100DaysOfOSS adventure!

docs/community/100-days-of-oss.md

@@ -17,7 +17,7 @@ keywords:
 ---
 
 Contributions are always welcome, no matter how large or small. Before contributing,
-please read the [code of conduct](./code-of-conduct.md) and follow the directions below:
+please read the [Code of Conduct](./code-of-conduct.md) and follow the directions below:
 
 ## Recommended Communication Style
 
@@ -28,13 +28,26 @@ please read the [code of conduct](./code-of-conduct.md) and follow the direction
 
 ## Issues
 
-If you wish to work on an open issue, please comment on the issue with `.take`, and it will be assigned to you. If an issue is not assigned, it is assumed to be available for anyone to work on. Please assign yourself to an issue before working on it to avoid conflicts.
+- If you wish to work on an open issue, please comment on the issue with `.take`, and it will be assigned to you.
 
-If you contribute to the project for the first time, you can search for issues with `good first issue` or `bug` labels in the repository. Please only self-assign a `good first issue` one time.
+  :::info
+  
+  If an issue is not assigned, it is assumed to be available for anyone to work on. Please assign yourself to an issue _before_ working on it to avoid conflicts.
+
+  :::
+
+- Issues with the `needs triage` label are unavailable to `.take` until they are triaged and the label is removed. Feel free to check on the issue regularly if you want to work on it.
+- If you contribute to the project for the first time, you can search for issues with `good first issue` or `bug` labels in the repository.
+
+  :::note
+  
+  Please only self-assign a `good first issue` one time.
+
+  :::
 
 In case you get stuck, feel free to ask for help in the [Discord](https://discord.gg/U2peSNf23P) server or [GitHub Discussions](https://github.com/orgs/open-sauced/discussions).
 
-Please follow our [code of conduct](./code-of-conduct.md) in all your interactions with the project and its contributors.
+Please follow our [Code of Conduct](./code-of-conduct.md) in all your interactions with the project and its contributors.
 
 ## Commits
 
@@ -51,8 +64,11 @@ After running this command, you can push your changes to the remote repo.
 See [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for more examples.
 
 ## Pull Requests (PR)
+---
 
-**_We actively welcome your pull requests. However, you must link your work to an existing issue._**
+We actively welcome your pull requests. However, you must ensure that **you are assigned** to an existing issue before working on changes, and you need to **link your work to the issue** in your PR form.
+
+---
 
 1. Fork the repo and create your branch from the default branch.
 2. Name your branch to something descriptive of your work, i.e., `add-navbar` or `fix/broken-links`.
@@ -66,9 +82,14 @@ See [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for m
 
    - The title must begin with "feat:", "fix:", or anything related to your changes. <br /> **Tips**: You can follow your chosen option when [committing](#commits) your changes.
 
-   - Unsolicited code is welcomed, but an issue is required to announce your intentions. <br /> **_PRs without a linked issue will be marked invalid and closed_**.
-  
-> [!IMPORTANT]  
+   - Unsolicited code is welcomed, but an issue is required to announce your intentions.
+
+⚠️ **PRs will be marked as invalid and may be closed if:**  
+
+- the issue is not assigned to the contributor who opened the PR  
+- no issue is linked to the PR  
+
+> **IMPORTANT:** <br />
 > Please do not DM Maintainers or contact them outside of GitHub if you want a PR Review. If you haven't received a review within a week, please tag them in the PR comments to ask for an estimated time of review.
 
 > _**Note for maintainers**: All PRs need a label to assist automation. See [this guide](./triage-guide.md#adding-issue-and-pr-labels) to determine which labels to use._