A back-office application for managing a web-hosting company's website, orders, registrations, trainings and clients — built during an internship.
🖼️ Screenshots · ✨ Features · 🌐 Company Website
Note
The source code is not public. This application was built for a company, and the code remains its property. This repository documents the work through a description and screenshots. A live walkthrough of the code is available on request — see See More.
- Overview
- What this project demonstrates
- Features
- Screenshots
- Tech Stack
- Architecture and Workflow
- Privacy and Confidentiality
- Technical Challenges and Learnings
- Possible Improvements
- See More
- Author
- License
This project was developed during my internship at Giga Manager (Béni Mellal, Morocco), a company providing web hosting and website development services. The company also sells business applications (for example school, pharmacy and optician management), website templates and training courses.
I built an administration dashboard that lets the team manage all of this from a single interface: incoming orders, user registrations, training programs, website template requests, quotes and clients. It also covers content updates on several pages of the company's official website, and I directly modified some pages of the live site as part of the work.
| Context | Internship project |
| Company | Giga Manager, Morocco |
| Source code | Private — property of the company |
- Delivery for a real company, not a tutorial exercise: real business modules, real workflows
- Back-office development in PHP and MySQL across many related entities
- Everyday admin UX: search, filters, date ranges, status badges, counters, card and table views
- Building on an existing template (Gentelella / Bootstrap) and turning it into a coherent application
- Working on a live website, with a local development environment and deployment by FTP
- Professional discretion: sharing the work publicly without exposing source code, client data or credentials
The interface is in French, the working language of the company's customers. The main modules are:
| Module | What it does |
|---|---|
| Dashboard | KPI cards (orders, administrators, trainings, registrations, classes, revenue) with trend indicators, a database overview with counters, and global performance bars |
| Orders | Full order list with per-category counts (web applications, hosting, digital marketing), search by name, e-mail or ID, and status filtering |
| Registrations and requests | Management of registrations, internship applications, contact messages and quote requests, with search, category and date-range filters, and view / e-mail / delete actions |
| Email history | History of the e-mails sent from the quote-request module |
| Trainings | Course catalogue as cards, with status, click counter, group management, pricing, pause / edit / delete actions, and a customer-reviews list |
| Sites and templates | Website template catalogue and a request pipeline with statuses such as price decision and payment validation |
| Packs and pricing | Management of the offers and price plans sold by the company |
| Clients | Client cards with logo, city, business sector and status; add, pause, edit and delete |
| Renewals | Subscription overview showing whether each order is active or inactive, with a renew action |
| Administrator profile | Edit personal information, role, status and avatar; last-login indicator |
All screenshots come from a real development environment.
 Dashboard — KPIs, database overview, global performance |
 Orders — categories, search and status filter |
 Internship requests — search, category and date filters |
 Template requests — price decision and payment validation |
 Renewals — active / inactive subscriptions |
 Quote requests — filters and e-mail history |
 Administrator profile — account and role |
 Clients — card view with status and actions |
 Trainings — catalogue, groups and pricing |
| Layer | Technology | Role in the project |
|---|---|---|
| Back end | PHP | Server-side logic and pages |
| Database | MySQL | Relational storage for orders, users, courses, clients and more |
| Admin interface | Gentelella (HTML, CSS, JavaScript, Bootstrap) | Template adapted into the dashboard |
| Local environment | XAMPP | Apache, PHP and MySQL on the development machine |
| Database tooling | Adminer | Managing the database during development |
| Deployment | FTP | Publishing updates to the live website |
| Versioning | Git and GitHub | Version control |
flowchart LR
ADM([Administrator]) -->|browser| D["Admin dashboard<br/>PHP + Gentelella"]
D --> M["Modules<br/>orders · registrations · trainings<br/>sites · clients · renewals · quotes"]
M --> DB[(MySQL database)]
flowchart LR
A["Local development<br/>XAMPP: Apache · PHP · MySQL"] --> B["Adminer<br/>database management"]
A --> C["Git and GitHub<br/>version control"]
A -->|FTP| D["Live website<br/>updates"]
Because the code belongs to the company, this repository contains no source code, no database schema, no credentials and no configuration files.
The screenshots were taken in a local development environment, and personal data such as e-mail addresses, phone numbers and revenue figures has been masked.
-
Organising a large back office. The dashboard covers many related entities: orders, registrations, courses and groups, templates, clients, renewals and quotes. Keeping the data organised in a relational MySQL schema, and the navigation consistent across modules, was the core structural challenge.
-
Adapting an existing template. Gentelella provides the layout, but turning it into a coherent French-language application — filters, status badges, counters, card views — meant reading and reshaping someone else's HTML, CSS and JavaScript rather than writing everything from scratch.
-
Working on a live website. Since I also edited pages of the company's live site, changes had to be prepared carefully in a local XAMPP environment and then published by FTP.
-
Sharing work under confidentiality. Documenting the project publicly without exposing code, client data or credentials required deciding what could be shown, and masking the rest.
If I rebuilt this project today, I would explore:
- Replacing the page-per-script structure (
commandes.php,clients_liste.php) with routing and an MVC framework such as Laravel or Symfony - Automated tests and a CI pipeline
- Granular roles and permissions beyond a single administrator role
- An audit log recording administrator actions
The source code is private, but I'm happy to walk through it and run the application live during an interview or a call.
El_Tousy — Computer Science student
This is not an open-source project. This repository is a portfolio overview only. The application and its source code remain the property of Giga Manager, and the screenshots and company branding may not be reused without permission.