Website development on Framer

A one-page website (Landing Page) needs to be created on WordPress + Elementor Pro for selling electric unicycles. Requirements: Layout on Elementor Pro. Responsiveness (PC, tablet, mobile). Modern design (preferably not a template). Filling the page with product information from the official website (photos, videos, specifications, descriptions, etc.), which will only be provided to the project executor. Application forms (name + phone). Main blocks: main screen, advantages, specifications, gallery, equipment, FAQ, contacts. Call-to-action buttons throughout the page. Basic SEO optimization. Loading speed optimization. After completion, the site must be fully ready for transfer to the client's hosting. All work on your hosting with daily reporting. Please indicate immediately: estimated cost; completion time; examples of similar landing pages on Elementor (if available). whether you use electric transport in your life (which one).

This is an unfinished plugin for After Effects: https://drive.google.com/drive/u/0/folders/1Nq9a672OK6ep9Com1lqelUhZxbx3_3f1 If I understand correctly, this is a CEP plugin (Adobe Extension) for After Effects. It is an HTML/JavaScript panel through Adobe CSXS that interacts with After Effects via ExtendScript. The goal was to automate the video creation process in the "maze challenge" style, reference on YouTube GOALRUSH-f8x or similar. Manually edited video: https://drive.google.com/file/d/1Ylzvax6w2JGDwaBqeCdbD49jh5wB5buY/view?usp=sharing File of one of the projects: https://drive.google.com/file/d/15vKd1L9VfHtDqK2wtLQdYEmDpH1d8Jvy/view?usp=sharing Besides the "bugginess" of the system due to vibe coding (so vibe coders are out), such details did not suit the device (real edits): https://docs.google.com/spreadsheets/d/18Svc6GoQ34PgLe1HY7gNX5tPLH0Cpv9E4mfjCRBCMFU/edit?gid=0#gid=0 It is necessary to create a system that will generate projects in After Effects with all the necessary video components listed in Base.pdf, more detailed logic in the form of photos, text documents, and mind maps for understanding all possible variations on the disk: https://drive.google.com/drive/folders/1Uf4Pnw3SKmwpmhL7sjPZFnfAbN0arUjr?usp=sharing Even more detailed (with a more in-depth descriptive part and links to time codes in references) the technical specifications will be finalized in the project workspace The final result is a system that creates videos: from 40 seconds to 1 minute, completely unique content for each creation, without AI metadata in the video file, it should have a clear plot (traps, dead ends, various emotions of celebrity characters as a result of some plot twists in the video), sound design according to the plot (screams and other emotions, explosions, etc.), stylistically not differing from the reference video from the channel.

Refinement of the working landing page - configurator created in AI is required. Almost all visualizations and options have been created. We will provide the archive. Everything needs to work well, be displayed properly, and be adaptive for mobile and PC. A screenshot of the landing page is attached.

TECHNICAL ASSIGNMENT FOR THE DEVELOPMENT OF A LANDING PAGE BASED ON WORDPRESSAbout the project: A selling landing page is required for an author's online intensive on the active corporate website of a law firm. Website platform: WordPress. Expected page URL: salyk.net/online_intensivePayment: The project will be paid with funds reserved on the website deposit. No "first I will do the work, then I approve the project and you make the payment".1. Design and structure:There is a ready prototype in the form of clean HTML/CSS code (includes texts, structure, color scheme, responsiveness, and vertical video testimonials 9:16). The code is attached to this technical assignment in the file "code". You can insert it here https://htmledit.squarefree.com/ and view the preliminary design.Design task: Take this code as a basis, but do not just copy it. Improvements in UX/UI are encouraged, including the addition of neat micro-animations, shadows, modern effects (features) that will make the page more attractive and selling while maintaining a strict corporate style.Photos: Currently, only 3 AI-generated photos are attached. After project approval, I will send my personal photos for integration on the landing page.2. Integration with CMS (Editability):Critically important: The landing page should not hang on the site as "bare" HTML code. The page must be assembled using a visual builder (Elementor) or implemented through flexible fields (ACF).The client must have the ability to easily change any texts, links, rates, photos, and video testimonials directly from the WordPress admin panel without interfering with the code.3. Technical requirements and responsiveness:Full responsiveness of cross-browser layout: Desktop, Tablet, Mobile. The page must display correctly on all types of devices (including the proportions of 3 vertical video testimonials).High performance: Basic optimization of loading speed is mandatory (Google PageSpeed). Images must be compressed and converted to WebP format, scripts and styles minified.4. Feedback form (Lead generation):The landing page has an application form (Name, Phone). It needs to be fully functional.All applications must be instantly sent to the corporate email: [email protected] is necessary to configure sending via SMTP server or use a reliable plugin (WPForms / Contact Form 7) to ensure that applications do not end up in the "Spam" folder.5. Multilingualism:The current site implies the presence of three languages (RUS, KAZ, ENG).As part of the project, the contractor must set up multilingualism for the new landing page (using plugins Polylang, WPML, or similar).During the task execution, the client will provide ready translations of the text into Kazakh and English. The contractor must create and format these additional language versions of the page.6. Integration with the main site:Set up a transition to the landing page from the main site.In the main menu (in the header) of the active site salyk.net, it is necessary to add a new button or menu item (for example, "Online Intensive") that will lead to the address /online_intensive.Additionally: create a function on the entire site to switch between languages rus/eng/kaz in the style of the site.

