For Designers
PHPTRAVELS guide for designers: how the v10 views, themes and front-end assets are organised, so you can restyle your travel booking website safely.
This guide explains where PHPTRAVELS v10 views, themes and front-end assets live, so you can restyle a travel booking website without breaking upgrades.
Where templates live
PHPTRAVELS v10 renders HTML from view files under the application views directory. The routing documentation describes views under paths such as /v10/app/views (exact folder layout can vary slightly by package layout; confirm on your installation).
Related developer reading:
Routing System -- how requests reach controllers and views
For Developers -- stack overview
Safe restyling principles
Prefer theme / override layers -- Change logos, colours and CSS through the theme or documented override locations instead of editing core files you will lose on update.
Keep a diff list -- Record every core file you must touch so you can re-apply after upgrades.
Do not remove required booking markup -- Search forms, checkout fields and payment containers often need specific IDs/classes for JavaScript.
Test mobile and RTL if you enable those languages.
Re-test checkout after any CSS/JS change that touches forms or buttons.
Logos, colours and CSS
Replace logo image assets used by the active theme; keep filename conventions if the theme references fixed paths.
Override colours via theme variables or a custom CSS file loaded after the main stylesheet.
Avoid editing minified vendor bundles when a source SCSS/CSS file exists.
Front-end assets
Static assets (CSS, JS, images) usually sit with the theme or under public asset folders. Clear caches (browser, CDN, any app cache) after deploying CSS/JS changes.
When designer docs are incomplete
Until full designer documentation ships:
Keep this page unlisted, or
Link designers to For Developers and the Routing System page for structure only
Use Submit Ticket for theme questions that need product engineering input
Last updated
Was this helpful?