1-800-COMPANY Mon-Fri: 9AM - 6PM EST
Investors Media Careers Register Login
ACMECORP
ACME Skin & CISS Elementor — A Standard DNN Skin, Built for Speed

Product story · ACME Skin & CISS Elementor

A Standard DNN Skin, Built for the Way Sites Actually Get Made

A collection of theme designs, dropped into one set of multi-purpose panes — with menus and content created visually, by the people who own the site.

A ACME Team · dnndefender.com · 7 min read

For a long time, building a DotNetNuke site felt like a tradeoff. Either you went with a stock theme and lived inside its limits, or you commissioned a custom skin and waited weeks for every layout change. Marketing wanted to ship; developers wanted to keep things clean; editors wanted to stop opening tickets just to move a button. The gap between the three only grew with every release.

That is the gap ACME Skin and CISS were built to close. We did not set out to invent a new module system, a parallel content store, or a proprietary template language. We set out to make a standard DNN skin — the kind any DNN developer can read, fork, or extend — that ships with everything an editor needs to put together a real site in a single afternoon.

One pane system. A whole collection of designs.

ACME Skin is, at its core, a single layout: a set of multi-purpose panes that handle the header, the drawer, the hero, the content area, and the footer. What changes is not the structure, but the design dropped into it. We ship a growing collection of theme designs — corporate, editorial, hospitality, education, healthcare, and more — all rendered through the same panes.

That means you can switch a portal from "professional services firm" to "campus landing page" without rebuilding the structure underneath. New child portal? Pick a design, set the brand colour, ship. The skin file is honest DNN markup — no obscure tokens, no proprietary descriptors — so the DNN team you already have can read it on day one.

What multi-purpose panes really means

Most skins assume the editor knows where things are supposed to go. ACME flips that: every pane is a generic surface that accepts any module — standard DNN Text/HTML, a CISS block, a third-party module — and renders it with consistent spacing, typography, and responsive behaviour. The editor stops thinking about "which pane do I drop this in?" and starts thinking about the page.

CISS Elementor: every essential block, no custom module per page

The pane system would not matter much if filling those panes still required a developer. So we built CISS — an in-page Elementor that ships every essential content block an editor needs:

  • Hero sections with eyebrow, title, subtitle, dual CTAs, background image and theme variants.
  • Image sliders and carousels with optional album filtering and CSS-driven swipe.
  • Tabs and events lists with structured per-event fields and category filters.
  • Photo galleries with multiple albums, cover images, captions, and a built-in lightbox.
  • A shared media library so a photo you uploaded for one gallery is instantly available everywhere.

Every block is configured in a small floating editor, previewed live, and inserted as a standard Text/HTML module. There is no custom database table, no module-per-page proliferation, no runtime JavaScript required on the visitor side. The output is plain, server-rendered HTML and CSS — the kind search engines actually index, the kind that survives a DNN upgrade.

In other words, CISS lets editors compose pages directly — without inventing a parallel content system. The HTML it produces is the HTML DNN already understands.

Menu Builder: visual menus, no markup

Menus are the other place where the gap between editors and developers shows up. We built a visual Menu Builder that lets the people who own the site information architecture — not the developers — arrange every menu item in the browser. Drag to reorder, group items into mega-menu panels, add badges and icons, set per-role visibility, and preview the result instantly. The configuration travels with the portal export, so what you build on staging is exactly what ships.

You can present the same menu as a wide mega menu for comprehensive sites with many destinations, or as a slide-out drawer menu for sites that want a minimal header and an app-like feel. One configuration, two presentation modes — pick the one that matches the audience.

Why this matters in practice

The combination is what makes the workflow fast. Pick an ACME design. Build the menu in the Menu Builder. Drop hero, slider, gallery and events blocks via the CISS Elementor. You have a live site, hosted in standard DNN, indexable by search engines, editable by non-developers, in an afternoon. Need a second portal next week? Pick a different design and repeat.

And because nothing about ACME or CISS is proprietary lock-in, the DNN team can still do everything they have always done. Custom modules still work. Existing skins can coexist on other portals. Your developers are not boxed in — they just get to spend their time on the parts that genuinely need them.

ACME Skin and CISS are available now for DotNetNuke 9.4 and later. You can see the live demo and read the install guide at dnndefender.com. If you want to discuss bringing this workflow to your team, write to support@dnndefender.com — we read every email.

DotNetNuke ACME Skin CISS Elementor Menu Builder Mega Menu Drawer Menu
MegaForm for DNN - Modern Self-Hosted Form Server
MegaForm for DNN

Modern Forms, Workflow Automation, and Self-Hosted Control — All in One Platform

MegaForm helps transform your DNN portal into a modern form platform inspired by the ease of Typeform and Google Forms, while giving you far more control over workflows, integrations, branding, publishing, and data ownership.

