Update index
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# **🐦🔥Order of the Phoenix — Website Development**
|
||||
# **🐦🔥 Order of the Phoenix — Website Development**
|
||||
|
||||
## **About the Project**
|
||||
## **📌 About the Project**
|
||||
|
||||
This repository contains documents, resources, and projects created during the **first phase of the Order of the Phoenix initiative** — a self-organized learning movement started by a group of computer science students.
|
||||
|
||||
@@ -8,72 +8,101 @@ What began as an effort to escape a passive academic environment evolved into a
|
||||
|
||||
The goal wasn’t just to learn a technology; it was to foster **self-driven learning, teamwork, and real-world problem-solving**.
|
||||
|
||||
---
|
||||
|
||||
## **Section 1 — Introductory Sessions**
|
||||
|
||||
The first part of the program focused on equipping everyone with fundamental web development skills.
|
||||
## **📚 Introductory Sessions**
|
||||
|
||||
### **Roadmap of What We Learned**
|
||||
1. **Web Fundamentals** — HTTP, REST, and the client-server model
|
||||
2. **MVC (Model-View-Controller)** — basics of application structuring
|
||||
3. **Web API Development** — designing and consuming APIs
|
||||
4. **ASP.NET Core Basics** — setting up and building modern backends
|
||||
The first part of the program focused on equipping everyone with fundamental web development **and solid software architecture principles**.
|
||||
|
||||
These sessions ensured that all participants, regardless of prior experience, could contribute to a real-world project.
|
||||
### **🗺️ Roadmap of What We Learned**
|
||||
|
||||
---
|
||||
1. **🌐 Web Fundamentals** — HTTP, REST, and the client-server model
|
||||
2. **🧩 MVC (Model-View-Controller)** — basics of application structuring
|
||||
3. **⚙️ Web API Development** — designing and consuming APIs
|
||||
4. **🚀 ASP.NET Core Basics** — setting up and building modern backends
|
||||
5. **🛠️ Dependency Injection (DI)** —
|
||||
- Why DI is crucial for **maintainability & testability**
|
||||
- Understanding ASP.NET Core service lifetimes (Transient, Scoped, Singleton)
|
||||
6. **🏗️ Design Patterns** —
|
||||
- **Repository Pattern** for data abstraction
|
||||
- **Unit of Work** for transaction management
|
||||
- **Factory & Builder** for complex object creation
|
||||
7. **🏛️ Clean Architecture Fundamentals** —
|
||||
- Separating **Domain, Application, and Infrastructure** layers
|
||||
- Designing business rules independent of frameworks
|
||||
|
||||
## **Section 2 — Project-Based Sessions**
|
||||
These sessions ensured that all participants, regardless of prior experience, could contribute to a real-world, **well-architected project**.
|
||||
|
||||
|
||||
|
||||
## **💻 Project-Based Sessions**
|
||||
|
||||
Once the fundamentals were solid, we moved to building a **real project**.
|
||||
### **Planning Phase**
|
||||
- Selected the project collaboratively (**Transportation Management System**)
|
||||
- Designed a detailed **ERD (Entity Relationship Diagram)**
|
||||
- Wrote **full documentation** to standardize the development process
|
||||
|
||||
### **Implementation Phase**
|
||||
### **📝 Planning Phase**
|
||||
|
||||
Each member implemented their **own version** of the project, applying Clean Architecture principles and experimenting with different approaches.
|
||||
- ✅ Selected the project collaboratively (**Transportation Management System**)
|
||||
- ✅ Designed a detailed **ERD (Entity Relationship Diagram)**, identifying entities, aggregates, and relationships
|
||||
- ✅ Wrote **full documentation** — requirements, use cases, and architecture diagrams
|
||||
|
||||
### **Project Overview**
|
||||
### **🔨 Implementation Phase**
|
||||
|
||||
#### **Backend — Transportation Management API**
|
||||
- **Tech Stack**: ASP.NET Core, Entity Framework Core
|
||||
- **Architecture**: Clean Architecture for modularity, testability, and maintainability
|
||||
- **Features**: Manage travelers, routes, tickets, and vehicle operations
|
||||
Each member implemented their **own version** of the project, following Clean Architecture guidelines while experimenting with different approaches.
|
||||
|
||||
#### **Frontend — Transportation Management Web App**
|
||||
|
||||
|
||||
### **🚦 Project Overview**
|
||||
|
||||
#### **🔗 Backend — Transportation Management API**
|
||||
|
||||
A **Clean Architecture-based** backend designed to be **modular, testable, and scalable**.
|
||||
|
||||
**Key Highlights:**
|
||||
|
||||
- **Domain Layer** 🏛️
|
||||
- Defined **entities**
|
||||
- Applied **domain rules** to ensure data consistency
|
||||
- **Application Layer** ⚙️
|
||||
- Contained **service classes** (e.g., `TicketOrderService`, `AccountService`) that orchestrated business logic.
|
||||
- Services handled **validation, entity manipulation, and coordination between repositories**.
|
||||
- Mapped DTOs to entities for input/output separation.
|
||||
- **Infrastructure Layer** 🗄️
|
||||
- Implemented **Repository & Unit of Work patterns** using Entity Framework Core.
|
||||
- Database interactions abstracted behind interfaces.
|
||||
- **Presentation Layer** 🌐
|
||||
- ASP.NET Core RESTful Web API
|
||||
|
||||
✅ **Why Clean Architecture?**
|
||||
- Clear **dependency direction** (outer layers depend only on inner ones).
|
||||
- Easier testing (business logic independent of frameworks).
|
||||
- High **maintainability and scalability**.
|
||||
|
||||
#### **🎨 Frontend — Transportation Management Web App**
|
||||
- **Tech Stack**: React, TypeScript, Zustand, Axios, Tailwind CSS
|
||||
- **Focus**: Clean, scalable architecture and user-friendly experience
|
||||
- **Focus**: A simple but modern UI to consume the API and simulate real-world use cases
|
||||
|
||||
---
|
||||
|
||||
## **Projects by Members**
|
||||
## **👥 Projects by Members**
|
||||
|
||||
| **Member** | **Projects** |
|
||||
| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| **Mehrdad Shirvani [GitHub](https://github.com/MehrdadShirvani)** | [Backend API](https://github.com/MehrdadShirvani/AlibabaClone-Backend) • [Frontend Web App](https://github.com/mehrdadShirvani/AlibabaClone-Frontend) |
|
||||
| **[Member 2 Name] [@GitHub](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#)** | [Backend API](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) • [Frontend Web App](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) |
|
||||
| **[Member 3 Name] [@GitHub](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#)** | [Backend API](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) • [Frontend Web App](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) |
|
||||
| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| **Mehrdad Shirvani [🐙 GitHub](https://github.com/MehrdadShirvani)** | [Backend API](https://github.com/MehrdadShirvani/AlibabaClone-Backend) • [Frontend Web App](https://github.com/mehrdadShirvani/AlibabaClone-Frontend) |
|
||||
| **[Member 2 Name] [🐙 GitHub](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#)** | [Backend API](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) • [Frontend Web App](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) |
|
||||
| **[Member 3 Name] [🐙 GitHub](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#)** | [Backend API](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) • [Frontend Web App](https://chatgpt.com/c/687a15ad-ab40-8010-8a9d-283c227b7bc3#) |
|
||||
|
||||
---
|
||||
|
||||
## **Acknowledgements**
|
||||
## **🙏 Acknowledgements**
|
||||
|
||||
A heartfelt thanks to:
|
||||
- **All members** who dedicated their time and energy, despite busy schedules
|
||||
- **The core team** who stayed committed through challenges
|
||||
- Everyone who believed in creating a culture of **self-driven learning**
|
||||
---
|
||||
## **Aspirations for the Project**
|
||||
- Everyone who believed in creating a culture of **self-driven, high-quality software development**
|
||||
|
||||
This is just the beginning. Our goals moving forward include:
|
||||
## **🚀 Aspirations for the Project**
|
||||
|
||||
- **Publishing all documents and projects publicly** for others to learn from
|
||||
- Expanding into **more advanced technologies** (cloud, microservices, distributed systems)
|
||||
- Building a **community-driven tradition** of collaboration, growth, and solving real problems
|
||||
This is just the beginning. Our future goals:
|
||||
|
||||
_"May this small spark inspire greater movements."_
|
||||
- **Publishing all documents and ERDs publicly** for others to learn from
|
||||
- Growing this into a **community-driven tradition** of collaboration and solving real problems
|
||||
|
||||
_"🔥 May this small spark inspire greater movements."_
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user