Update readme.md

This commit is contained in:
Remco
2026-05-13 19:15:45 +02:00
parent f5e01cd8f8
commit 06f622f655
+24 -19
View File
@@ -1,39 +1,44 @@
# EpicNabbo Catalogue v2 (In Development 🛠️)
EpicNabbo Catalogue v2 is a complete, ground-up rewrite of the original catalog system. Version 1 suffered from architectural bottlenecks due to an incorrect development approach. Version 2 rectifies these mistakes, delivering a highly optimized, clean database structure.
EpicNabbo Catalogue v2 is a complete, ground-up rewrite of the original catalog system, specifically engineered for **Nitro v3** with 100% full native support.
> ⚠️ **Status: Work In Progress (WIP)**
> This project is currently under active development. Features are being implemented rapidly using our new, corrected methodology. It is not yet ready for production use.
Version 1 failed to meet our strict quality standards due to a flawed development approach. To fix this, we are rebuilding the system from scratch using a highly optimized, improved methodology.
## 🚀 Key Objectives & Improvements over v1
> ⚠️ **Current Status: Active Development (WIP)**
> The core framework and base structure are now ready, but it is **not yet suitable for production use**. Estimated time to completion and final release is **a few weeks**.
* **100% Complete Goal:** Built to ensure all pages, tabs, and sub-items are fully implemented. Zero missing pages upon final release.
* **Blazing Fast:** Re-engineered from scratch. v2 loads and renders significantly faster than v1 due to an optimized indexing strategy.
* **Superior Structure:** Clean, logical database relationships and structured category trees replace the messy, unorganized approach of the previous version.
* **Faster Development Cycle:** By fixing our initial approach, development is moving much faster than v1, despite being built from the ground up.
## 🚀 Key Improvements & Objectives over v1
* **Native Nitro v3 Support:** Specially tailored to fully support all Nitro v3 features and packet structures out of the box.
* **Meeting High Quality Standards:** Re-engineered to fix the quality issues that caused v1 to fail our internal benchmarks.
* **100% Complete:** All pages, tabs, and sub-items are being structured properly. Absolutely zero missing pages upon release.
* **Blazing Fast:** Re-architected with optimized database indexing, resulting in much faster loading times than v1.
* **Better Development Approach:** By correcting our past mistakes, development is moving significantly faster despite building everything from scratch.
## 📈 Comparison
## 📈 Comparison (Targeted Outcomes)
| Feature | Version 1 (Old) | Version 2 (New) |
| :--- | :--- | :--- |
| **Status** | Completed (Flawed) | **In Active Development** 🛠️ |
| **Completeness** | Missing pages & broken links | 100% Complete (No missing pages) |
| **Status** | Discontinued (Failed Quality Checks) | **In Development (Base ready)** 🛠️ |
| **Nitro v3 Support**| None / Partial | **100% Full Native Support** |
| **Completeness** | Missing pages & broken links | 100% Complete & verified |
| **Performance** | Slow loading / poor queries | Blazing fast architecture |
| **Database Structure** | Unorganized / brute-forced | Clean, indexed, and modular |
| **Development Speed**| Slow due to troubleshooting | Near-instant deployment |
| **ETA** | - | **A few weeks** |
## 🛠️ Current Roadmap
- [x] Analyze v1 bottlenecks and fix core architecture.
- [/] Rebuild database schema and indexing structure (In Progress).
- [ ] Port catalog pages to the new layout.
- [ ] Final testing and verification (Zero missing pages check).
- [x] Analyze v1 bottlenecks and define new quality standards.
- [x] Implement core database framework and base architecture.
- [/] Integrate full Nitro v3 compatibility hooks (In Progress).
- [ ] Port and organize all catalog pages (No missing pages target).
- [ ] Final quality assurance testing.
## 📦 Installation (Development Preview)
## 📦 Getting Started (Development Preview)
1. Clone this repository:
```bash
git clone gitlab.com
```
2. Check the active development branches for the latest updates.
2. Keep an eye on the development branches for daily updates over the next few weeks.