9 comments

  • UX ING, 4 years ago

    A CMS that practically takes a CS degree to setup and configure. Exactly what the CMS demographic is looking for!

    I’ll bookmark this one in the same folder as my CLI toaster.

    8 points
    • Catalin CimpanuCatalin Cimpanu, 4 years ago

      Sharing because it's actual "news" on DesignerNews, rather than personally recommending it :D

      1 point
    • Mike Wilson, 4 years ago

      Savage but true.

      There’s probably 500+ static site generators and 50+ Static site CMS options out there right now—and 0 of them are anywhere near the ease of use of Wordpress for non-technical people.

      Hence why Wordpress won’t die. Every time you expect a user to fire up the command line + git and deal with constant errors over installing and updating and configuring packages and pre-fixers and build process and blah blah blah...you’ve lost 98% of your potential customer base.

      9 points
      • Taylor PalmerTaylor Palmer, 4 years ago

        While I agree, there are still markets for more technical CMSs like this.

        Their goal likely isn’t to appeal to non-technical web content admins, but to a small site developer who doesn’t want to write their blogs in straight HTML.

        0 points
        • Aaron Wears Many HatsAaron Wears Many Hats, 4 years ago

          I'd like to argue that the developer of this particular CMS seems to think otherwise.

          I’ve been setting up content management systems for people since the early 2000’s. In the beginning, CMSs like WordPress and Drupal gave our non-developer colleagues website editing powers. But we’ve seen very little innovation on the editing experience in the past 10+ years. Meanwhile, the editing experience of site builders like Squarespace, Wix and Webflow have become very sophisticated.

          When I watch people use a traditional CMS, I often see them struggle because the input (the CMS) lacks the context of the output (their site) and using a CMS feels more like filing your taxes than editing a website. Now that we’ve moved to headless CMSs and the JAMstack, editors often lose the ability to preview, leaving them in the dark as they create content.

          From my reading, they've said "in the past, wordpress and drupal give editing powers to non-developers", and goes on to mention the experience of site builders for non-devs like wix etc. Then pivots to "so hey I built a JAMstack webapp that needs to be built from the CLI"

          Seems like its at odds with itself IMHO.

          1 point
      • Todd Padwick, 4 years ago

        Craft CMS beats ease-of-use for non-technical people any day... Also has a similar live preview feature to Tina CMS, and with far more capability. https://craftcms.com/

        0 points
    • Andrew C, 4 years ago

      It doesn’t look that difficult?

      But I suppose if you’re technical enough to do this then Wordpress or vanilla HTML/JS isn’t out of the question.

      1 point
  • Frédéric AudetFrédéric Audet, 4 years ago

    You guys are a little hard on Tina, it's actually pretty cool. Tina can't be compared to WordPress. WP is a CMS you install first, then add content to it. Tina is a toolkit that allows you in add editing capability to an existing site. That can be done on your server, or on Tina's cloud. Not the same!

    0 points
  • Dan GDan G, 4 years ago

    it's weird how well the llama is designed considering everything else

    0 points