rehaul site to remove the implementation domains and system levels

Author: CameronBrooks11

TODO.md

@@ -10,7 +10,7 @@
 
 - [x] Update all templates to use revised KMLib
 
-- [ ] Clean up concepts:
+- [x] Clean up concepts:
   - VEGIS and CRUST
   - The 2 stacks
   - SLICE, LOAF, BATCH, OVEN

_config.yml

@@ -91,18 +91,6 @@ defaults:
       path: "**/README.md"
     values:
       nav_exclude: true
-  - scope:
-      path: "implementation-domains/**"
-    values:
-      layout: "default"
-      parent: "Implementation Domains"
-      nav_exclude: false
-  - scope:
-      path: "system-levels/**"
-    values:
-      layout: "default"
-      parent: "System Levels"
-      nav_exclude: false
   - scope:
       path: "developer-resources/**"
     values:

_data/navigation.yml

@@ -4,25 +4,7 @@
 # External project links (imported content)
 external_links:
   - name: BREADS
-    url: /implementation-domains/breads/
-  - name: FROOTS
-    url: /implementation-domains/froots/
-  - name: PROTINS
-    url: /implementation-domains/protins/
-  - name: SUGIRS
-    url: /implementation-domains/sugirs/
-  - name: SLICE
-    url: /system-levels/slice/
-  - name: LOAF
-    url: /system-levels/loaf/
-  - name: BATCH
-    url: /system-levels/batch/
-  - name: OVEN
-    url: /system-levels/oven/
-  - name: KiCad-Master-Lib
-    url: /developer-resources/kicad-master-lib/
-  - name: KiCad-Simulation-Examples
-    url: /developer-resources/kicad-simulation-examples/
+    url: /projects/breads/
   - name: ProtoKit
     url: /projects/protokit/
   - name: DevBoardDepot
@@ -33,3 +15,7 @@ external_links:
     url: /projects/crumbs/
   - name: linux-wire
     url: /projects/linux-wire/
+  - name: KiCad-Master-Lib
+    url: /developer-resources/kicad-master-lib/
+  - name: KiCad-Simulation-Examples
+    url: /developer-resources/kicad-simulation-examples/

_data/sources.json

@@ -6,7 +6,7 @@
             "repo": "FEASTorg/BREADS",
             "ref": "main",
             "subdir": "docs",
-            "mount": "implementation-domains/breads",
+            "mount": "projects/breads",
             "nav_order": 1,
             "redirect_from": [
                 "/breads/",
@@ -17,125 +17,6 @@
                 "**/TODO.md"
             ]
         },
