Update readme: to mention blog

readme.md

@@ -1,86 +1,83 @@
----
-id: readme
-aliases: []
-tags: []
-area: general
-priority: low
-project: none
-related: []
----
-
-## Eduuh's Byte Safari
+# Eduuh's Byte Safari
 
 This repository is designed to store my public notes, public blog related source code together.
 
-### Objective
+The top level folder structure is as follows.
 
-- **Knowledge Repository:** Functions as an Obsidian vault, storing notes in Markdown format for easy organization and reference.
-- **Learning Hub:** A space for continuous growth, focusing on Data Structures & Algorithms (DSA), frameworks, and Neovim configuration.
+```mermaid
 
-### 1. Data Structures & Algorithms (DSA)
-
-#### Goals
-
-- **Unified Solution Format:** Build each solution in one file, with reusable test cases that work across different programming languages.
-- **Language Diversity:** Solve problems in various languages to improve proficiency in different syntax's and paradigms.
-- **Repository Growth:** Expand the repository as new concepts and solutions are learned.
-- **Fast Debugging:** Leverage [Neovim DAP](https://github.com/mfussenegger/nvim-dap) (Debug Adapter Protocol) for efficient debugging.
+graph TD
+    Root["/"]
+    Root --> blog --> eduuh.com
+    Root --> content["Cleanup Notes"]
+    content --> MDX["MDX Files (.mdx)"]
+    content  --> notes
+    content --> blogs
+    content --> topics
+    content --> inbox
+    blogs --> draft
+    blogs --> published
+    notes --> drafts
+    notes --> cleanups
+    notes --> archived
+    notes --> dailies
 
-#### Future DSA Enhancements
+```
 
-- **Automated Question Downloads:** Integrate tools to download questions from platforms like [LeetCode](https://leetcode.com), [Codeforces](https://codeforces.com), or other online judges, and automate solution submissions.
-- **Competitive Programming Bootstrap:** Set up a development environment for competitive programming with quick-start templates.
-- **Interactive Challenges:** Incorporate tools like embedded code-runners on my
-  blog, visualization tools.
+Content is the obsidian vault.
 
-### 2. Framework Exploration (Any Language)
+## Objective
 
-#### Core Principles
+- **Knowledge Hub/Repository:** This acts like an Obsidian vault; it stores notes in Markdown, & mdx format. This is a growing space focusing on DSA, Neovim configurations, Math, and other interesting things.
 
-- **Sandbox for Ideas:** Provide an isolated environment to experiment with ideas and frameworks without waiting for lengthy build times.
-- **Cross-Language Testing:** Experiment with various frameworks across different programming languages.
+### 1. Data Structures & Algorithms (DSA)
 
-#### Future Additions
+#### Goals
 
-- **Template Generator:** Create a script or tool to generate boilerplate code for common frameworks, facilitating rapid experimentation.
-- **Framework Comparison:** Set up benchmarks to evaluate different frameworks based on performance, ease of use, and scalability.
+- Solve problems in single files with reusable, cross-language test cases.
+- Practice in multiple languages to learn new skills.
+- Continuously add new solutions and refine old ones.
+- Use [Neovim DAP](https://github.com/mfussenegger/nvim-dap) for quick debugging.
 
-### 3. Neovim Configuration Testing
+#### Future Enhancements
 
-#### Purpose
+- Automate question downloads and solution submissions for platforms like [LeetCode](https://leetcode.com) and [Codeforces](https://codeforces.com).
+- Set up templates for competitive programming.
+- Add code runners and visualization tools to enhance learning and blogging.
 
-- **Stability and Reliability:** Dedicated to testing and maintaining the stability of my Neovim configuration by experimenting with plugins, themes, and settings.
+### 2. Neovim Configuration
 
-#### Testing Approach
+#### Goals
 
-- **Isolated Config Environment:** Test new configurations or plugins in an isolated environment to avoid breaking the main setup.
-- **Performance Monitoring:** Regularly check the performance of the setup to ensure it remains lightweight and efficient.
-- **Version Control:** Use version control to track changes in configuration, ensuring compatibility and easy upgrades.
+- Test and improve the stability of the Neovim setup with plugins, themes, and settings.
+- Maintain a lightweight and efficient configuration.
 
-### 4. Competitive Programming Roadmap
+#### Approach
 
-#### Immediate Goals
+- Use an isolated environment to test changes without affecting the main setup.
+- Monitor performance and track changes using version control.
 
-- **Regular DSA Practice:** Tackle DSA problems regularly to build proficiency in both theory and implementation.
-- **Solution Review:** Continuously review and optimize existing solutions for better coding practices and efficiency.
+### 3. Competitive Programming
 
-#### Mid-Term Goals
+#### Goals
 
-- **Multi-Language Proficiency:** Solve problems in at least three different languages to enhance problem-solving flexibility.
-- **Contest Participation:** Actively participate in platforms like [LeetCode](https://leetcode.com), [Codeforces](https://codeforces.com), and [AtCoder](https://atcoder.jp/) using the setup.
+- Regularly practice DSA problems to build skills.
+- Review and optimize solutions for better performance.
+- Participate in coding contests on platforms like [LeetCode](https://leetcode.com) and [AtCoder](https://atcoder.jp/).
 
-#### Long-Term Goals
+#### Long-Term Vision
 
-- **Automated Workflow:** Establish an automated workflow for downloading problems, solving them locally, and submitting solutions directly via CLI.
+- Automate workflows for downloading, solving, and submitting problems via CLI.
+- Develop proficiency in multiple languages for flexibility in problem-solving.
 
-### 5. Ideas for Growth
+### 4. Growth & Challenges
 
-- **Versioned Solutions:** Maintain different versions of DSA solutions to compare approaches and performance.
-- **Comprehensive Documentation:** Develop thorough documentation to make the repository a useful reference for future use.
-- **Modular Learning:** Organize solutions into categories based on topics such as sorting, graphs, dynamic programming, and more.
-- **Code Challenges:** Set up daily or weekly coding challenges to maintain consistency in learning and problem-solving.
+- Maintain versioned solutions to track progress and improvements.
+- Organize solutions by topic (e.g., sorting, graphs, dynamic programming).
+- Add documentation to make the repository a comprehensive reference.
+- Introduce regular coding challenges to stay consistent.
 
-### Related Repos
+### Related Repositories
 
 1. [nvim Configuration](https://github.com/eduuh/nvim)
 2. [HomeLab](https://github.com/eduuh/homelab)