At Last, We Published the Form Platform We Wanted to Have

A more article-like introduction to why MegaForm matters.

For a long time, many teams loved the convenience of tools like Typeform and Google Forms, but they still wanted more. They wanted stronger control over branding, deeper workflow capabilities, better integration with databases and CRM systems, richer widgets, more flexibility in how forms are published, and most of all, real ownership of the collected data.

That is exactly why MegaForm matters. After a long journey of design, engineering, testing, refinement, and practical business thinking, we finally published a form platform that feels modern and easy to use while still giving organizations the control they need. MegaForm is designed to help DNN become much more than a CMS page with a few input fields. It can become a true form platform.

What makes this especially powerful is that MegaForm is flexible in how it is used. It can be used as a normal form module directly inside your own DNN portal, just like any standard form module. In that mode, forms become a natural part of your website, your business pages, and your portal experience. But MegaForm can also go beyond that role and act as a broader form server, allowing you to publish and embed forms for external audiences across landing pages, partner sites, campaign pages, or even WordPress websites.

In other words, MegaForm lets you start with simple portal-based forms and grow into a centralized, self-hosted form platform as your needs expand.

This is important because many organizations do not want their collected data to live on someone else’s server by default. They want the convenience of modern forms, but they also want self-hosted control, stronger integration options, and the confidence that their workflows belong to them. MegaForm gives them that option.

It is not just about collecting a few names and email addresses. MegaForm supports a much wider range of real-world scenarios: signatures, repeatable sections, uploads, spam protection, multi-step flows, appointment-like experiences, payment-ready journeys, conditional behavior, embedded publishing, and workflow automation into database operations, CRM processes, webhooks, and more. This makes it useful not only for public forms, but also for internal operations, intake workflows, service processes, registrations, approvals, and customer journeys.

Another major advantage is the role of AI assistance. Not every user wants to spend hours building layouts by hand or dealing with raw HTML and CSS. MegaForm is built with the idea that AI can help teams create better forms faster. Instead of starting from a blank page every time, organizations can use AI-assisted thinking and structured templates to move from idea to live form much more efficiently.

For teams that care about privacy, internal ownership, custom process integration, or long-term extensibility, that is a major strategic advantage. MegaForm gives you the ability to offer the kind of polished, workflow-ready form experience people expect from modern platforms, while keeping your infrastructure, your integration logic, and your collected data under your own control.

Rich Widgets That Go Far Beyond Basic Forms

MegaForm is not limited to plain text boxes. It supports a wide set of practical widgets needed by real organizations.

Signature

Capture Signatures with Confidence

Use signature fields for consent forms, acknowledgments, approvals, agreements, and workflows where a visual sign-off matters.

Repeater

Repeatable Sections for Real Data Entry

Add repeated entries for participants, products, services, dependents, invoice lines, items, or structured business records.

CAPTCHA

Protect Public-Facing Forms

Reduce spam and abuse with CAPTCHA support for contact forms, lead forms, inquiry forms, and open public submissions.

Upload

Collect Files and Attachments

Allow users to submit supporting documents, attachments, images, and files as part of the overall form process.

Multi-step

Create Guided Form Journeys

Break long forms into better experiences with sections, page breaks, wizard-style flows, and more controlled progression.

Conditional Rules

Show the Right Fields at the Right Time

Build smarter forms that adapt to user input, reveal only relevant questions, and keep the experience cleaner.

Appointment

Support Scheduling Scenarios

Build form journeys for consultations, reservations, booking requests, time slots, or service scheduling workflows.

Payment

Payment-Ready Form Experiences

Support scenarios where payment becomes part of the form process, helping forms move closer to real transactions.

MegaForm also includes the practical building blocks teams expect every day: text, email, phone, number, textarea, select, checkbox, radio, date, content blocks, sections, and structured layouts for polished forms.

Workflow Engine and Business Integrations

A form should do more than collect data. MegaForm helps submissions move into real business processes.

DB

Database Integration

Use submitted form data as part of database-oriented workflows and operational storage processes.

CRM

CRM-Oriented Flows

Move leads, requests, and customer interactions into broader CRM processes instead of manual copying.

WH

Webhook Automation

Send events and payloads to external services or custom endpoints for integration and orchestration.

WF

Operational Workflow

Trigger approvals, notifications, follow-up actions, and internal business routing after submission.

From Form Submission to Action

MegaForm is built so that a form submission does not have to end as an email notification sitting in an inbox. Instead, it can become the start of something more meaningful: a business process, a CRM action, a database operation, an external trigger, or an internal decision flow.

  • Send data into structured systems
  • Trigger business automation after submit
  • Support operational workflows, not just data capture
  • Connect forms to the real movement of work

