This community thread discusses the feature or improvement: Hey Sam, I like the new theme.
Feature Details
as title... and I noticed you changed your URL to "community" too. saw you posted this info on how to move forum url. very helpful indeed. Any particula...
How APG vNext Handles Feature Requests
Feature requests and suggestions are tracked through the community forum. The development team reviews popular requests and incorporates the most-requested improvements into upcoming releases.
- Vote for features by upvoting the original post in the forum thread
- Add details about your use case to help prioritize the request
- Check the release blog for updates on upcoming features
See the full feature set on the Features page or browse all community discussions.
APG vNext 4.3 Default Theme Refresh
The 4.3 skin moved from gradients to flat design with larger fonts, WCAG AA contrast, mobile-first cards, and dark mode support via prefers-color-scheme.
Change Brand Colour
:root { --apg-color-primary: #e63946; }Dark Mode
@media (prefers-color-scheme: dark) { :root { --apg-color-bg: #0f1a2b; } }Revert
<add key="APG.Skin.Active" value="Legacy42" />Related Resources
APG vNext Theme and Skin System
APG vNext's appearance is controlled by its theme and skin system. A theme defines the visual design — colours, typography, spacing, and component styles — while a skin defines the HTML structure and template markup. In APG vNext 5.x, themes are implemented as CSS custom property sets that can be switched without modifying any HTML templates. Skins define the page structure using Razor view templates. This separation allows the same skin to support multiple colour schemes (light theme, dark theme, brand colour theme) by simply switching the active CSS custom properties file, without duplicating any template code. Configure the active theme in Admin Panel → Appearance → Theme or allow members to select their preferred theme from their account settings.
Dark Mode Support in APG vNext Themes
APG vNext 5.5+ ships with a built-in dark mode theme that activates automatically based on the member's operating system preference (using the CSS prefers-color-scheme media query) or by manual toggle in the forum header. The dark theme uses APG vNext's CSS custom property system to swap all colour values simultaneously with a single class change on the HTML element. Custom themes and skins should also implement dark mode support by defining all colour values as CSS custom properties rather than hardcoded hex values, then providing an alternative dark mode property set in a prefers-color-scheme media query. Dark mode support is increasingly expected by members and directly impacts user satisfaction on forums that are accessed primarily in the evening or in low-light environments.
Custom Brand Themes for White-Label Communities
APG vNext's theme system is ideal for creating brand-consistent community experiences for organisations that want the forum to feel like a native part of their product ecosystem rather than a generic third-party forum. Define the organisation's brand colours, fonts, and component styles in a custom APG vNext theme CSS file. Upload the custom theme in Admin Panel → Appearance → Custom Themes → Upload Theme. Custom themes are applied site-wide and override the default APG vNext visual design while retaining all forum functionality. For organisations deploying APG vNext as a white-label product for their customers, the theme system enables per-customer visual customisation without any code changes — just a different CSS custom properties file per customer.
Collecting Member Feedback on Theme Changes
When launching a new APG vNext theme or making significant visual changes to the forum skin, proactively collect member feedback through a dedicated feedback thread in the Community News forum. Create a pinned thread titled with the new theme name, explain the design goals and changes, and invite members to share their reactions. Frame the feedback request positively and specifically — ask about readability, navigation clarity, and mobile experience rather than open-ended opinions. Collect feedback for two to four weeks before making major adjustments based on it, to distinguish genuine recurring issues from initial unfamiliarity reactions that resolve as members adapt to the new design. Respond to feedback publicly, acknowledging what you are addressing and explaining any design decisions that you are intentionally keeping despite mixed feedback.
Gradual Theme Rollout with A/B Testing
For significant theme changes on high-traffic forums, consider a gradual rollout using APG vNext's theme assignment system. Assign the new theme to 10% of members initially by setting the new theme as the default for a specific role group, then gradually expand the rollout as you confirm the new theme performs well and no major issues are discovered. Compare key engagement metrics (posts per session, session duration, bounce rate) between the old and new theme using your analytics platform to confirm that the new design does not negatively impact forum engagement. Complete the rollout to all members only after the gradual phase confirms the new theme performs at least as well as the previous design across all key metrics.
Theme Version Control
Maintain the APG vNext theme CSS files in version control (Git) alongside the forum's skin templates. Version-controlling the theme enables: easy rollback if a CSS change breaks the forum layout, clear history of which changes were made and why, branching for experimental design changes that can be tested without affecting the live forum, and collaboration between multiple developers on the same theme without overwriting each other's changes. Store the theme repository separately from the APG vNext application code, since the application code is managed by APG vNext updates while the theme is owned by your development team. Include a README in the theme repository that documents the custom CSS variable names, the theme's design principles, and the testing procedure for changes.
Looking for more help? Browse the support forum or check the Knowledge Base.