Inpost and dpd to set on the Polish website Opencar 3

It is necessary to develop an online booking form for a beauty salon and integrate it into the existing website (landing page). The site is in the development stage (in HTML, CSS, JS). The site does not have its own database (and none is planned), so it is necessary to propose a free solution for storing and managing data that will be easy to administer and stable in operation. Required functionality: loading the list of service categories; loading services according to the selected category; loading the list of masters who perform the selected service; displaying available dates and free times according to the master's work schedule; creating a booking with automatic blocking of the selected time; protection against double booking. Data in the form: name; phone number; service category; service; master; date; time; comment (optional). Administration: There should be the ability to: add and edit service categories; add and edit services; add and edit masters; set the work schedule for each master; manage days off, vacations, and other periods of unavailability; view, edit, and cancel client bookings. Please specify: what solution you propose for data storage; estimated cost; completion time. Design is not important, the main thing is functionality. The person who does the site layout will design it in the required style.

I have some logic in Google Excel related to the integration with the Nova Poshta API and the Turbosms API. Overall, everything works fine, but some functionality needs to be added. All details will be discussed in correspondence. I will provide access to the Excel and the code. It is essential for the performer to have experience working with Google Excel JS in Apps Script.

Hello everyone, we need to create a website for event creation and ticket sales. Possible options include using a ready-made template, a framework, or your own solution. It is preferable that you have experience in developing websites for ticket sales. We will send examples of websites in private messages. If necessary, we will create a prototype. If you have previously worked on similar websites, please send examples in private messages. We will discuss the details in private messages. Thank you and have a great day!

The site is built on the Next.js framework (based on React). All points in the technical specification need to be completed. The technical specification is attached in the file. I look forward to your proposals.

Website for evaluation: https://copy.eurobrands-shop.de/ Task: fix frontend bugs at the Magento 2 / Amasty theme level: CSS/LESS/JS, mobile, RTL, minicart, language dropdown, layout shift/CLS. Work format: - without local Magento deployment; - work through DevTools + theme source files; - edits in CSS/LESS/JS/template files of the theme; - result: diff / commit / archive of changed files; - deployment and assembly on our side; - work through a secure deal; - NDA until the transfer of source files/accesses. What needs to be checked and evaluated: 1. RTL / Arabic version: - phone in the header is displayed incorrectly; - element offsets in header, minicart, wishlist/account, product page; - margins, direction, unicode-bidi, positioning. 2. Header: - language dropdown; - cart/wishlist; - hit-area of icons. 3. Minicart: - opens unstably on some pages; - check Console / Network / Event Listeners / customer-data / z-index / overlay. 4. Mobile: - cart/wishlist badges are too large; - Categories block is compressed/cut off; - mobile menu / Menu-Account. 5. Product page: - layout shift / CLS of images; - Add to Cart / Quantity / BOX / PALLET in RTL. 6. Wishlist/account: - /wishlist/ - /mwishlist/ - tabs, Back button, overflow of counters. Problematic URLs: - https://copy.eurobrands-shop.de/alpro - https://copy.eurobrands-shop.de/producers - https://copy.eurobrands-shop.de/wishlist/ - https://copy.eurobrands-shop.de/mwishlist/ In your response, please write: 1. Do you have experience with Magento 2 frontend? 2. Do you have experience with RTL? 3. How many hours do you need for the first stage? 4. What is the cost? 5. When can you start? 6. What accesses do you need? 7. Are you ready to work through a secure deal and sign an NDA? Important: a specific result is needed — corrections or a technical explanation for each point: fixed / not reproducible / not a frontend issue.