Applying fragmentation, arrays, function.
Table of Contents
This is a Travel tour guide made to showcase the following: fragmentation, function, and arrays.
- Authentication & Authorization
- CRUD Operations for Invetory System
- Always use
AD-in the front of the Title of the Project for the Subject followed by your custom naming. - Do not rename
.phpfiles if they are pages; always useindex.phpas the filename. - Add
.componentto the.phpfiles if they are components code; example:footer.component.php. - Add
.utilto the.phpfiles if they are utility codes; example:account.util.php. - Place Files in their respective folders.
- Different file naming Cases
Naming Case Type of code Example Pascal Utility Accoun.util.php Camel Components and Pages index.php or footer.component.php - Renaming of Pages folder names are a must, and relates to what it is doing or data it holding.
- Use proper label in your github commits:
feat,fix,refactoranddocs - File Structure to follow below.
AD-Task-2
AD-Task-2
├── .php_tmp
├── .qodo
├── assets
│ └── css
│ │ └── style.css
│ └── img
│ ├── destinations.png
│ ├── guides.png
│ ├── indexbg.png
│ └── services.png
├── components
│ └── componentGroup
│ └── example.component.php
│ └── templates
│ └── example.component.php
├── docs
│ └── VS Code Profile ...
├── handlers
│ └── example.handler.php
├── inc
│ ├── data.php
│ ├── footer.php
│ └── functions.php
├── pages
│ ├── destinations
│ │ ├── assets
│ │ │ └── css
│ │ │ │ └── style.css
│ │ │ └── img
│ │ │ ├── cape-town.png
│ │ │ ├── kyoto.png
│ │ │ └── paris.png
│ │ └── index.php
│ ├── guides
│ │ ├── assets
│ │ │ └── css
│ │ │ │ └── style.css
│ │ │ └── img
│ │ │ ├── benjamin.png
│ │ │ ├── chiaki.png
│ │ │ └── daniel.png
│ │ └── index.php
│ ├── services
│ │ ├── assets
│ │ │ └── css
│ │ │ └── style.css
│ │ └── index.php
│ └── tips
│ └── assets
│ └── css
│ └── style.css
│ └── index.php
├── utils
│ └── Example.utils.php
├── .dockerignore
├── .gitignore
├── bootstrap.php
├── compose.lock
├── composer.sample.yaml
├── composer.yaml
├── Dockerfile
├── index.php
├── readme.md
└── router.php
The following should be renamed: name.css, name.js, name.jpeg/.jpg/.webp/.png, name.component.php(but not the part of the
component.php), Name.utils.php(but not the part of theutils.php)
| Title | Purpose | Link |
|---|---|---|
| destinations.png | This image serves as a banner or icon to represent the "destinations" section of the website, directing users to content related to travel locations. | www.canva.com |
| guides.png | This image is probably used as a banner or icon for the "guides" section, indicating content about travel guides or expert recommendations. | www.canva.com |
| indexbg.png | This image is the background image for the website's homepage (index.php), providing a visual foundation for the main landing page. | www.canva.com |
| services.png | This image acts as a banner or icon for the "services" section, visually representing the various offerings or features of the website. | www.canva.com |
| cape-town.png | Used within the "destinations" section, this image specifically showcases Cape Town, illustrating one of the featured travel destinations. | www.canva.com |
| kyoto.png | This image is found in the "destinations" section and highlights Kyoto, serving as a visual representation of this specific destination. | www.canva.com |
| paris.png | Located in the "destinations" section, this image depicts Paris, providing a visual reference for this popular travel spot. | www.canva.com |
| benjamin.png | This image is featured in the "guides" section and represents a specific travel guide named Benjamin, perhaps showing their photo or an avatar. | www.canva.com |
| chiaki.png | Found in the "guides" section, this image represents a travel guide named Chiaki, serving as their visual identifier on the page. | www.canva.com |
| daniel.png | Located within the "guides" section, this image represents a travel guide named Daniel, acting as their visual profile. | www.canva.com |
