Editing the newsletter itself
In this application, the newsletter is the editing surface. Copy can be revised where it appears in the mailing, and custom blocks provide the structure for each campaign. Neos serves as an email editor rather than a website backend.
Each block connects that editing experience to the HTML output. Its fields define the information an editor can change; its rendering code determines how that content appears in an email. Updating the copy does not require working on the mailing’s HTML.
Content blocks that render email HTML
Our custom components produce email HTML directly. Each block has its own email-specific output; there is no finished web page to convert into a newsletter afterwards.
The templates use table-based layouts, inline styles and targeted adjustments for classic Outlook to accommodate differences between email clients. Those details stay separate from the editing interface: changing a sentence changes the content, not the template structure.
The editing fields and their HTML output are designed together. The Neos preview lets editors see the newsletter in context; checking the generated email in the intended clients is a separate part of the process.
Create in Neos, send through Acoustic
The architecture separates editing from delivery. Neos provides the newsletter workspace; Acoustic handles sending. Our integration prepares the content created in Neos for use in Acoustic mailings.
That handover is also built into the content blocks. Acoustic-specific placeholders pass through the HTML rendering intact instead of being treated as ordinary copy.
The custom Neos application adds an editing environment tailored to win2day’s newsletters. It complements Acoustic rather than replacing the sending platform.
New jackpot data triggers a new header image
New jackpot values arrive through an API and trigger image generation. ImageMagick runs on the server to produce the corresponding headers with the updated amount. There is no need for an editor to open a graphics application and recreate each variation.
The server also produces animated GIFs with a count-up sequence. In the newsletter, the animation is an image file, with no JavaScript required in the email client.
The first frame is deliberately the finished header, complete with the full jackpot amount. A client that displays only that frame still shows the key information, not an intermediate value from the animation. The count-up adds movement without making the amount depend on animation support.
Incoming API data triggers a new graphic, not someone opening the email. The application handles the data and image processing; the newsletter only needs to display the image.
Turning supplied designs into an editorial application
Working from client-supplied designs, we developed the HTML-email templates and the application around them: custom editing blocks, the Acoustic integration and automatic jackpot-header generation.
Neos and its underlying PHP framework, Flow, provide the foundation. We built the newsletter editor, content blocks and integrations specifically for this project; they are not standard Neos features.
The application shows what Neos can do beyond conventional websites. Editors work directly on a newsletter, while the software brings together the design rules, email HTML, external data and sending platform.
Neos is the editing environment, custom components produce the email HTML, and Acoustic handles sending. New jackpot data triggers image generation with ImageMagick. The first frame of each animated header contains the full amount, so it also works as a static image.