Script for Automatic Thread Creation on Forums

We're looking for a developer to fix a few issues in an existing system that monitors public tenders from Brazil’s PNCP. The platform is already live and built with Next.js, TypeScript, Supabase, PostgreSQL, and Vercel. Current issues include: * “Failed to query editais: Bad Request” with certain filters * The “Not reviewed” filter failing as the number of records grows * Possible pagination or Supabase query limit problems The work includes reviewing the code, reproducing the issues, applying stable fixes, testing the affected filters, and deploying the corrections to production. This is a small maintenance task, not a new development project. Please send your experience with Next.js and Supabase, availability, estimated delivery time, and price.

General information It is necessary to develop a simple minimalist web system, the main purpose of which is to maintain a client database, create appointments for visits, and automate the process of confirming visits via SMS, sending one-time links through the API from the service itself. The project is being developed in stages. In the first stage, it is necessary to implement only the basic functionality (MVP) so that the system can be used in real work. After launch and testing, it will gradually be expanded with new modules.Main functionality of the first stage User authorization; Client database; Creating and editing appointments; List of appointments (or a simple calendar); Switching between points of sale; Integration with the SMS operator via API; Sending SMS with any text or link for visit confirmation; Confirmation or cancellation of the visit by the client via a one-time link; Displaying the confirmation status directly next to the client's appointment. At the initial stage, instead of a full calendar, the use of a simple list of appointments by days is allowed. Each day should contain a chronological list of bookings indicating the time, client's name, service, employee, and confirmation status. Later, this list can be replaced with a full calendar without changing the system structure. The system must have the ability to switch between points of sale. Each point of sale has its own list of appointments (or calendar), but they all use a common client database.

Project: landing page for student recruitment for a manicure/pedicure academy based at LÁSKA Beauty Studio (Frýdek-Místek, Czech Republic). Website languages: Czech (main) + Ukrainian (language switch). Goal: application for the course through the form on the website Target audience and course information (programs, prices, target audience profiles): will be provided to the contractor after the work starts. Landing page structure: in the attached file (ready to discuss) Design references Palette and style — brand book will be provided Landing pages that are liked: thezeny.cz, makeupinstitute.cz Functional requirements Responsive layout (desktop/tablet/mobile). Language switch CZ/UA (all content duplicated). Application form with validation Google Maps with the studio in Frýdek-Místek. SEO markup + microdata Course/LocalBusiness. Consent for personal data processing (GDPR).

Looking for an experienced Go developer to participate in a project. Confident knowledge of Go, experience in backend/API development, working with databases, and Git is required. Experience with Docker, Kubernetes, and microservices architecture will be a plus.

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.