Install ACME Skin System and start editing with 2sxc

ACME Skin System combines a production-ready DNN skin, responsive page designs, editable 2sxc content blocks, and CISS navigation tools. It gives site owners a fast way to launch polished pages without replacing the normal DNN module model.

Why ACME uses 2sxc for content

ACME uses 2sxc as its content layer instead of building another proprietary content manager. 2sxc already provides mature content types, field validation, image and link pickers, repeated items, permissions, native edit toolbars, and Razor views. Customers can work with familiar editing forms while ACME stays focused on the skin, layout system, and reusable design components.

We also avoid storing an entire page body in a single DNN HTML module. Large raw-HTML documents are easy to damage during routine editing: an incomplete tag, removed wrapper, altered utility class, or pasted formatting can break spacing, colors, responsive behavior, and every section that follows it. They also make individual cards, testimonials, pricing plans, FAQs, heroes, and footers difficult to find and maintain.

Meaningful values are stored as structured 2sxc fields. Editors can update text, links, images, lists, and repeated items without touching markup. They can use Change view to switch among curated layouts for components such as Hero and Footer. Developers who need deeper control can edit the app's Razor views and CSS directly. See Customize ACME 2sxc views and Razor source.

DNN modules still work normally

2sxc is the recommended content editor for ACME sample content, but it does not replace DNN. The skin exposes standard DNN panes including ContentPane, HeroPane, TopFullPane, column panes, BottomFullPane, and FooterContentPane. Administrators can add third-party or built-in DNN modules to these panes exactly as they do with any other DNN skin.

Before you start

• Use a Host or SuperUser account for extension installation.
• Back up the DNN database and the /Portals folder.
• Keep an administration page on a known-good skin so you have a recovery route.
• Use the current matching ACME Skin and CISS SideMenu packages from the same release bundle.

Install in this order

1. Open Settings > Extensions in the DNN Persona Bar.
2. Install the supported 2sxc for DNN package and complete its installation wizard.
3. Install the CISS SideMenu module package.
4. Install the ACME Skin System package and review the installation report.
5. Open Site Settings > Appearance, select [G]Skins/AcmeSkin/default.ascx as the site theme, then click Save or Publish.
6. Reload a public page and confirm that the header, menu, content panes, and footer area render correctly.

Create and edit sample pages

1. While signed in as an Administrator or Host, click Edit menu in the ACME header.
2. Open Create sample pages, select the required designs, and create the pages.
3. Make sure every generated page uses [G]Skins/AcmeSkin/default.ascx, then click Save or Publish.
4. Use the native 2sxc toolbar on the page to edit content, add or reorder repeated items, and switch a component with Change view.
5. Add any additional DNN module to an available pane when the page needs functionality beyond the supplied content blocks.

The illustrated workflow is available in Create ACME sample pages.

MegaMenu Builder and standard navigation

CISS SideMenu provides the visual MegaMenu Builder used by ACME, while the skin continues to support standard DNN navigation behavior. Site administrators can organize the page tree, labels, links, visibility, responsive navigation, and richer submenu presentation from one integrated workflow. This keeps navigation content separate from page-body content and allows a site to use simple menu links and advanced mega menus together.

For the complete workflow, read Using the Menu Builder. To see the skin system, standard navigation, mega-menu behavior, and page designs working together, open the ACME Corp live demo.

First-run checklist

• The public page uses the ACME skin and has no theme-installation warning.
• The Edit menu control is visible only to authorized users.
• The Menu Builder opens and can save the current navigation.
• A generated sample page shows native 2sxc edit controls and meaningful fields rather than one raw page-level HTML field.
• Change view offers the curated layouts supplied for that component.
• Additional DNN modules can be placed in the intended skin panes.