EBAY STORE PARTYTOYS

PROJECT OBJECTIVE

To reach at a large level, thus it also helps merchants make and manage their sales.


PROJECT REQUIREMENT

Online store is designed with the element or plug in, which makes it great solution for attracting and engaging customers. The perquisites while considering a design for a party toys store is as follows:-

1)Home Page:-The page which entertains people and give them a short piece of information about your services.

2)About page:-Where you can showcase a bit more information about your store.

3)Sale page:-Here you can showcase your products, sidebar with categories and filter.

4)Store Page:-Which is a copy of the sale page, however you can use it to place the products subcategories.

5)Blog page:-Where your posts are showcased in a listing layout.

6)Contacts Page:-For people to find you where you are located.


CHALLENGES FACED

1)Design for mobile:-A vast array of mobile devices accomplishes a variety of tasks while running tons of applications. The plethora of device options means that you need to account for a wide assortment of display sizes in the design process.

2)Frameworks that work:-The concept of responsive design provides for a optimal viewing and interaction across many devices. Media queries are rules to developers write to adapt designs to specific screen widths or height. Writing these from scratch can be time consuming and repetitive.

3)Organizing a large code base:-Depending on the size of a web project, the front-end code can be difficult to organize. Creating an organizational standard all developers on a team should follow is a challenge faced..


SOLUTIONS

To avoid or minimize those problems is to build in a modular way

1)The modular Button:- A modular approach would be to write code which you can reuse. It means cleverly separation of styles. The. button class contains the styles every button in your project uses, so you don’t have to repeat it. Your button module could end up consisting up several independent buttons, ready to be used whenever you need them.

2)Creating as standalone elements:- The aim is to create modules which are standalone elements, independent of other modules, when combined, these modules will form templates, where you simply reuse the modules as needed and work towards completing your design

3)Implementing SMACSS ("in shot smacks") scalable and modular architecture for CSS:- Implementing SMACSS will examine your design process and in a way fit those rigid frameworks into a flexible thought process.

4)Involving the Client:- Keep the client in loop and get their confirmation. The beauty of the development process is that clients can be active members of your team. You can safely show them the modules and they can overlook the process and pitch in at all times to make product better

5)Building a prototype:- By building gas prototype, that is exactly what you will get in the early phase of the project. Where static mockups and IN Vision fall short, HTML prototypes excel. The prototype serves as a perfect responsive deliverable for your clients. And once client is satisfied by the look and feel of the prototype, all you need is to polish it until it works the way it needs to. Build, Test, iterate


TECHNOLOGIES

Html5, CSS3 etc.


ebay-partytoys-casestudy