7
3 Comments

What would your top 5 CMS no-code features be?

Hey no-code fans :) I'm working on something with a friend (in pre-alpha...I'll let everyone know when it's available for alpha and beta testing) and I'd love some input...

I'd like to know what are the most desirable features, or perhaps even what you consider to be prerequisite features for an MVP of a content management system (CMS, like wordpress) are from your perspective?

Naturally I'm thinking super MVP, here's some examples:

  • Easy to get started with an array of page templates
  • Enable embeds so third party tools and content can be easy dropped into pages
  • Use simple, accessible language
  • Be multi-page
  • Be quick and affordable to get live
  • Look good by default
  • Be responsive by default

I'm talking true no-code here, not code-light - imagine it's a tool so your grandmother can make a website to show off her knitting or something.

Thanks :)

on December 4, 2019
  1. 1

    Hello @blunicorn,

    Let try our new product here if you are interested: https://www.producthunt.com/upcoming/layouthub

    Its a Page Builder for Shopify and WordPress. We focus to make a Big Library of Layouts/Sections ready to use. Just select layout you like then edit with text and images to publish.

    We build this product for really people without code, design skills can use

    Best Regards

  2. 1

    Integration to a payment system like Trolley for an ecommerce experience.
    (I would say that, I'm the maker of Trolley!)

    And:

    • Rather than responsive-by-default, aim for mobile-first.
    • Think about how customers can move off your platform if they're successful enough to outgrow you.
    • Think about sign-in options for admins & content authors; companies will want e.g. sign-in-with-Google.
    • Support some kind of approval workflow (think PRs for content) - most decent CMS have this now.
    1. 1

      Thanks Rory, sign-in-with-google we already set up :) I like the approval workflow suggestion too. It's a bit too early in the project to think about how people move off the platform, but also worth thinking about from a GDPR perspective I guess!