Croatia

Brief:&nbsp;My client asked for a website like this one&nbsp;https://www.qoqa.ch/de. It has to have a similar design, same structure and functionalities. Design Preferences:&nbsp;The design concept will be similar to to the reference website. We work in InVision. We'll set up some page templates and have a few corrections with the client. Once the client approves the design and structure, we'll hand out the materials to you for development. Any icons, logos, and image materials will be given to you. Site structure:&nbsp;A collection of One page webshops ( I call them subShops&nbsp;), each offering a single Product for a limited time. The product can have more options to choose from, multipacks or flavours.. Feel free to explore it additionally. Moreover, Each subShop has it's own blog, and all posts are merged under&nbsp; Menus and menu locations: 3 menu bars, and a side menu. I guess you will need at least 6 different&nbsp;menu locations. The HEADER contains two menu bars. The top one contains&nbsp;the logo and has two menu locations.&nbsp;The main navigation (all subShops, blog) and the language switcher aligned right with maybe a few more menu items. The bottom menu bar contains a&nbsp;button which opens the side menu and another menu location aligned right. The content of this bottom bar can change, and it sometimes gets another menu on the left, like on the blog page. The third menu&nbsp;bar contains "on page navigation" on the homepages of each webshop. Contains #tags to the Daily blog section, Highlights, and Specifications sections. Smoothscroll please.&nbsp;It is sticky and animated. Contains the number of comments on each product and a featured comment. The side menu has two locations stacked upon each other. The top one contains the pages related to your account, which I'll talk about more in the "Pages" section, and below that we have some other pages which can be accessed without logging in. And lastly, we have another simple menu in the footer. General pages: 1) A webshop page template (basically homepage) which will be reused across all shops. Each shop has its own subdomain. Each page has its own cart which can't be updated between subdomains. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- Hero header section with a youtube video opening onclick, Title and a subtitle, a progress bar with a counter (counting down time left to buy the product with this offer), a price tag and an add to cart button.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- Sticky secondary menu bar with #links to the next three parts of the page &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- a Daily blog section, Highlights, and Specifications about the product All subShops have these things in common, The last two sections should be editable by the client, as much as possible. What is your Headless CMS of choice? I think it would be great to have something like the WP gutenberg editor, and I'm open to see what do you propose. &nbsp; 2) Blog Archive - Each webshop has its own Blog and they all merge together by default and are ordered by date.&nbsp;Additional categories (Recipes and Tips) appear on the secondary nav. 3) Post page - I want to make an offer for 2 blog page templates, a standard one (which would fit almost all shop categories), and a custom one ( like for the recipe page, which also creates a downloadable PDF of the recipe ). Any additional page template and functionality will be charged to the client additionally as you like. 4) Offer History - a page where all previous offers can be found, sorted by category (subShop) and by year and month. 5) Contact and help information - this page has three sections which basically work in a similar way, you can click on different questions, and the answer appears on the right, and if that answer didn't solve your problem you can send a message to the customer support. Also, if the problem is product related, a list of all products that the user ordered appears and the user simply selects it. Let's limit it to 15 questions and answers for starters, and we can charge more later on if needed. 6) Vouchers - usable across all subShops, each purchase generates a downloadable voucher pdf for printing. All vouchers can be re downloaded on the "orders" page, but is also sent by email to the customer upon making a purchase. Not sure if the vouchers can add up or if they can be used one at a time. But i guess this is only one small detail, and it won't affect the offer. 7) Legal notice - lots of styled text.. as always 8) Concept - a pretty simple page which tells a little about the idea behind each individual subShop Account pages: 1) Profile - the user can change or set his avatar, nickname, first and last name, e-mail, phone number, language, password and connection to other apps.. for instance if he signed in with google or facebook, he can disconnect it there. 2) Address - The user can create and name different addresses and use them while making a purchase. 3) Orders - contains all orders.. not sure for how long they will be visible there after they are delivered. 4) Newsletter - that connects to Mailchimp. The page contains a list of on of switches for each subShop, e-mail address field for changing the address and a few check boxes 5) Favourite posts - contains all blog posts that the user marked for himself. Technology Preferences:&nbsp;MEAN Stack (AngularJS&nbsp;+ ExpressJS + NodeJS) seams like a good solution to me, but I don't have anything against React. The reference page, qoqa, is built with it, and it seems like the backend is handled by Ruby? Also, Materialize is a must for the front end. https://builtwith.com/qoqa.ch&nbsp;this is the build with profile I was reading through..&nbsp;As part of your application for this project, I would like if you&nbsp;

A custom eCommerce Multisite Website

Useful links

Company

Information

Content Writers

Freelancers

Freelance Jobs

Online Jobs

Designers

Developers

Translations