Two small changes on the website (Joomla)

We are looking for an experienced Framer developer for the professional enhancement of the existing website of Azzurro Cabinets, a company operating in Central Florida, USA. Current website: https://azzurro.framer.website/ The project is based on the Modivana template in Framer. It is necessary to redesign the website structure for private clients, maintain a separate section for builders and contractors, create a managed CMS catalog of kitchen cabinets, update the completed projects section, and perform technical SEO settings. The company does not manufacture kitchen cabinets. Main services include: selling cabinets from suppliers, assistance with selection and planning, ordering and delivery, professional installation. Main tasks: • enhancement of the existing project on Framer without transferring to another platform; • removal of third-party template content and images; • redesign of the main pages of the website; • creation of a catalog of collections, styles, colors, and finishes through Framer CMS; • creation of dynamic pages for individual collections; • redesign of the Projects section through Framer CMS; • separate scenarios and forms for homeowners and builders; • adaptation for desktop, tablet, and mobile; • setup of forms, analytics, and technical SEO; • connection of the main domain; • transfer of a fully editable project and instructions for working with the CMS. Important: work is to be done only on Framer. Transfer to WordPress, Webflow, Wix, or another platform is not considered. A detailed technical assignment is attached to the project. In your response, please specify: Links to 2–5 completed websites specifically on Framer, separately highlighting projects with CMS. How you propose to organize the CMS for Cabinet Collections and Projects. An initial estimate of costs and timelines or the procedure for their approval. The number of included rounds of revisions. Which points of the technical assignment will require custom code or third-party integrations. Confirmation that the work will be performed in the client's project and fully transferred to the client. Cost, stages, and payment terms will be determined after reviewing the technical assignment and agreeing on the exact scope of work.

https://www.figma.com/design/bSzGOmDb3scdsBgjR3hHLb/Robo?node-id=0-1&p=f https://robo.org.ua/index.php?route=product/product&path=145802278&product_id=237 Task: redesign the product and reviews page on the main page The website is already developed and fully operational. The designer has prepared a new design in Figma that needs to be implemented on the existing site. It is necessary to: code the new design according to the layout; integrate it into the current site; adapt the pages for mobile devices, tablets, and computers; check the correct operation of buttons, forms, menus, and other elements; ensure maximum accuracy in matching the layout. There is no need to develop the site from scratch — only the redesign and replacement of the current design with the new one are required.

Development of an MVP online tutoring platform (analogous to Preply) for the Lithuanian marketProject description:We are looking for a team of developers or individual specialists (Full-stack / Backend / Frontend / UI-UX) to create a two-sided online learning marketplace for the Lithuanian market.The goal of the project is to launch a web platform that connects students with freelance tutors for conducting individual lessons in real time.Main functionality of the MVP: Tutor's cabinet: Profile with a video introduction, upload of diplomas, schedule setup (calendar) and hourly rates. Student's cabinet: Search by filters (subject, price, language, rating), purchase of lessons, personal class calendar. Search and filtering: Smart matching of teachers with a review and rating system. Virtual classroom: Integration of video communication (WebRTC, Zoom or similar), built-in chat and file sharing. Payment system: Secure transaction (Escrow). Freezing of funds and payment to the freelancer after lesson confirmation. Integration with Stripe / Paysera is needed.

