Illustrated Agritech App Landing

Provide brand, audience and product introduction, actual solutions/stories, required pages and owned illustrations or permission to generate replacements. Add confirmed prices, hardware specs, users/customers, team, addresses and dates. Record missing content as placeholders for confirmation; do not invent integrations, performance, certifications, regulatory/privacy/security claims or customer outcomes. Product-specific sample numbers should remain identifiable as examples until replaced.

Use standalone HTML when no project/framework is requested. In an existing or requested project, inspect conventions, preserve unrelated files and port the same design into components, typed collections and actual routes. The package suggests Next.js App Router with TypeScript when a framework is requested without a name. React generic controls have a ReUI mapping; non-React support needs an explicit compatible plan, while landscape masks, phone, contour bands, charts and maps stay bespoke.

Keep the measured hero anatomy: a 1268px maximum sky shell with square top/rounded bottom, small label, 67px desktop headline and one white pill action above the landscape. Phone headline is about 43px and may use three lines; the small 226×400 phone stays below the button. Landscape is a bottom band with a short twelve-percent top fade, not a duotone background. Preserve clear sky for copy and a calm landscape center for the phone; avoid extra CTAs, floating data cards, statistics or glow.

Carry Bricolage Grotesque display, Figtree body/UI and Geist Mono data across the site. Blue is the action color; water/map/livestock/planning/weather/soil tints distinguish topics without recoloring buttons. Preserve the 1240px content width, 20–40px gutters, 84–136px section rhythm, inset rounded blue bands, navy text and tinted ground. Cards/widgets/shells have different radius roles; inputs are 14px and controls pill-shaped. Adapt mobile splits, chip scrolling, team grid and table overflow intentionally.

Populate solutions, articles, team, hardware, plans, FAQ and product-screen data together. A new solution needs an image key, detail section and appropriate widget binding; without a widget entry its tool box is omitted. Home shows up to six solution bento slots; three entries keep the first three, four/five require bottom-row span adjustments and seven or more keep extras on the index. Keep at least three articles for the home journal, match plan/team/timeline/office columns to real counts and update number-bearing headings.

Adapt the domain rather than merely replacing farm names. Garden/plant-care apps can use beds/rooms, reminders and guides; crew tools can use sites, jobs and seat/add-on estimates. With no hardware remove both platform specifications and pricing estimator. Without an app download remove its route/links, while retained phone components show the actual product screens. Product UI must remain meaningful to the new business instead of displaying unrelated moisture values under new labels.

Keep dashboard controls and their evidence boundary clear. Field selection updates local moisture, rain totals, threshold band and plotted series; the curve is generated from example drying/rain/irrigation rules and shifted to a chosen endpoint, with labels anchored to July 2026. Task toggles change interface state and a toast, not a synchronized crew record. Replace field names, polygons, crop/area/water labels and readings coherently; a clickable map is not a connected geographic or sensor platform.

Preserve each solution tool’s distinct role. Irrigation chooses among four zones with prepared chart/recommendation text. Mapping slides between an illustration and colored vigor overlays for two sample dates; it does not derive a satellite measurement. Livestock toggles groups between due/checked and allows undo. Planning emphasizes fixed April–November Gantt bars by job type. Weather filters seven fixed daily samples with job rules, and soil compares fixed yearly field records. These demonstrations should not be presented as validated operational or agronomic guidance.

Review units and implied outcomes when adapting widgets. Weather’s °F/°C switch converts temperatures while wind remains mph; job thresholds and labels need full localization. Soil text says original lab reports are attached, but the inspected table has no attachment control. Mapping and task messages mention a sent scouting task or next-shift visibility without a service behind them. Keep useful sample tools while qualifying/removing unsupported delivery, report or synchronization claims.

Use pricing to explain actual costs. The sample card toggle displays annual total or monthly price; the hardware estimate adds one-time quantities to annual plan cost, or to twelve monthly payments. Hardware quantities run from zero to forty and a missing gateway shows a warning rather than enforcing compatibility. Its estimate is a first-year comparison, not a checkout, tax calculation, financing quote or validated sensor design. Change hardcoded plan/gateway references and only retain billing toggle when two confirmed rates exist.

Keep the rule builder as a configuration demonstration. Trigger choices refill place/condition options; action and recipient update a sentence and notification preview. Presets load the controls, save adds a local rule after a short delay, reset restores a preset and switches pause/enable entries. No telemetry is evaluated and no job/notification is scheduled. The sample toast promising it runs on the next reading needs honest demo wording until an engine is integrated.

Plan all twenty-four illustration slots in one flat editorial style: rounded shapes, gentle shading, clear daylight, sky/leaf/wheat/barn colors and no lettering or baked UI. Keep a distinct subject for each solution/article/process role; matching card/detail reuse is appropriate for that entity. Illustrations of people appearing in portraits and story scenes should retain consistent identity. The hero world, product stills and portrait backdrops need appropriate empty space and crops, reviewed at desktop and 390px.

Owned illustrations or an available agent image tool can supply replacements; generation may charge. Neutral farm scenery, signup landscape, scarecrow and mailbox can remain when the business is rural/food/outdoor. Generated customer/team/story people are stand-ins, not evidence of real staff or customers. Replace sample solution covers, journal topics, hardware kit and tractor context when the product differs; a non-rural brand needs its own coherent world in the same composition. Keep product screens code-built.

Give articles full sections, byline/date, cover, table of contents, pull quote, takeaways and related reading. About needs story, principles, timeline, people and locations; contact/FAQ/newsletter need useful alternatives and next steps. Replace customer trust figures, privacy/data-ownership statements, office addresses, reply windows and app requirements with actual facts. Legal text and standards chips require review rather than serving as proof of compliance.

Test form states without describing them as delivered services. Generic validation checks required values/email/minimum lengths; SMS uses a sample ten-digit US rule, and signup validates two steps plus terms. Local success follows a short timer. Inspected copy promises setup email, download SMS, newsletter editions or a team reply despite no sending/account backend. Change those promises to explicit demo outcomes until integrations exist; successful local validation does not create an account, send data or charge.

Rebrand metadata/page titles, shell marks, screen greetings/farm, task/rule assignees, domain/address bar, notifications, widget copy, customer stories, FAQ help identity, articles, social/copy-link URL, contacts and legal content. Rename page sections, links, nav mapping and dynamic solution/article paths together. Changing a content array alone leaves static examples and wired IDs behind.

Prepare offline output using Node.js 18+ with initial network access for the three font files. Embed local assets and keep the 5MB target/8MB cap; the image map supports reuse and repeated static tags can be deduplicated. Inspect the inliner exit result because output may already exist when it reports missing assets/fonts. The static validator checks paths in file/template modes and text/route/signature patterns, but permits pages with no static h1 and does not establish widget correctness, image rights, full palette fidelity or real services. A framework port needs build/type checks.

Inspect every route at 1440/1024/768/390px, with wider/narrower overflow checks and two visual review passes. Exercise mega menu/drawer focus/Escape, solution/article filters/search/sort/empty results, dashboard map/range/tasks, all six widgets, rule presets/save/toggles/reset, prices/hardware, phone tabs/carousel, signup back/next/terms and all form invalid/success states. Verify article/legal anchors, actual clipboard result, route/back navigation, reduced motion and offline/iframe loading. Report actual acceptance, placeholders/stand-in artwork and outstanding data/service connections.