Management of the main page template of the yii2 site

Technical assignment for the development of functionality for managing templates of the main page of the website

1. General information

Project: https://confideline.com, Yii2.
A ready-made solution that includes a user part and an admin panel.

• Download the website archive for study from the link: https://drive.google.com/drive/folders/10xJQTxa3abY-7r4tPG9eBJpE7hGJUqIo?usp=drive_link

Task:
Implementation of functionality for selecting the display of the main page of the website using various templates.

2. Functional requirements

2.1 Template management

It is necessary to create a template management page https://confideline.com/admin/theme/theme-variants, where the administrator should be able to:

• Upload new templates in the form of zip archives.

• Select the active template for displaying the main page, registration page, and authorization page.

• Delete unnecessary templates.

2.2 Template storage

• Templates are placed in a directory, for example, /templates/home/.

• Each template is a folder with files (HTML, CSS, JS, images).

• The structure of templates should be organized and flexible, allowing new templates to be added without changes to the code.

2.3 Selection of the active template

• The selected template is saved in the database.

• When loading the page, the server loads the files of the active template.

2.4 Uploading new templates

• The administrator selects a zip archive with the template on their computer and uploads it to the server.

• Templates are prepared by the layout designer, after which they are handed over to the administrator for upload.

• The admin panel interface allows uploading a zip archive, which is automatically unpacked into a new folder.

• The upload form should include:

  • A field for uploading a zip file.

  • A field for entering the template name (if the name is not entered, the default name of the archive file will be used).

• After uploading, the archive is unpacked into a folder, for example /templates/home/, where a new folder with the template name is created. The new template will be available in the list of templates.

2.5 Deleting templates

• When deleting a template:

  • All files from the corresponding folder are deleted.

  • The template disappears from the list of available templates.

3. Functional requirements

3.1 Admin panel

The "Template Management" section:

• A list of available templates displaying folder names.

• Options for each template:

  • "Select" — make the template active for the main page, authorization, and registration pages.

  • "Add new template" — upload a new zip archive.

  • "Delete" — remove the template from the server.

3.2 Working with files

• Uploading and unpacking a zip archive:

  • Creating a new directory in /templates/home/.

  • Unpacking the contents of the archive.

  • Checking the integrity of files (presence of index.php, style.css and other mandatory files).

6. Template structure

Each template should be organized in a separate folder and include:

• index.php — main HTML file.

• style.css — styles.

• script.js — JavaScript file.

• Images and other resources.

7. Features

• There should be a possibility to add new templates without the need to change the code or the system structure.

6. Example of how this is implemented in another project

An example of how this can be implemented:

Step 1 - select the theme name from previously uploaded - black - main page BlackHugs

https://prnt.sc/lsDWAAiff4Xm

https://prnt.sc/hAwS0t9auG85

Step 2 - select the theme name from previously uploaded - asian - main page AsianHugs

7. Use case

1. The administrator enters the "Template Management" section.

2. Sees a list of available templates.

3. Selects the active template (the result is immediately displayed on the site).

4. Uploads a new template via zip archive.

5. Deletes unnecessary templates.

8. Readiness criteria

• The functionality uploads, displays, and deletes templates through the admin panel interface.

• The selected template is displayed on the main page without the need to edit the code.

• All admin actions are logged.