Skip to content

[Enhancement]: Aperture Theme Wrapper Issue: Enhancement Suggestions for Community Discussion #7041

@Timo-Breumelhof

Description

@Timo-Breumelhof

Is there an existing issue for this?

  • I have searched the existing issues

Description of problem

First of all, I value the effort that went into the new Aperture theme for DNN 10. But I do think it could serve our community in an even better way by adding some things. I would like to have an open discussion on what other things could be useful — I'm just listing my first thoughts here.

Background & Motivation
The Aperture theme is a great starting point, and IMO it could serve two important purposes beyond aesthetics:

Showcasing DNN's capabilities
Giving users and evaluators a real sense of what the platform offers out of the box.
Helping surface issues early — features that aren't exercised in the default theme are more likely to go untested. Issue #6712 is a good example of something that might have been caught sooner had Search been part of the theme.

Suggested Improvements

  1. Additional Theme Objects
    Consider incorporating more of DNN's built-in Theme Objects to better demonstrate platform capabilities like:
  • Search — showcases core search functionality
  • Language Selector — highlights DNN's multilingual capabilities
  • Messaging — surfaces the messaging system
    (Other suggestions from the community welcome)
  1. Multiple Panes & Drag-and-Drop
    The theme could demonstrate the use of multiple content panes and module drag-and-drop — a distinctive DNN capability that's worth highlighting for both new users and developers.

  2. Concept Documentation
    It would be valuable to document the design intent and concept behind the Aperture theme — what it's trying to achieve, what principles guide its structure. A good home for this could be DNN Docs (?), with links back from:

The theme's intro/default page
Comments within the theme files themselves

This would help contributors understand the vision and make consistent contributions over time.

Next Steps
This is intentionally a discussion-first issue. Feedback, pushback, and additional ideas are all welcome. :-)
Practically: create child issues for the individual items?

Description of solution

Get feedback :-)

Description of alternatives considered

No response

Anything else?

No response

Do you plan to contribute code for this enhancement?

  • Yes

Would you be interested in sponsoring this enhancement?

  • Yes

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions