Budget: 1000 UAH Deadline: 1 day
hi there
This is a very basic stub of my bet. it will be either updated or revoked later
Project Description:
We need a frontend developer to set up dynamic loading of messages in Next.js 14 (app router) using Next Intl. It is necessary to implement loading of different message files depending on the page.
Task:
Organize the structure of importing messages so that they are dynamically loaded according to the current page.
Example:
On the main page, load messages from default(en/main/main.json).
On the destinations/north-america page, load standard messages and additionally messages from en/continents/north-america/main.json.
Required Experience:
Experience working with Next.js 14 app router and next-intl.
Budget: 1000 UAH Deadline: 1 day
hi there
This is a very basic stub of my bet. it will be either updated or revoked later
Не могу откликаться в проект, напишу здесь)
Есть большой опыт с Next js.
Пишите обсудим детали
Можна більше деталей про проект? розбивка даних локалі по окремих сторінках то в певній мірі дивна річ. має бути вагомий привід до того
У нас для каждого континента и каждой страны будут свои переводы, сотни строк текста в каждом файле, для того чтобы не грузить все 250+ файлов стран и 6 континентов переводов на каждой странице, было принято решение их разделить.
Файловая структура готова нужно только переделать дефолтный механизм загрузки messages в динамический по странице
ну, ок. загальна ідея зрозуміла. тоді добре лягяає наступний принцип:
одна мова -- один файл зі всіма строками для всього сайту.
а для чого дробити на континенти та сторінки? (якщо я правильно зрозумів ваш опис). так ви добавляєте додаткові і потенційно лишні слої, через які зростає складність управління цим усим
We're looking for an experienced Blockchain Full-Stack Developer to help build a next-generation Endless Runner Web3 game with on-chain gameplay mechanics, NFTs, and tokenized rewards. This is an opportunity to work on an innovative game that combines modern web technologies with blockchain infrastructure. You'll collaborate with game developers, backend engineers, and designers to build scalable smart contracts, Web3 integrations, and a seamless player experience.
It is necessary to transfer the finished website design (landing page for a course, infobusiness) from Figma to Weblium in one day.
We are looking for a developer (or a team) to create an automated service for ordering home services in Warsaw. Main analog and reference: CleanWhale.pl — we take the convenient step-by-step logic of the calculator, the grid of additional services, the interface for selecting frequency, and the overall principle of placing an order from here. Task: Create a similar Mobile-First service in terms of convenience and design, but with simplified tariff logic and built-in gamification (“Housing Sharing”). Stack: We are considering options on WordPress + Elementor / WooCommerce, No-Code (Bubble / FlutterFlow), or your ready-made custom solutions.
Good day! We have a project on Next.js, React, Node.js, and Strapi. Currently, the main page is designed, and two secondary pages need further development. It is also necessary to design another 4–5 pages with adaptation and complex animations for different devices and connect them to the Strapi admin panel. Due to the change in the workload of the previous developer, we are looking for a new specialist to complete the project. We are looking for a responsible developer with practical experience working with this stack. In your response, please include examples of similar projects. The budget will, of course, be discussed.
It is necessary to automate the update of the existing Custom Audience in Meta Ads, which is used to exclude buyers from advertising campaigns. Required logic: once a day, retrieve the last 400 orders from the CRM (for example); take the customer's phone number and, if available, email; remove duplicates and format the data to the format accepted by Meta; completely replace the customer list in the existing audience, keeping its current ID; ensure protection: do not clear the audience if the CRM returns an empty or incorrect list; set up automation through Make and/or Meta Marketing API; check that the audience continues to be used correctly in the exclusions of advertising campaigns. The audience is already created, but is currently updated manually. The executor is required to: Propose the optimal implementation method. Specify what accesses and permissions will be needed. Estimate the cost and time for completion. Indicate experience working with Meta API and Make. After setup, provide a brief description of the logic of operation and the accesses used. Additionally, please clarify: is a complete daily replacement of the audience possible through the API and what limitations or risks may exist from Meta's side.