There is an active production site with a product catalog, model cards, and informational pages. Frontend stack: — Next.js; — React; — TypeScript; — existing component system; — staging and production environments. There is an approved visual direction and design for the new homepage. It is necessary to implement it into the existing project, adapt it for desktop/tablet/mobile, and bring all main types of pages on the site to a unified updated style. A complete redesign of the product and changes to business logic are not required. MANDATORY SCOPE 1. New homepage — implement the homepage according to the provided design; — maintain existing functionality, links, and routing; — correctly connect approved sections and CTAs; — use existing data and APIs; — ensure correct display of dynamic content. Main types of sections: — header/navigation; — hero; — informational blocks; — model/offering cards; — analytical or market insight blocks; — CTA sections; — footer. The exact composition of sections will be provided to the selected performer along with the layout. 2. Responsive It is necessary to implement: — desktop; — tablet; — mobile; — intermediate resolutions; — correct behavior of grids, cards, menus, buttons, and typography; — absence of horizontal scrolling and visual conflicts. 3. Typography and general styles — implement new approved fonts; — unify sizes, weights, line-height, and spacing; — update styles for buttons, cards, fields, badges, and headings; — use common design tokens or CSS variables where possible; — avoid duplicating styles separately for each page unnecessarily. 4. Unification of existing pages Check and bring to the new style the main types of pages: — catalog; — model card / PDP; — informational pages; — header; — footer; — forms; — modal windows; — existing CTAs; — loading / empty / error states, if they are already present in the project. This is about the visual unification of existing components, not a complete individual redesign of each page. 5. Catalog Check: — card grid; — images; — name, reference, and price; — filters and sorting; — buttons and links; — desktop/mobile display; — loading and empty states; — absence of visual shifts during loading. 6. PDP Check: — gallery; — main information block; — price and CTA; — analytical sections; — tables and metrics; — About Watch; — desktop/mobile layout; — long names, references, and missing data. It is necessary to maintain current functionality and existing API contracts. 7. Header and Footer — unified style across all pages; — responsive navigation; — mobile menu; — correct active/hover/focus states; — absence of discrepancies between the homepage, catalog, and PDP. 8. Interface states For dynamic blocks, check: — loading; — empty data; — API error; — insufficient data; — missing image; — missing price; — long text; — mobile display. There is no need to develop new complex business logic. It is necessary to correctly visualize already existing states. 9. Quality and performance — do not worsen SEO and current indexing; — maintain correct metadata and semantic HTML; — avoid critical layout shifts; — optimize images and fonts; — consider reduced motion for animations; — check basic accessibility: focus states, contrast, keyboard navigation; — do not include heavy libraries without justified necessity. 10. Staging and QA — deploy changes on staging; — check main types of pages; — check desktop, tablet, and mobile; — fix visual and responsive bugs; — after acceptance, perform production deployment; — ensure bug fixes for the implemented scope for at least 7 calendar days after deployment. RESULT OF WORK — Pull Request with frontend code; — implemented new homepage; — responsive desktop/tablet/mobile; — unified fonts, cards, and basic UI components; — visually agreed catalog, PDP, and informational pages; — staging deployment; — fixing identified visual errors; — production deployment; — brief description of modified components; — 7-day bug-fix period after acceptance. ACCEPTANCE CRITERIA 1. The homepage matches the provided design. 2. All sections work correctly on desktop, tablet, and mobile. 3. Header and footer are uniform across all pages. 4. Catalog and PDP visually correspond to the new system. 5. Current functionality of the site is not disrupted. 6. API contracts and backend logic are not changed without agreement. 7. No horizontal scrolling and critical layout shifts. 8. Fonts and images load correctly. 9. Loading, empty, and error states are displayed without breaking the layout. 10. Changes are checked on staging and deployed to production. 11. Visual errors identified during acceptance are fixed within the agreed scope. WHAT IS NOT REQUIRED — backend development; — changes to business logic; — creation of a new catalog or CMS; — development of a new API; — complete redesign of each informational page; — new user features not present in the layouts; — development of a complex design system from scratch; — creation of a new project instead of improving the existing one; — changes to the SEO structure without separate agreement. REQUIREMENTS FOR THE PERFORMER — confident in Next.js / React / TypeScript; — experience working with existing production projects; — quality responsive layout; — experience implementing designs from Figma; — component approach; — confident working with CSS / CSS Modules / Tailwind or the existing project system; — understanding of Core Web Vitals; — Git / Pull Request workflow; — ability to work through staging. IN RESPONSE, IT IS MANDATORY TO INDICATE 1. Fixed price for the full mandatory scope. 2. Completion time in working days. 3. Estimate in hours. 4. When you are ready to start. 5. Links to 2–3 relevant projects on Next.js/React. 6. Experience working with catalogs, product cards, or analytical interfaces. 7. What will be needed for an accurate estimate before starting work. 8. Does the price include: — staging; — responsive QA; — production deployment; — bug fixes; — 7-day bug-fix period. Template responses without reviewing the requirements and without a specific estimate will not be considered. Access to production is not provided at the first stage. Work begins after a limited code review and is deployed through staging.