wieworki / web-project-with-php Goto Github PK

A table for all the business products needs to be made. It has to show:

• Product name
• Product description
• Product price
• A picture of the product

For now, the four propierties have to be recovered from the DB. For the image, the URL is going to be stored.

As a start, we need to be able to retrieve the rows from the table "editorial" so they can be loaded in the creation form of the products.
Since there are plans to add a filter at the public catalog according to "editorial", keep in mind this selection query should be public.

At some point, the users should also be able to add, remove or modify rows from the table "editorial". These actions should only be done by the registered users.

Now that there catalog table is functional, it needs to look good. This is the main page that the costumers will se, so we need to make it appealing. Feel free to change anything from the table structure, but keep the number of rows to 5, or the data won´t be loaded correctly from the DB.

Absolute routes doesnt seem to be working. We will use relative paths for now, but some way to ensure correct paths needs to be found.

Right now, the catalog table displays all the available products in the same page. This will bring troubles in the future, as more products are loaded in the DB. For now, a maximum of 10 rows should be displayed on the table, with the option of showing the next 10 products

Revamp the user management page, to make it responsive and more appealing

Make an option to create new users for admins. Change the db so there is a difference between admins and users.

The logged user needs to be able to access a section that lets edit, eliminate, and create new mangas, by a sub-menu of the catalog administration, following the option "Administrar títulos".

A manga item has a name, a description, an ilustrative image that will be linked by an stored URL, and a associated editorial

The name, description, and URL can be loaded by text inputs. The editorial has to correspond with the editorials stored in the DB, so the user should only have a combo box with the availibles options.

We will start with the front-end interface for now. The inputs can be represented using a table, like in the user management, or by a form structure with each input in a new row. Feel free to choose whatever option you like.

When the page width is small, the table columns doesn't fit the table

This needs to be fixed, in case the user needs to access this page in a mobile device. We can try with the "@media" property, that may let us adapt the size of the columns and the table according the width and height of the device.

Set up the current login system to make it validate the username and password from a table in a database

The catalog administration page will call php functions by AJAX to implement the changes in the DB.
The following functions needs to be implemented:

• New manga
• Update manga
• Delete manga

Keep in mind that the manga table has the following columns:

• id (auto)
• nombre
• descripcion (null)
• url_descripcion (null)
• id_editorial (null)

Even though some columns can have null values, the php should still ask for these parameters when it is called.

Improve the login interface. Right now it is lacking a return button, and the menu bar.

The CSS should be improved too, so it makes the page more appealing. We can try to use Bootstrap

Set up the Front End of a Login form

The user needs some way to search a product in the table. A search tab with suggestions would be a good adition. Some filters or some way to order the table according to the titles should be implemented too

Since the latest requirements analysis, some changes needs to be done in the DB structure. They will impact the way the application recover information from it, so some of the PHP functions, the AJAX calls from some JS functions and part of the front-end code, will need some changes.

The "manga" table now will have a many-to-one relation with the table "editorial", and a many-to-many relation with the table "genero". A new table, "volumen", will have a one-to-many relation with the table "manga". With this changes, the product catalog will now have at least one extra column for the volumes, and we will be able to make search by genre and by editorial.

The user table will remain the same, so user administration won't need any changes.

The changes will be applied in a new branch, "DB improvement".