You told us DigiStream might be the last company still hosting its own website. In 4 weeks, it won't be. Same look, new platform, and your marketing team edits the site without waiting on IT.
You told us you might be the last company still self-hosting its website. The inventory you sent backs that up: DNN 9.13.10 on an IIS server in your Azure tenant, and that's as far as DNN can upgrade in your setup.
The site also props up two other things. Both video player sites pull their styles and scripts from DNN, so a CSS change on the main site can break them.
You were clear about the order: replatform first, redesign later. This proposal moves the site as it looks today, cuts the DNN cord, and hands your marketing team a site they can change in an afternoon.
Your current look carries over, so our hours go into moving the site instead of redrawing it. Every page gets rebuilt or redirected, the video players keep working, and DNN turns off at launch. The redesign your marketing team wants starts from a clean platform in 2027.
We stand up Paigebuilder, your content model, and separate staging and production on Google Cloud. You own the repo and hosting from day one, or run it in Azure.
No redesign. We rebuild today's type, color, and layout as reusable components, with a phone layout that keeps the menu and the Refer button on screen.
Home, Solutions, and all five service pages rebuilt on shared templates. Clip of the Month gets player controls, and new thumbnails resize themselves on upload.
Orange Papers, Coverage, Office Directory, and License Directory become entries marketing can edit. Mission, CSR, and Careers move onto the same components.
Both player sites load styles from DNN today. We move those files to a fixed address first, so the players keep working the day DNN shuts off.
Every old URL gets a redirect, page metadata carries over, and the sitemap lists your papers. Then DNN goes offline and we walk your team through publishing.
Each risk on the current setup, and what happens to it on the new stack.
| The risk | On DNN today | On Next.js and Paigebuilder |
|---|---|---|
| Upgrade ceiling | 9.13.10 is as far as DNN goes in your setup. | Closed Next.js and Paigebuilder update on a normal release cycle. There's no server to upgrade. |
| Self-hosted server | An IIS server your team patches, watches, and pays for. | Closed Pages are built ahead of time and served as files from managed hosting. The web server role retires. |
| Players tied to DNN | A CSS change on the main site can break both video players. | Closed Shared styles and scripts live at a fixed address the player sites load directly. |
| Stolen password | Anyone with a login can change the site. | Still a risk Same on any platform. Two-factor sign-in on Paigebuilder and hosting cuts it down. |
We'd rather tell you the fourth one stays than oversell the first three.
"It is self-hosted, which perhaps we're the only ones left that self-host our website."
Live the week of November 2. From you we need DNS access, a hosting account owner, your call on any pages to retire, and 30 minutes with whoever runs the video player sites.
Open any line to see what's included.
Assumes the player sites and the video playback service stay on your servers, and existing clips, stories, and papers move over as they are today.
Switch any add-on on to see the new total. Each one is fixed price, and you can add it now or after launch.
You get Paigebuilder on Google Cloud, your current look on every page, video players that keep working, and DNN switched off. That's 4 weeks at $7,500 fixed, billed half at signature and half at launch.
We can start Monday, October 12. Tell me which add-ons you want, if any, and we'll lock the date.
Brian Hammond
VP of Sales, FYC Labs
bhammond@fyclabs.com
fyclabs.com