Merge pull request #410 from JonDevOps/main

major updates

Author: JonDevOps

.github/CHANGELOG.md

@@ -1,4 +1,5 @@
-edit this
+edit this template
+new info TBD
 
 Read here for more info on what a changelog is https://keepachangelog.com/en/1.0.0/
 

.github/CODEOWNERS

@@ -8,22 +8,22 @@
 # -------------------------------------------------
 
 # -------------------------------------------------
-# All files except markdown are owned by dev team
+# All files except markdown are owned by w3develops core
 # -------------------------------------------------
 
-* @w3develops/dev-team
+* @w3develops/w3develops-core
 *.md
 
 # -------------------------------------------------
-# All files in the root are owned by dev team
+# All files in the root are owned by w3develops x
 # -------------------------------------------------
 
-/* @w3develops/dev-team
+/* @w3develops/w3develops-x
 
 # -------------------------------------------------
 # All markdown files in the root are owned
 # by Jonathan Jackson.
 # He oversees the README, LICENSE, etc.
 # -------------------------------------------------
 
-/*.md @JonathanJackson
+/*.md @jondevops

.github/CODE_OF_CONDUCT.md

@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at w3develops@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@w3develops.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 

.github/CONTRIBUTING.md

@@ -1,27 +1,26 @@
-[//]: (copy freecodecamps most current contributing guidlines, also make a page for the w3develops pages mentioned below.)
 # Contribution Guidelines
 
 Hello 👋!
 
 w3Develops.org is possible, thanks to thousands of kind volunteers like you. We are grateful for your contributions and we are excited to welcome you aboard.
 
-We strictly enforce our ["Code of Conduct"](https://www.w3develops.org/code-of-conduct). Take a moment to read it. It's only 196 words long.
+We strictly enforce our ["Code of Conduct"](https://github.com/w3develops/w3Develops/blob/main/.github/CODE_OF_CONDUCT.md). Take a moment to read it. It's only 196 words long.
 
 Happy contributing 🎉!
 
 ## Here are some fun ways that you can help
 
 You can choose to contribute to any area that interests you:
 
-1. [Contribute to this open source codebase](#contribute-to-this-open-source-codebase). Help to edit [guide articles](https://w3develops.org/guide), [coding projects](https://w3develops.org/projects), or fix bugs on the learning platform.
+1. [Contribute to this open source codebase](#contribute-to-this-open-source-codebase). Help to edit [guide articles](https://w3develops.org/guide), [coding projects](https://w3develops.org/group-projects), or fix bugs on the learning platform.
 
 2. Help campers on our [public forum](https://www.w3develops.org/forum/). Answer their coding questions or give them feedback on their coding projects.
 
 3. Help us add subtitles or closed captions to our [YouTube channel videos](https://www.youtube.com/channel/UC8butISFwT-Wl7EV0hUK0BQ/videos).
 
 ## Contribute to this open source codebase
 
-Our open source codebase consisting of many of [coding projects](https://w3develops.org/projects) and [guide articles](https://w3develops.org/guide).
+Our open source codebase consisting of many of [coding projects](https://w3develops.org/group-projects) and [guide articles](https://w3develops.org/guide).
 
 You can help us to:
 
@@ -43,7 +42,7 @@ Our guides will help you get a quick understanding of what a study group or proj
 
 We welcome your help writing these guides. You don't have to be an expert in a topic to write about it but you should know how a study group or project collaboration group operates. This entire Guide is open source, so even if you make a mistake, another contributor will eventually correct it.
 
-To help find a guide to write about go to our [projects page](https://w3develops.org/projects) or [study groups page](https://w3develops.org/groups), find a topic you are knowedgable in write the article, then open a pull request to replace the current page with your updated version. A [pull request](https://help.github.com/articles/about-pull-requests/) is how you'll suggest changes. It lets others know about, review, and eventually adopt your changes.
+To help find a guide to write about go to our [projects page](https://w3develops.org/group-projects) or [study groups page](https://w3develops.org/study-group), find a topic you are knowedgable in write the article, then open a pull request to replace the current page with your updated version. A [pull request](https://help.github.com/articles/about-pull-requests/) is how you'll suggest changes. It lets others know about, review, and eventually adopt your changes.
 
 ### Create, Update and Fix Bugs in our coding projects
 

.github/LICENSE

@@ -1,21 +1,29 @@
-The MIT License (MIT)
+BSD 3-Clause License
 
-Copyright (c) 2017-2026 w3Develops
+Copyright (c) 2026, w3Develops
+All rights reserved.
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
 
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+* Neither the name of the copyright holder nor the names of its
+  contributors may be used to endorse or promote products derived from
+  this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

.github/PULL_REQUEST_TEMPLATE.md

@@ -3,7 +3,7 @@ edit this
 
 <!-- Please follow this checklist and put an x in each of the boxes, like this: [x]. It will ensure that our team takes your pull request seriously. -->
 
-- [ ] I have read [w3Develops contribution guidelines](https://github.com/freeCodeCamp/freeCodeCamp/blob/master/CONTRIBUTING.md).
+- [ ] I have read [w3Develops contribution guidelines](https://github.com/w3develops/w3Develops/blob/main/.github/CONTRIBUTING.md).
 - [ ] My pull request has a descriptive title (not a vague title like `Update index.md`)
 - [ ] My pull request targets the `staging` branch.
 - [ ] None of my changes are plagiarized from another source without proper attribution.

.github/SUPPORT.md

@@ -1,3 +1,5 @@
+TBD - GOOD FIRST ISSUE
+
 SUPPORT files work just like CONTRIBUTING files. They can live in your repository root, .github/, or docs/ folder, and will be displayed throughout GitHub such as above the new issue form.
 
 Instead of describing how to contribute to the project like CONTRIBUTING files do, SUPPORT files can be used to direct users to dedicated support resources, such as community forums, FAQ documents, or corporate support channels.

.github/style-guide.md

@@ -0,0 +1 @@
+TBD - GOOD FIRST ISSUE