Transfer of the website to another control panel

A small project needs to be implemented for selling digital and physical products. What needs to be done: Develop a simple modern landing page for selling 3 products: PDF version; physical kit; paid Telegram subscription. Connect payment through WayForPay. Integrate orders with KeyCRM: transfer of customer data; creation of orders in KeyCRM; possibility of further automation. Develop a Telegram bot for managing subscriptions: automatic access issuance after payment; subscription activity check; subscription renewal; automatic access removal after payment completion; user administration through a simple panel or bot commands. It would be a plus: experience with WayForPay; experience integrating with KeyCRM; experience creating Telegram bots and paid subscriptions. Please specify immediately: exact cost; implementation timeline; examples of similar projects.

1. General Information about the Project Client: family amusement park in Germany (full name and domain revealed to the contractor after the project starts) Project Type: complete redesign and rebuild of the website from scratch Current Website: WordPress/Elementor, outdated, requires complete replacement Target Audience: families with children aged 2 to 12 years, region of Germany with several large cities nearby (15 to 20 minutes by car) Website Language: primary German (DE), additionally English (EN), separate language version CMS: at the discretion of the developer, WordPress with a custom theme, Webflow, or headless CMS. Do not use Elementor. Domain: existing, transferred without replacement Deadline: to be agreed upon with the client 2. Goals and Key KPIs The new website must fulfill three strategic functions: Convey the atmosphere of the park as an immersive adventure, not a list of services, but an immersion into a themed world. Maximize conversion: the website visitor should make a booking in less than 3 clicks from any page. Ensure flawless mobile UX, with over 60% of traffic expected from mobile devices. KPI #1: time to first click "Book" no more than 10 seconds from the moment the homepage loads KPI #2: Page Speed Score (Google PageSpeed Insights) at least 85 on mobile, at least 90 on desktop KPI #3: bounce rate less than 45% KPI #4: correct display in all modern browsers (Chrome, Firefox, Safari, Edge) and on iOS/Android 3. Scope of Work 3.1 Pages and Sections Minimum set of pages: Homepage: Hero section, announcement of live shows on weekends, top 5 attractions, Google reviews, CTA block Attraction catalog with age filter (0 to 3 / 3 to 6 / 6 to 12 years), cards with photos and videos Birthday packages, description plus configurator Current promotions and seasonal events, each with its own visual card Prices, table plus online booking widget (integration with external booking system) Restaurant, menu, and atmosphere Photo gallery plus embedded Instagram feed About the park, rules, FAQ (without duplicating rules) Contacts, Google Maps, contact form, working hours, clickable phone and email Mirror of all pages in English 3.2 What Needs to Be Removed from the Current Website All texts about COVID-19 restrictions (2021 to 2022), including the footer FAQ with questions about website development costs (third-party content) Outdated copyright year, replace with the current one Non-working Elementor popup buttons Outdated notifications about reopening after restrictions Duplication of park rules in the FAQ section 4. Functional Requirements P1 = critical for launch, P2 = desirable in v1.0, P3 = possible enhancements later 4.1 Hero Section (Homepage) P1, Fullscreen Video Hero: autoplay video without sound (muted, loop), 100vw by 100vh. Sound enabled on click. Overlay text slogan and CTA button. P1, text layer over video: H1 title, subtitle plus "Book" and "Learn More" buttons. Font readable on any background. P1, Sticky Navigation: navigation bar fixed at the top when scrolling, background changes from transparent to dark when scrolling. P1, Sticky CTA Button: "Book" button always visible, in the header on desktop, on mobile a fixed bar at the bottom of the screen. P2, Scroll animations: elements appear with CSS animation (fade in plus slide up) when scrolling. Use Intersection Observer or AOS.js library. No heavy 3D libraries. 4.2 Attractions P1, attraction cards: photo/video, name, brief description, age restriction icon, "More Details" button P1, age filter: client-side filter without page reload, implementation with CSS classes plus vanilla JS or Vue/React component P1, detailed attraction page: own URL, large photo/video, full description, height/age restrictions, booking button P2, short form video: 15 to 30 seconds clip for each attraction, autoplay on hover on desktop or tap on mobile 4.3 Booking System P1, integration with external booking system: widget embedded inline (iframe or JS embed) on prices and birthday pages, without opening in a new tab P1, multi-step booking flow: step-by-step wizard, type of visit, date/time, number of guests, confirmation, mandatory progress bar P1, explanation of time slots: info block next to time selection P2, live availability of slots: API request to the booking system, displaying occupied/free slots in real-time 4.4 Birthday Configurator P1, multi-step configurator: age of the birthday person, number of children, package selection, additional options, date selection, request form or direct booking P1, dynamic price calculation: updates in real-time when parameters change, without page reload P2, final summary: summary card of selection on the final step with "Request" and "Book Directly" buttons 4.5 Trust and Social Proof P1, Google Reviews widget: at least 5 reviews, average rating, stars, placed on the homepage above the booking CTA block P1, Instagram feed: embedded feed of the last 9 to 12 posts via official API or widget, link to the account P2, visitor counter: animated counter 4.6 Additional Functional Blocks P1, live status "currently open/closed": automatic marking based on working hours P1, clickable contacts: phone and email as active links, mandatory in the header and on the contact page P2, interactive park map: SVG or image map with clickable attraction zones P2, load tracker: visual indicator of expected park load P2, countdown to event: countdown widget to the nearest seasonal event P3, separate section for evening events: page or section with its own visual style and booking button 5. Non-Functional Requirements 5.1 Performance LCP no more than 2.5 seconds on mobile (3G fast) CLS less than 0.1 FID/INP less than 100 ms Google PageSpeed Score at least 85 mobile, at least 90 desktop Images: WebP format plus fallback JPEG, lazy loading, srcset Video: streaming via CDN or YouTube/Vimeo embed, do not store heavy MP4 on hosting 5.2 SEO Schema.org: LocalBusiness plus OpeningHoursSpecification plus Event Meta tags: unique title (no more than 60 characters) and description (no more than 155 characters) on each page Hreflang for language switcher Canonical URL on each page Sitemap.xml automatically generated Configured robots.txt 5.3 Accessibility WCAG 2.1, level AA as the minimum standard Alt attributes mandatory for all images Text/background contrast of at least 4.5 to 1 Full keyboard navigation ARIA attributes on all interactive elements 5.4 Security HTTPS mandatory, redirect from HTTP DSGVO/GDPR: cookie banner (Consent Management), current privacy policy CSRF protection, honeypot or reCAPTCHA v3 on all forms All dependencies up to date, without known vulnerabilities 5.5 CMS and Editability Texts, prices, working hours, photos editable via CMS without involving a developer Creation/archiving of promotions and events through the CMS interface Automatic updating of Instagram feed via API Video tutorial (10 to 15 minutes) on working with the CMS, mandatory deliverable 6. Design System 6.1 Color Palette: primary deep green, secondary medium forest green, accent red for CTA, light green for card backgrounds, beige for textural accents, dark for main text, white 6.2 Typography: expressive display font for headings (in the spirit of adventure), readable neutral sans serif for main text, minimum size 16px body, 14px caption, line height 1.5 to 1.7 6.3 Images and Media: only real photos, do not use stock photos, WebP format, minimum 1920px for hero, 800px for cards, hero video no longer than 30 to 60 seconds in loop version, all images with publication rights 6.4 Animations: hover effects smooth (scale 1.03 on cards), scroll animations fade in plus translateY, only transform and opacity for GPU acceleration 7. Expected Results Design layouts in Figma: desktop plus mobile view of all pages (desktop 1440px, mobile 375px) Responsive layout: breakpoints 375 / 768 / 1024 / 1440px, mobile first approach Ready website on staging domain for acceptance, after approval deploy to the live domain CMS setup: all editable areas configured, test-filled Video tutorial (10 to 15 minutes) on content management Basic SEO setup: meta tags, Schema, Sitemap, connection to Google Search Console Installation of Google Analytics 4 plus Google Tag Manager, event setup (click CTA, form submit, page_view) Cross-browser and cross-device testing, PageSpeed Insights report before delivery Transfer of source code (Git repository) to the client after final payment 8. Acceptance Criteria All P1 requirements implemented and tested PageSpeed Score at least 85 mobile, confirmed by screenshot Correct display on iPhone (Safari), Android (Chrome), iPad, MacBook, Windows (Chrome, Edge, Firefox) Booking form successfully submits request and sends confirmation Google Reviews load correctly Instagram feed updates automatically All links work, no 404 errors Cookie banner complies with DSGVO, GDPR Content in CMS is editable without involving a developer

