Trimly is a modern, all-in-one management platform designed exclusively for hair salons. Built with the real needs of salon owners in mind, Trimly helps businesses organize their daily operations, grow their client base, and maintain a strong online presence — all from a single, easy-to-use system.
Trimly is developed for the Greek market and beyond, combining powerful salon tools with a clean, modern user experience.
Trimly acts as a specialized CMS for hair salons, bringing together business management and online visibility into one platform.
With Trimly, salons can:
- Manage appointments and schedules efficiently
- Organize services, pricing, and staff
- Maintain a professional salon website
- Communicate clearly with clients
- Gain insights into their business performance
All features are designed to be simple, fast, and practical — without unnecessary complexity.
Trimly helps salons stay organized and avoid double bookings by offering:
- Centralized appointment scheduling
- Clear daily and weekly views for staff
- Easy management of working hours and availability
- Better control over busy and off-peak hours
This allows salon owners and employees to focus more on clients and less on administration.
Salons can fully customize their offerings inside Trimly:
- Create and manage services (haircuts, coloring, treatments, etc.)
- Set prices and durations per service
- Assign services to specific staff members
- Organize team members and roles
Everything stays structured and easy to update as the business evolves.
Trimly is not just an internal tool — it also powers the salon’s public website.
Through Trimly, salons can:
- Showcase their services and pricing
- Present their team and salon identity
- Share contact information and opening hours
- Maintain a professional, modern online image
The website is directly connected to the salon’s data, ensuring consistency and saving time.
Trimly provides useful insights that help salon owners make better decisions:
- Overview of appointments and workload
- Visibility into popular services
- Better understanding of salon performance over time
These insights help salons grow sustainably and plan ahead.
Trimly is built specifically for:
- Independent hair salons
- Small and medium-sized salon businesses
- Salon owners who want simplicity without losing control
- Teams that need a reliable, modern management tool
No generic features — only what salons actually need.
Trimly is developed using modern, reliable technologies to ensure speed, security, and scalability:
- A robust backend for business logic and data
- A fast, responsive dashboard for salon management
- A modern website frontend for clients
The platform is designed to grow alongside the salon.
Trimly’s mission is simple:
Help hair salons run their business effortlessly while looking professional online.
By combining management tools and a salon-focused CMS, Trimly allows salon owners to spend less time on administration and more time doing what they love.
Welcome to Trimly — smart salon management, made simple.
This wiki is the central knowledge base for the Trimly team. It is written for everyone involved in building, maintaining, and growing the Trimly platform.
The goal of this wiki is to:
- Create a single source of truth for how Trimly works
- Help new team members onboard quickly
- Document decisions, processes, and standards
- Reduce tribal knowledge and repeated questions
If it’s important to Trimly, it should live here.
This documentation is intended for:
- Developers – backend, frontend, and infrastructure
- QA & Testers – testing strategies, environments, and flows
- Product & Operations – features, workflows, and business rules
- Sales & Support – product understanding, use cases, and limitations
- Future team members – onboarding and context
Each section is written with its audience in mind, but clarity for everyone is always the priority.
- Start from the high-level concepts before diving into technical details
- Prefer clear explanations over assumptions
- Keep documentation practical and up to date
- When in doubt, document why a decision was made — not just what was built
This wiki evolves alongside the product.
The wiki will be organized into clear sections, such as:
- Product Overview – what Trimly does and why
- Architecture – system design, backend & frontend structure
- Backend (Laravel) – layers, conventions, APIs
- Frontend (Next.js) – patterns, hooks, components, styling
- Dashboard – internal salon management features
- Website – public-facing salon websites
- Testing & QA – test strategies and environments
- Deployment & Infrastructure – servers, CI/CD, environments
- Sales & Support – product capabilities, FAQs, limitations
- Guidelines & Decisions – standards, conventions, and rationale
Each section should be independently understandable and easy to extend.
This section collects important links used daily by the Trimly team. It serves as a quick entry point to all external and internal tools related to the product.
- Backend API – Internal API powering the dashboard and website
- API Documentation – Endpoints, authentication, and data contracts
- Postman / API Client – Shared collections for development and testing
Exact URLs and credentials should be added and maintained here.
- Dashboard – Internal salon management interface
- Admin / Internal Pages – Non-public tools used by the Trimly team
- Huly App – Project management, tasks, and team collaboration Huly link
- Architecture Overview – System design and high-level flows
- Backend Docs (Laravel) – Layers, conventions, and patterns
- Frontend Docs (Next.js) – Hooks, facades, components, styling
- Testing & QA – Test plans, environments, and release checks
- Deployment & Infrastructure – Servers, CI/CD, environments
This section should be kept up to date, as outdated links slow everyone down.
When contributing to this wiki:
- Write for someone new to the project
- Avoid unnecessary jargon
- Prefer examples over abstract explanations
- Keep sections small and focused
- Update docs when behavior changes
Good documentation is part of the product.
As Trimly grows, this wiki should become:
- A complete onboarding guide for new hires
- A reference for technical and product decisions
- A bridge between technical and non-technical teams
Trimly is built for the long term — and so is this documentation.