Mi Primer PremioPublic website for a monthly subscription raffle platform

Development of the public website at Azirgo SAS: home page, legal pages, structured data, analytics and deployment.

The raffle platform runs in its own app, with its own API and sign-in. What it lacked was the front door: a site that explains in seconds how the four monthly raffles work, shows the plans at the same price the app charges and takes people straight to subscribing with the plan already chosen, without prices and copy drifting out of sync every time the business changes a plan.

• A single-page home with a banner slider, community, this month's raffles, plans, how it works, winners, FAQ and a closing call to join the WhatsApp group.
• A plans section that reads the platform's four plans from its API at build time, with the price, the raffles included and the monthly equivalent calculated in whole cents.
• A “Choose plan” button that opens the app's sign-in with that plan already selected.
• Four standalone, indexable pages: terms and conditions, raffle rules (with the month's prize table), privacy policy and contact.
• Structured data in a single @graph: Organization, WebSite, a Product with its Offer for each plan and an online Event for each raffle.
• Animated WebGL backgrounds - five variants: smoke, aurora, fog, beams and vapour - and a shower of coins over the raffles section.
• GA4 and Microsoft Clarity analytics loaded once the page has finished loading, and a sitemap.xml generated from the list of real routes.
• A Docker image that builds the site and serves it with nginx, with long caching for the versioned files.

A static-output Astro site, with the home page as a React island. Everything that repeats lives in shared data modules, so the header, the footer, the legal pages and the JSON-LD all read from the same source.

The home page is built on large illustrations and animated backgrounds, so every heavy piece has its own rule to keep it from slowing down the first screen.

• Astro with static output and the home page as a React island: the HTML comes out of the build complete - copy, prices and JSON-LD - and React only takes over afterwards for the slider, the FAQ and the animated backgrounds.
• Plans are requested from the API during the build rather than in the browser, so prices arrive already written into the HTML. If the API fails, the site falls back to the backup plans instead of breaking the deploy.
• Each plan is matched to its design by subscription type, not by name or slug: the API has plans whose slug says “annual” and that bill monthly.
• In the JSON-LD each Offer carries the number of months it covers, so $15.99 every six months is not indexed as a monthly price, and the declared price is exactly the one on the card.
• Whatever the business has not confirmed yet is not invented: empty fields are left out of the schema and, on the pages, show a visible pending marker instead of passing as real data.
• Published images carry the version in their filename, because nginx serves them with a one-month cache: new artwork gets a new URL instead of waiting for the cache to expire.

• Keeping five WebGL backgrounds smooth on modest phones: they render at half resolution (a third on devices with few cores or little memory), at 30 or 20 frames per second, only while the section is on screen and never when reduced motion is on.
• Publishing illustrations with the lettering painted into the image without WebP eating the letters: a 100 KB ceiling per file, with separate allowances for the lettered banners and the vertical artwork.
• Placing a transparent header over the slider without the logo covering the headline on 320 px screens: the extra space is added by the script that generates the WebP files, stretching the edge of the artwork, without touching the originals.

The site is live: home page, plans with the prices from the API, raffle rules and legal pages, all static and served by nginx, with the plan and raffle structured data crawlable and GA4 and Clarity analytics running.