We are preparing to migrate from the old platform to the new experience. We've made recent changes to one of our existing custom pages (https://data.townofcary.org/page/storydirectory/) by updating HTML/CSS in the main content area between the navigation menu bar and the footer. Do we need to do anything now to ensure the current content on this page will display once we migrate to the new experience? (We have about 10 custom pages in the same situation.)
Solved
Custom pages when migrating to new experience
Best answer by Benwa
Hi @kguttman,
Good news on the migration front: your custom pages will automatically become assets in the new experience — no action needed on your end, and any changes you make now can be published as usual without affecting the migration.
On the broader question of managing style changes across your ~10 pages, here's the recommended approach:
1. Move shared styles to the platform-level CSS. Huwise has a global stylesheet at the platform level, separate from each page's individual CSS. Anything that should be consistent across pages (fonts, colors, spacing, component styles…) belongs there. Update it once, it applies everywhere.
2. Define a clean page template. Once your global styles are in place, build one reference page with the right structure and make sure it uses those shared styles correctly.
3. Replicate the template, then add content. Use that template as the base for each page and drop in the specific content — no copy-pasting styles page by page.
That said, since you're already preparing a migration, it might be a good moment to take stock of two things:
- Some of your HTML pages could be rebuilt as Studio pages (no-code). If the content isn't heavily custom, the Studio editor will be much easier to maintain going forward — no HTML/CSS required.
- The new no-code style configuration lets you manage your portal's look and feel visually, without touching CSS directly. Moving some of your current CSS rules there could simplify how you handle style changes across the board.
Neither is required, but a migration is often the right moment to reduce the amount of custom code you're maintaining long-term.
Benwa
+3Hi @kguttman,
Good news on the migration front: your custom pages will automatically become assets in the new experience — no action needed on your end, and any changes you make now can be published as usual without affecting the migration.
On the broader question of managing style changes across your ~10 pages, here's the recommended approach:
1. Move shared styles to the platform-level CSS. Huwise has a global stylesheet at the platform level, separate from each page's individual CSS. Anything that should be consistent across pages (fonts, colors, spacing, component styles…) belongs there. Update it once, it applies everywhere.
2. Define a clean page template. Once your global styles are in place, build one reference page with the right structure and make sure it uses those shared styles correctly.
3. Replicate the template, then add content. Use that template as the base for each page and drop in the specific content — no copy-pasting styles page by page.
That said, since you're already preparing a migration, it might be a good moment to take stock of two things:
- Some of your HTML pages could be rebuilt as Studio pages (no-code). If the content isn't heavily custom, the Studio editor will be much easier to maintain going forward — no HTML/CSS required.
- The new no-code style configuration lets you manage your portal's look and feel visually, without touching CSS directly. Moving some of your current CSS rules there could simplify how you handle style changes across the board.
Neither is required, but a migration is often the right moment to reduce the amount of custom code you're maintaining long-term.
Benwa
Login to the community
No account yet? Create an account
Already have a Huwise account ?
Log in with Huwiseor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.