🚀
Uniweb CMS
English
English
  • Uniweb CMS
  • 💫Let academic websites build themselves
  • Guides
    • ☁️How to manage content with profiles
    • 📰How to create content-first websites
  • Video playlists
    • ▶️Content management and website building
    • ▶️Feature walkthrough
    • ▶️Website template creation
  • Advanced Use Cases
    • 🎨How to create website templates
      • 🎋Design starts from data
        • 1️Creating logical data paths
        • 2️Planning for exceptions
        • 3️Defining clear, logical rules
        • 4️Other data design elements
      • 🗺️Think about the viewer's path
      • 🗃️Filter options, defining ranks for content, and more
      • 🖌️The design process
      • 🛠️Uniweb Launchpad
Powered by GitBook
On this page

Was this helpful?

  1. Advanced Use Cases
  2. How to create website templates
  3. Design starts from data

Other data design elements

PreviousDefining clear, logical rulesNextThink about the viewer's path

Last updated 2 years ago

Was this helpful?

With the most important elements out of the way we can look at the other ones. To begin we have a card for notes. This can communicate more general ideas that cannot be communicated through the Figma mock-ups or general themes that cover a large section of content

And finally, for the data design elements, we have the user-configurable options box. This allows you to define options that can be changed.

You cannot let users change anything UI related (number of columns in a list, size of specific images, etc.) Instead your configurable options should be content related (pin one type of publications to the top of the page, replace an image with a different one, etc.).

Keep in mind, the PDD methodology is meant to eliminate most, if not all the time spent on creating and managing a website. Overwhelming users with more choices is not always a good thing.

🎨
🎋
4️
Note card
User-configurable options card