-        {
-            "name": "froots",
-            "title": "FROOTS",
-            "repo": "FEASTorg/FROOTS",
-            "ref": "main",
-            "subdir": "docs",
-            "mount": "implementation-domains/froots",
-            "nav_order": 2,
-            "redirect_from": [
-                "/froots/",
-                "/froots"
-            ],
-            "exclude": [
-                "**/*.xcf",
-                "**/TODO.md"
-            ]
-        },
-        {
-            "name": "protins",
-            "title": "PROTINS",
-            "repo": "FEASTorg/PROTINS",
-            "ref": "main",
-            "subdir": "docs",
-            "mount": "implementation-domains/protins",
-            "nav_order": 3,
-            "redirect_from": [
-                "/protins/",
-                "/protins"
-            ],
-            "exclude": [
-                "**/*.xcf",
-                "**/TODO.md"
-            ]
-        },
-        {
-            "name": "sugirs",
-            "title": "SUGIRS",
-            "repo": "FEASTorg/SUGIRS",
-            "ref": "main",
-            "subdir": "docs",
-            "mount": "implementation-domains/sugirs",
-            "nav_order": 4,
-            "redirect_from": [
-                "/sugirs/",
-                "/sugirs"
-            ],
-            "exclude": [
-                "**/*.xcf",
-                "**/TODO.md"
-            ]
-        },
-        {
-            "name": "slice",
-            "title": "SLICE",
-            "repo": "FEASTorg/SLICE",
-            "ref": "main",
-            "subdir": "docs",
-            "mount": "system-levels/slice",
-            "nav_order": 1,
-            "redirect_from": [
-                "/slice/",
-                "/slice"
-            ],
-            "exclude": [
-                "**/*.xcf",
-                "**/TODO.md"
-            ]
-        },
-        {
-            "name": "loaf",
-            "title": "LOAF",
-            "repo": "FEASTorg/LOAF",
-            "ref": "main",
-            "subdir": "docs",
-            "mount": "system-levels/loaf",
-            "nav_order": 2,
-            "redirect_from": [
-                "/loaf/",
-                "/loaf"
-            ],
-            "exclude": [
-                "**/*.xcf",
-                "**/TODO.md"
-            ]
-        },
-        {
-            "name": "batch",
-            "title": "BATCH",
-            "repo": "FEASTorg/BATCH",
-            "ref": "main",
-            "subdir": "docs",
-            "mount": "system-levels/batch",
-            "nav_order": 3,
-            "redirect_from": [
-                "/batch/",
-                "/batch"
-            ],
-            "exclude": [
-                "**/*.xcf",
-                "**/TODO.md"
-            ]
-        },
-        {
-            "name": "oven",
-            "title": "OVEN",
-            "repo": "FEASTorg/OVEN",
-            "ref": "main",
-            "subdir": "docs",
-            "mount": "system-levels/oven",
-            "nav_order": 4,
-            "redirect_from": [
-                "/oven/",
-                "/oven"
-            ],
-            "exclude": [
-                "**/*.xcf",
-                "**/TODO.md"
-            ]
-        },
         {
             "name": "kicad-simulation-examples",
             "title": "KiCad Simulation Examples",

_pages/contributing.md

@@ -36,7 +36,7 @@ We welcome contributions from developers, engineers, researchers, and automation
 
 ### 1. Explore the Ecosystem
 
-Familiarize yourself with the [Functional Implementation Domains](/implementation-domains/) and [Hierarchical System Levels](/system-levels/) to understand how FEAST components work together.
+Familiarize yourself with the project to understand how FEAST components work together.
 
 ### 2. Join the Community
 

_pages/roadmap.md

@@ -8,46 +8,3 @@ nav_order: 10
 ## FEAST Development Roadmap
 
 This roadmap outlines the planned development and evolution of the FEAST ecosystem. Our development follows an iterative approach, with each phase building upon the foundation established in previous phases.
-
-### Phase 1: Foundation (Current)
-
-- ✅ Core architecture definition
-- ✅ Documentation infrastructure
-- ✅ Basic component specifications
-- 🔄 Initial implementation examples
-- 🔄 Community establishment
-
-### Phase 2: Core Implementation
-
-- ⏳ Complete BREADS hardware specification
-- ⏳ FROOTS firmware framework
-- ⏳ PROTINS middleware development
-- ⏳ SUGIRS interface system
-- ⏳ Reference implementations
-
-### Phase 3: Ecosystem Expansion
-
-- ⏳ Third-party integrations
-- ⏳ Extended component library
-- ⏳ Advanced tooling and utilities
-- ⏳ Performance optimizations
-- ⏳ Production deployment guides
-
-### Phase 4: Advanced Features
-
-- ⏳ AI/ML integration capabilities
-- ⏳ Cloud-native deployments
-- ⏳ Enterprise features
-- ⏳ Certification programs
-- ⏳ Commercial partnerships
-
-## Legend
-
-- ✅ Completed
-- 🔄 In Progress
-- ⏳ Planned
-- 🚫 Deferred
-
-## Contributing to the Roadmap
-
-Community input helps shape our development priorities. See our [Contributing](/contributing/) guide to learn how you can influence the roadmap or contribute to development efforts.

_pages/site-architecture.md

@@ -34,7 +34,7 @@ FEASTorg uses a hybrid Jekyll architecture that combines automated content impor
 
 ### Linked Projects Architecture
 
-Some projects maintain standalone GitHub Pages sites but are linked through the hub due to complex CI/CD requirements. For example, hardware projects (e.g., Slice\_\* repositories) have their own build pipeline using [bread-infra](https://github.com/FEASTorg/bread-infra), or the Freeboard Project, which has its own CI/CD setup using auto-generated developer API reference and component documentation from monorepo packages, published via VuePress and GitHub Actions.
+Some projects maintain standalone GitHub Pages sites but are linked through the hub due to complex CI/CD requirements. For example, hardware projects have their own build pipeline using [bread-infra](https://github.com/FEASTorg/bread-infra), or the Freeboard Project, which has its own CI/CD setup using auto-generated developer API reference and component documentation from monorepo packages, published via VuePress and GitHub Actions.
 
 These are managed via `_data/linked_projects.json` and automatically generate redirect stub pages.
 

_posts/2026-01-26-new-year-update.md

@@ -0,0 +1,18 @@
+---
+layout: post
+title: "New Year Update: Progress and Plans for 2026"
+date: 2026-01-26 13:24:00 -0400
+author: Cameron K. Brooks
+---
+
+As we kick off 2026, I wanted to share some exciting updates on the progress we've made with FEASTorg and outline our plans for the year ahead.
+
+## KiCad-Master-Lib
+
+The KiCad-Master-Lib repository has seen significant enhancements over the past few months. The organization and standardization of footprints and symbols have been a major focus, ensuring that the library is both clear for users and positioned to grow with future contributions. Now all symbols, footprints, and 3D models are stored within named subdirectories. Furthermore, the repo previously known as KiCad-Hierarchical-Designs has been merged into KiCad-Master-Lib under `kmlib-local/blocks`, streamlining our resources and making it easier for users to find what they need.
+
+In addition, we've added numerous new components, improved existing footprints, and refined our documentation to make it easier for users to get started. If you haven't checked it out recently, I encourage you to explore the latest additions and updates.
+
+## Main Site Improvements
+
+A large change has been the archiving of the "Implementation Domains" and "System Levels" pages. These pages served their purpose during the initial phases of FEASTorg while I explored the area and organization of the stack but have now been retired to streamline our documentation as we have progressed away from the exact ideas presented in those pages.

archive/README.md

@@ -0,0 +1,29 @@
+---
+layout: page
+title: Archive
+permalink: /archive/
+nav_order: 100
+has_children: true
+---
+
+## Archive
+
+This section contains archived concepts and documentation from earlier phases of the FEAST project. These materials represent the exploration and evolution of ideas during the initial development of FEASTorg.
+
+While these concepts are no longer part of the active project structure, they are preserved here for historical reference and to document the development process.
+
+## Contents
+
+- [Functional Implementation Domains](implementation-domains.md) - Original domain organization concept
+- [Hierarchical System Levels](system-levels.md) - Original hierarchical system structure
+- [Naming Organization (Old)](naming-organization-old.md) - Early naming and organizational framework
+- [FROOTS Concept](froots.md) - Firmware layer concept
+- [PROTINS Concept](protins.md) - Middleware layer concept
+- [SUGIRS Concept](sugirs.md) - Software interface layer concept
+- [BATCH Concept](batch.md) - System clustering concept
+- [OVEN Concept](oven.md) - Facility-level network concept
+- [VEGIES Concept](vegies.md) - User-fabricated hardware concept
+
+## Note
+
+These archived materials served their purpose during the conceptual phases of FEASTorg. The project has evolved beyond these specific organizational structures, but the foundational ideas continue to influence the current direction.

archive/batch.md

@@ -0,0 +1,14 @@
+---
+layout: page
+title: BATCH Concept
+permalink: /archive/batch/
+parent: Archive
+nav_order: 7
+---
+
+## BATCH Concept
+
+- **BATCH**
+  - Multiple LOAF subsystems can be bridged together in a leader-worker configuration to form a local device cluster to coordinate multiple processes to perform some integrated complex process
+  - This is referred to as **BATCH** which stands for _Bridging Architecture for Task Control & Handling_
+  - **Example:** Multiple LOAFs (e.g., one for a mechanical shredder, one for a chemical reactor, and one for a bioreactor,) to create a plastic upcycling system that converts PET waste into edible microbial protein.