Why This Matters

Many form tools are convenient, but they stop at collection. MegaForm is designed to support the next step as well. That is what makes it useful for registrations, intake, internal processes, lead handling, approvals, service workflows, and customer journeys.

MegaForm helps forms become part of your process, not just a place where information gets stored.

Use It Inside Your Portal or As a Broader Form Server

MegaForm is flexible enough to work as a normal form module or as a larger publishing platform for wider audiences.

Use MegaForm Like a Normal Form Module

MegaForm can be used directly inside your own DNN portal, just like a standard form module. This gives you a fast and professional way to publish forms naturally as part of your portal, business pages, intranet, or customer-facing site.

  • Portal-based contact forms
  • Registration and request forms
  • Internal operational forms
  • Department or workflow-specific pages

Use MegaForm As a Form Server

MegaForm can also act as a broader self-hosted form server. In that model, you manage forms centrally and publish them beyond your main portal, reaching other websites, landing pages, campaigns, partner channels, and external audiences.

  • Embedded forms for external sites
  • Landing page and campaign publishing
  • WordPress and external audience scenarios
  • One engine, many publishing channels
This means you can begin with simple portal forms today and grow into a centralized, self-hosted form platform tomorrow without changing the core direction of your solution.

AI-Assisted Building and the Value of Self-Hosted Control

MegaForm combines the convenience of modern form tools with the ownership and extensibility serious organizations need.

1

Describe

Start from the business goal, not from raw HTML and CSS.

2

Design

Use AI-assisted thinking, templates, and structured layouts to shape the experience faster.

3

Publish

Render forms in your portal or publish them out to wider external audiences.

4

Automate

Connect form submissions to workflows, database actions, CRM flows, and webhooks.

5

Own

Keep your infrastructure, your branding, your workflow logic, and your data under your control.

More Than a Form Builder

MegaForm is built for organizations that want the polished experience people expect from modern form platforms, but do not want to give up control over their branding, publishing model, workflow logic, or collected data.

For teams that care about privacy, internal ownership, custom process integration, or long-term extensibility, that is a major strategic advantage. MegaForm gives you the ability to offer modern, workflow-ready forms while keeping your infrastructure, your integration logic, and your collected data under your own control.

MegaForm can be used as a normal form module within your own portal, or as a centralized form server for publishing forms to a wider external audience. That flexibility is what makes it such a strong foundation for DNN-based form experiences.

DNN and Oqtane

I've been working with DNN Platform (DotNetNuke) since the very early versions – it's familiar, powerful, and "does everything." Recently, I've also spent a lot of time with Oqtane – the "spiritual successor" from the same creator, Shaun Walker. After multiple large and small projects, here are my honest, no-fluff thoughts to help those of you who are still deciding.

1. DNN: The Reliable "Big Brother" – Does Everything, Super Familiar

DNN really can handle almost anything. Modules? Thousands available – membership management, events, e-commerce, ERP integrations, industry-specific ones (real estate, hospitals, schools...). Skins? Ready-made, beautiful, responsive for years. The admin panel is so familiar that you know exactly what to do just by looking.

I used to think DNN was too legacy-heavy (WebForms, old postbacks, lower performance compared to modern stacks). But recent BuiltWith data (early 2026) shows ~48,000–49,000 live sites, with signs of slight growth again. Why?

  • DNN 10.x updates (especially 10.0 to 10.2.x) have improved a lot: removed legacy APIs, better .NET Framework 4.8 support, JWT/API tokens, smoother content approval, constant security fixes.
  • Many enterprise and government sites have run DNN stably for 10–15 years – low maintenance cost, familiar team.
  • Commercial module ecosystem is still alive; many providers continue selling high-quality DNN modules.

In short: DNN isn't "Old guy" as some AIs think. It's like an old reliable truck that's been upgraded with a new engine, next to a super market with full of goods– still great for long hauls.

2. Oqtane: Lightweight, Blazing Fast, Modern – But Ecosystem Still "Young"

Oqtane is completely different: full Blazor (.NET 8/9/10), SPA experience (no page reloads), incredibly fast page loads (especially Blazor Server + prerendering). Code is clean, modular just like old DNN philosophy: plug-and-play modules, multi-tenant, easy to extend.

I've tested small projects: really quick deploy and fast on same hosting account, I am sure it can work with any hosting providers, sql.. . The admin panel is simpler than DNN but get improved – true plug-and-play feel.

Real talk though:

  • Available modules are still limited (mostly core + some high-quality community ones).
  • Themes/skins aren't as rich or varied as DNN's.
    • Blazor is currently the best technology anounced by Microsoft --> that's why.
  • For complex features right away (advanced membership, full e-commerce), you'll need to build or wait – more time than DNN.