It is necessary to develop a modern online store for electric, gasoline, and battery tools with a separate B2B platform for partners, dealers, and dropshippers. At this stage, I would like to receive a preliminary estimate of the cost, development timelines, and technology recommendations. (because I have a website on the Horoshop platform)Main Site The following should be provided: a product catalog with categories, brands, filters, and search; product pages with specifications, photos, descriptions, prices, and availability; cart and order checkout; customer personal account; adaptive version for phone, tablet, and computer; SEO settings; the ability to independently add and edit products, categories, pages, and banners; integrations with payment systems, delivery services, CRM, or accounting systems; import and automatic updating of products, prices, and stock.B2B Platform After authorization, the partner should have access to a separate account where they can: see individual or wholesale prices; view current product stock; create and track orders; view order history; see order statuses; view their balance, debts, payments, and settlements; upload invoices, waybills, and other documents; submit requests for returns, warranties, or service; receive notifications about new products, promotions, and price changes. It is preferable to provide different types of partners with varying prices, discounts, credit limits, and working conditions.Administrative Part The administrator should be able to: manage products, prices, and stock; create partners and assign them individual conditions; set personal discounts and limits; view all orders, payments, and debts; generate documents; view sales statistics; manage service, return, and warranty requests; send messages to individual partners or all users of the B2B platform; distribute access rights among employees.Important Requirements The system must be fast, secure, user-friendly, and suitable for further expansion. It is important that most information can be changed through the admin panel without the intervention of a programmer. In your response, please indicate: the estimated cost of development; approximate timelines; recommended technology or CMS; what is included in the cost; which integrations can be implemented; whether you provide further technical support; examples of similar online stores or B2B systems that you have developed. I am considering both a complete development from scratch and implementation on a ready-made CMS with further refinement for the necessary functionality.

