Who I am
I build web systems for real use, not short-lived demos or decorative landing pages.
Personal portfolio
Mohamad Ghashim
I build practical web applications, clear admin systems, and APIs that can be relied on.
I focus on projects that need a clean foundation, clear logic, and delivery that can still be understood and extended later.
- Laravel APIs for products that need a stable and clear backend.
- Admin systems built for real day-to-day use.
- Full-stack delivery when the project needs frontend and backend together.
About
I prefer work that starts with a clear problem and ends with a system people can rely on.
I am not interested in surfaces that only look polished. What matters is a system that is clear, fast enough, and maintainable after delivery.
What I focus on
My focus is Laravel, REST APIs, admin dashboards, and web applications that need frontend and backend to work together cleanly.
How I work
I start by defining scope, then I organize structure and data, and only after that do I build the interface and logic.
Featured Work
Featured work
This section is reserved for real case studies that can be explained with screenshots, context, and results. No generic feature cards.
Frontend / 2026
TEC Oto Servis
A frontend marketing site for an automotive service center in Basaksehir, focused on services, training, and fast contact in Arabic and Turkish.
- Languages
- AR / TR
- React
- Vite
- Framer Motion
Full-stack / 2026
SyncNova
A task management web app built around Kanban boards, account registration, login, language support, and dark mode.
- Laravel
- React
- Tailwind CSS
Services
The work I offer
Direct, practical work without vague promises.
Services
Backend development
Application logic, data structure, and a foundation that stays easy to work with later.
Laravel APIs
Clear REST APIs for projects that need integrations, multiple interfaces, or a separate frontend.
Dashboards and internal tools
Operational systems built for daily use, permissions, tracking, and clear workflows.
Full-stack web apps
Frontend and backend together when the project needs one complete delivery from start to launch.
What I can build
Concrete deliverables
Examples of outputs that can be scoped clearly and delivered cleanly.
Operations dashboard
Permissions, states, tables, and clear daily workflows for teams or management.
Documented API
Organized endpoints, access control, and a structure that supports future integrations.
Client portal or internal system
Direct user flows for clients or staff with clear data movement and accountability.
Reporting and operations views
Pages that help daily decisions with useful signals instead of visual noise.
Stack
Technology I actually use
I prefer a stack that stays readable and maintainable.
Backend
- Laravel
- PHP
- REST APIs
- MySQL
Frontend
- Next.js
- TypeScript
- Tailwind CSS
- HTML
Systems
- Authentication
- Role-based access
- Dashboards
- Admin workflows
Delivery
- Git
- Vercel
- Deployment
- Technical documentation
Process
Practical steps from first brief to delivery
I handle projects in short, clear stages so the technical decisions stay understandable.
01
Understand the need
I define the goal, the user, and what the first useful version needs to do.
02
Set the scope
I split the work into screens, data, and permissions before I start building.
03
Build the core
I start with the database and API, then connect the interface to that structure cleanly.
04
Deliver and improve
I deliver a usable version with clear notes on what can be improved after launch.
Contact
If you have a suitable role or a clear project, we can talk directly.
The best messages are the ones that explain the need clearly: the problem, the scope, and the expected timeline.
Contact channels
You can start by email directly if you have not connected a form endpoint yet.
Send a message
Add a form endpoint in the locale file to enable sending.