3. Our Team's Conclusion: Run Both in Parallel – But With Eyes on the Future

After careful evaluation (and checking recent forum activity):

  • DNN is very comfotable for building portal, documents management, pemissions based.
  • Anything running well on DNN (large legacy sites, existing clients, ready modules) . Upgrade to DNN 10.x for security and performance stability. No rush to migrate if there's no urgent reason.
  • But for all new projects (2026 onward) → prioritize Oqtane. Reasons: modern tech, Blazor is hot and sound so promising, high performance, long-term future-proof (.NET 10 LTS until 2028). We're building shared core modules (auth, multi-tenant, content) to reuse across both, and migrate gradually when needed.

We still love DNN – deeply. It's given us so much over the years: stability, ecosystem, familiarity. But from what we've seen on the forums and in the broader .NET community, even though we love DNN, we also love Oqtane for carrying forward the same modular, developer-friendly spirit – just rebuilt for today's world (Blazor, SPA, cross-platform potential).

This dual approach lets us:

  • Retain old flatform (stable).
  • Prepare for the future (performance, mobile hybrid, cloud-native) and dont have to look elsewhere: WP, Umbraco....
  • All tools we have.

Update 2026: What Our Team Is Actually Building to Bridge DNN and Oqtane

Many of you asked: "So what is your team concretely doing to support the transition?" Here's the real update (March 2026).

  1. Tool to Convert DNN Skins for Use on Oqtane
    Our biggest (and most challenging) ongoing project. DNN skins are typically .ascx files with server controls, Token replacements, skin objects, and inline Razor/VB, C#, HTML/CSS mixes. Oqtane themes are pure Blazor Razor components (.razor files) + CSS/JS, using Layout.razor, Pane components, and dynamic rendering via Cascading parameters.
    Currently in internal beta. Goal: public release (low-cost) soon.
  2. Form Module That Runs Seamlessly on Both Platforms
    We built an Advanced Form Builder from scratch.
    - Native on DNN and 100% on Oqtane.
    - Shared codebase: validation, submissions, emails, integrations.
    - Multi-tenant, conditional fields, file uploads, captcha, anti-spam.
    Already live for several clients; great feedback on speed and UX.
  3. MegaMenu: About to Release!
    MegaMenu is essential for large sites.
    - Finalizing a MegaMenu module for Oqtane (with DNN compatible version).
    - Features: Drag-drop builder, icons support, mega dropdown columns, mobile responsive.
    - Planned: Q2 2026 (possibly sooner).
  4. Our Iron Rule: 12+ High-Quality Modules per Year – No Junk
    Team commitment:
    - Only high-quality: clean code, documented, tested, secure.
    - No low-value or buggy modules.
    - Target: 12+ per year, focused on real enterprise needs.
    All aim for cross-compatibility between DNN & Oqtane.

Final Thoughts

We haven't abandoned DNN – we still maintain legacy sites and appreciate everything it has built. But with quieter forums and shifting community energy, we're excited to embrace Oqtane as the natural evolution.

If you're on DNN and worried about the future: Follow our skin converter tool and cross-platform modules. We're happy to share beta/tests (comment or DM me)!

What do you think of this direction? Which module would you like us to build next? 😊

#dotnet #blazor #oqtane #dnn #cms #aspnetcore #moduledevelopment #migration

All Posts Author: SuperUser Account

Modern Webshells 2024–2026: Minimal C# Loader Techniques with Encrypted Payloads from C2 and How They Bypass Detection

Posted on: February 13, 2026 | Author: Hung

Today, we will examine one of the detection capabilities that the DNNDefender module is designed to provide—specifically, the types of stealth techniques that are often overlooked by traditional antivirus engines or hosting-level firewalls. While AV solutions typically rely on signatures and generic heuristics, and hosting firewalls focus on network-layer filtering, modern loader-based implants often operate within legitimate IIS and .NET execution flows, making them far harder to identify.

2026-02-12
2
0

Why Bots Target Forms, including DNN ones

Automated bots frequently target DNN contact and registration forms with malicious intent. Common goals include:

  1. SEO Backlink Spam — Submitting links to scam/gambling/fake sites to create unwanted backlinks from your site.
  2. Spam Relay Abuse — Using “send me a copy” features to turn your server into a spam sender, risking domain/IP blacklisting.
  3. Vulnerability Exploitation — Probing forms for SQL Injection, XSS, or other attacks (e.g., deserialization, password reset abuse) that can lead to full compromise.
  4. Mass Fake Account Creation — Flooding registration forms to build fake accounts for future spam or abuse.
  5. Resource Abuse (Application-Level DDoS) — Repeated submissions overload database, email queues, and server resources, slowing/crash the site and raising costs.
2026-02-12
4
0