Technical task for the development of the official website Public organization “Federation of Sitting Volleyball of Ukraine” 1. General information It is necessary to develop a modern, fast, secure, and adaptive official website for the Federation of Sitting Volleyball of Ukraine. The site must work correctly on: computers; tablets; smartphones (Android and iPhone). Languages of the site: Ukrainian (main) English 2. Design Style: modern; sporty; official; minimalistic. Main colors: blue; yellow; white. It is necessary to use: the Federation's logo; the state symbols of Ukraine; photos of athletes; photos of veterans; photos of the national team. 3. Main page The main page should include: large banner; the Federation's logo; news; latest events; competition calendar; button “Become a member of the Federation”; button “Support the Federation”; button “Contact us”. 4. Sections of the site About the Federation history; mission; goals; areas of activity; Statute (PDF); official documents. Leadership Separate page: President Vice-President Board Supervisory Board Audit Commission For each person: photo; position; short biography; contacts. News Ability to independently add: news; photos; documents; videos. Calendar Must include: championships; Ukrainian Cup; international tournaments; training camps; seminars. Competitions Separate section: calendar; results; tournament tables; photos; videos. National teams of Ukraine Section: men's; women's; youth; veterans. Regional centers Interactive map of Ukraine. For each region: contacts; leader; address; phone. Gallery Separate albums: photos; videos; tournaments; training; veterans. Documents Ability to upload PDF: Statute; orders; protocols; regulations; decisions; applications; forms. Partners Logos: Ministry of Youth and Sports of Ukraine; National Committee of Sports for the Disabled of Ukraine; international federations; sponsors. Contacts Must include: address; phone; email; Google Maps; feedback form. 5. Personal account After registration, the user should be able to: change personal data; pay membership fees (in the future); submit applications for participation in competitions; receive documents; view application history. 6. Administrative panel The administrator should be able to: add news; edit pages; upload documents; create photo galleries; manage users; create event calendars; publish tournament results. 7. Integrations It is necessary to connect: Facebook Instagram YouTube Telegram TikTok Also: Google Maps Google Analytics Google Search Console 8. SEO Full SEO optimization: correct URLs; META Title; META Description; Open Graph; Sitemap; Robots.txt. 9. Security Must include: SSL certificate; backup; spam protection; administrative panel protection; two-factor authentication (if possible). 10. Speed Google PageSpeed rating: Desktop — at least 95 points. Mobile — at least 90 points. 11. CMS The site should be developed on a modern CMS (WordPress or another), so that the Federation's employees can independently: edit text; add news; upload documents; add photos; create pages without the help of a programmer. 12. Domain and hosting It is necessary to: connect the domain; set up hosting; corporate email automatic backup. 13. Additionally Provide for the possibility of further expansion of the site: online registration of athletes; online payment of membership fees; athlete database; coach database; referee database; online broadcasts; electronic document management; personal account of a Federation member; mobile application (in the future). Expected result The developer must create a modern official website that meets European standards, has high speed, adaptive design, a convenient management system, and is ready for the further development of the Federation of Sitting Volleyball of Ukraine at the national and international levels.

Need to make several additions and changes to a landing page in Framer. -- Change 1 word in header -- Change heading and description of 1 selling block -- Turn off two buttons and make them light grey (to reflect that they are not clickable) -- Modify an existing form, add mandatory multiple choice before submitting a form and name field