cleanup errors and reorg nav

Author: kefortney

docs/concepts/_category_.yml

@@ -1,4 +1,4 @@
-position: 2
+position: 3
 label: Concepts
 collapsed: false
 link:

docs/concepts/ai_and_llms.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 24
+---
+
 # AI and LLMs in Programming
 
 **Large Language Models (LLMs)** have rapidly changed how software is written. Tools like GitHub Copilot, ChatGPT, Claude, and Cursor can generate code, explain errors, write tests, and review pull requests. Understanding what these tools are, how they work, and how to use them responsibly is increasingly important for any programmer.

docs/concepts/apis.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 8
+---
+
 # APIs
 
 An **API** (Application Programming Interface) is a defined way for two pieces of software to communicate with each other. APIs are everywhere in modern software: when a weather app shows you the forecast, it's fetching data from a weather API. When you log into a site with Google, that site is calling Google's OAuth API.

docs/concepts/ci_cd.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 9
+---
+
 # CI/CD
 
 **CI/CD** stands for **Continuous Integration** and **Continuous Delivery** (or Deployment). It's a set of practices and tools that automate the testing and deployment of software, letting teams ship code more reliably and frequently.

docs/concepts/collaboration_and_communication.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 10
+---
+
 # Collaboration and Communication
 
 Collaboration and communication are at the heart of open source development. Open source projects thrive on the contributions of a diverse and often geographically dispersed community of developers, designers, testers, and users. Effective collaboration and clear communication are key to the success of these projects. In this guide, we'll explore how collaboration and communication work in the open source ecosystem.

docs/concepts/command_line.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 2
+---
+
 # Command Line
 
 The command line (also called the **terminal**, **shell**, or **CLI** — Command Line Interface) is a text-based way to interact with your computer. Instead of clicking icons and menus, you type commands.

docs/concepts/community.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 17
+---
+
 # Community
 
 The open source community is diverse and highly motivated. Whether it’s development or advocacy, open source software and other collaborative projects benefit through, and because of, community.
@@ -35,7 +39,8 @@ The role of an open source community architect involves a variety of tasks and r
 - Developing strategies to grow and engage the community
 - Monitoring and measuring the health and success of the community
 
-## Links
-https://opensource.org/community
+## References
+
+- [Open Source Initiative: Community](https://opensource.org/community)
 
 

docs/concepts/debugging.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 4
+---
+
 # Debugging
 
 Debugging is the process of finding and fixing errors (bugs) in your code. Every programmer spends a significant portion of their time debugging — it's a core skill, not a sign of failure.

docs/concepts/documentation.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 6
+---
+
 # Documentation
 
 Documentation is any communicable material that is used to describe, explain or instruct regarding some attributes of an object, system or procedure, such as its parts, assembly, installation, maintenance and use.
@@ -47,6 +51,10 @@ To write good open source documentation, there are a few key things you should k
 - Keep it up to date: As the project evolves, make sure to update the documentation to reflect any changes or new features. This will ensure that the documentation stays relevant and accurate.
 - Get feedback: Ask other contributors or users to review the documentation and provide feedback. This can help identify any gaps or areas that need clarification.
 
+## See Also
+
+- [Open Source Projects](/concepts/projects) — how to write a good README and CONTRIBUTING file for your project
+
 ## References
 - [The Documentation System](https://documentation.divio.com/)
 - [Wikipedia's documentation page](https://en.wikipedia.org/wiki/Documentation)

docs/concepts/engineering_methodologies.md

@@ -1,3 +1,7 @@
+---
+sidebar_position: 14
+---
+
 # Engineering Methodologies
 
 Engineering methodologies are structured approaches to planning, executing, and managing engineering projects. They provide a systematic framework for designing, developing, and maintaining complex systems, products, or processes. By following established engineering methodologies, teams can ensure efficiency, quality, and successful project outcomes. Here, we explore some commonly used engineering methodologies:
@@ -65,7 +69,7 @@ RAD is an approach that prioritizes rapid prototyping and quick iterations. It a
 The Spiral model is a risk-driven methodology that combines iterative development with elements of the Waterfall model. It involves cycles of planning, risk analysis, engineering, and evaluation. Each iteration addresses potential risks, making it suitable for large and complex projects.
 
 - [ArtofTesting: Spiral Model](https://artoftesting.com/spiral-model)
-- [Broken Link](https://www.spaceo.ca/blog/spiral-model-of-software-development/)
+- [Spaceo: Spiral Model of Software Development](https://www.spaceo.ca/blog/spiral-model-of-software-development/)
 
 ## Six Sigma