Project essence We track trucks transporting goods for our clients (industrial factories). Autonomous GPS beacons TKSTAR TK-905B are issued to the trucks during loading (coordinates are transmitted every 5 minutes). The beacons are NOT permanently attached to the vehicles — they operate on a rotation scheme: the manager issues the beacon to the driver during loading, after the trip the driver returns the beacon with documents, and the same beacon is issued for the next trip with a different vehicle. A web platform is needed: the beacons send data to our server, clients (factories) log into the site and see their vehicles on the map in real-time. Each factory sees ONLY its beacons. Part 1. Backend Deploy Traccar (open-source) on a VPS. We purchase the VPS, the candidate recommends the configuration. Set up data reception from TK-905B beacons (the protocol is supported by Traccar out of the box). Assist with redirecting beacons from the Chinese server to ours (SMS commands). Multitenancy. Roles: Admin (us): sees all beacons, all companies, all trips. Creates companies and users, assigns trips to companies. Manager/dispatcher (our employee at the loading site): issues and receives beacons (see the rotation module). Client (factory): login/password, sees only its active trips and its history. Does not see other beacons, the free pool, and service information. Part 2. Beacon rotation module (key logic) Each beacon has a short number in the system (No.1, No.2, No.3...), matching the sticker on the case. Search for the beacon by this number. Issuance: the manager selects a beacon from the pool → enters the vehicle number (mandatory field) + optionally: full name/phone of the driver, direction/delivery point, client company. The operation should take seconds: one window, minimum fields. From the moment of issuance, the point on the map is marked with the vehicle number and trip (for example, “AH1234VH → Kyiv”), not the device ID. Re-issuance = closing the old trip + opening a new one. For the manager, it looks like “just entered a new vehicle number,” but the system must keep a history of bindings: each period of the beacon's operation is tied to the vehicle number that was active at that moment. Overwriting the number with loss of history is unacceptable (otherwise, old tracks will be marked with other vehicles). Trip completion and return of the beacon to the warehouse — two separate actions: the trip is closed upon unloading (the return path of the beacon with mail is not shown to the client), the return changes the beacon's status to “in the pool, free.” Free beacons (in the pool / charging / returning by mail) are not displayed on the client map. The admin sees them with statuses. History: for each beacon — all its past trips; for each company — all its trips. Part 3. Frontend (website) Page layout: In the center — a live map with vehicles in real-time (updating without page reload, WebSocket/polling). Vehicle icons; click on a vehicle → card: vehicle number, driver, direction, speed, time of the last mark, status (moving / stopped / no connection). On the right — profile panel of the logged-in user: company name, list of its active trips with online/offline statuses, quick access to the vehicle on the map. At the top — search for its beacons/vehicles (by vehicle number, beacon number, direction). Login page. Responsive for mobile (managers and clients will open from their phones). Functions: Route history for the selected period (playing back the track on the map). Parking report: where the vehicle was parked, from what time to what time, how many hours (example: “Kyiv, Tue 08:00 — Thu 09:00, 49 hrs”). Geofences: admin outlines zones on the map (factory, unloading points). Report on time in zones + notifications of entry/exit (in the interface; e-mail/Telegram — a plus, negotiable). Export reports to Excel/PDF — a plus. Part 4. Technical requirements Backend: Traccar API (REST + WebSocket). Custom rotation logic — a separate layer on top of Traccar (own service + DB) or through Traccar attributes, at the discretion of the performer, but with justification. Frontend: React or Vue. Map: Leaflet + OpenStreetMap (or Google Maps, if justified). Set up auto-cleaning of coordinate history older than 6 months (retention policy in Traccar / by agreement), so the database does not grow indefinitely. Reports and trip summaries for old periods must be preserved. Interface language: Ukrainian (Russian — a plus, switch not mandatory at the start). Data and server are fully ours: no ties to third-party closed services. Part 5. Project delivery Working platform on our domain. All accesses: VPS, Traccar, database, repository with code. Brief instructions (text or video): how to add a new beacon, how to create a company/user, how the manager issues and receives beacons. 2–4 weeks of support after delivery for bug fixes (negotiable). Questions for the candidate (must answer in the response) Have you deployed Traccar? Have you created a custom frontend on top of the Traccar API? Links/screenshots of examples. How do you propose to implement multitenancy and the rotation module (briefly, 3–5 sentences)? Timeline and price: (a) MVP — map, logins, rotation, parking; (b) full version with geofences and reports. Recommended VPS configuration for ~20–50 beacons.

A plugin needs to be developed. The goal is a convenient table for quick selection and purchasing of goods by wholesale buyers. Functionality Front: Columns - Product selection (check), Name, Category, Warehouse, Delivery, Price, Quantity selection, Add to cart, Clear filters search products in a list filter by categories filter by warehouses filter by delivery product quantity selection adding to cart Back: bulk price increase and decrease by % per warehouse