Why We Built It
Having spent years developing websites on well known platforms such as Wordpress, Joomla , Drupal & similar, we as a collection of designers developers and normal human beings decided that there HAD to be a much more "huggable" way to offer the same flexibility, ease of use and outright publishing power of the "big boys" without the need for hours of training or 1000's of pages of support documentation in order to change a video clip or bullet point !Now if these things annoy us as "professionals" in our field then we can only imagine (thats a lie we have witnesssed this in person, over the phone and via email , msn & facebook .... ) the chaos that ensues when a website is handed over that has more options for adding content than you get making a sandwich at Subway!
And so MIQWAI was born ....
MIQWAI was built around the following principles ...
Easy to Use
Let's face it. Most of the time, as a website owner you want to only be worrying about what content you want where , not how to actually get it there ....
Easy to use navigation is of utmost importance within the admin screens ...
a distinct lack of long convoluted processes to add images , posts , pages , links etc
If you need a piece of content to be placed in multiple places in the website, it would be nice if the CMS could handle that for you . The benefit of a customized solution is that the development team can tweak the CMS to anticipate your needs and be ready to deliver when you need it to.
When you need help, you want to get to it quickly and easily. Tool tips, easy-to-locate help sections, videos on how to do a certain process, FAQs, videos etc , these are all extremely helpful.
If you are going into your CMS to update a bullet point, you don't want to have to jump through hoops to get it done. Likewise, if you are adding an entire new section to the site, inputting SEO-relevant content, you expect some complexity, tags and keywords, along with some checks and balances along the way.
If you want something to be done, it should be possible. This is one of the reasons we developed our own CMS: So we could do the things you wanted to be done within the system.
Don't you love when you hit one button and it seems the whole internet goes down? Or, at the very least, it seems you may have fried some sort of major thing with servers and possibly satellites and you swear you smell smoke? A good CMS should keep you out of harm's way. You shouldn't be able to do massively bad things without being loudly prompted (several times) by your CMS:
"Are you sure you want to delete that page?"
"Are you sure you want to erase a week's worth of work?"
"Hello ........ DELETE IT ALL .... PHONE A FRIEND?"
You want the people who need to know, knowing. And those who only need to know a little, well, they should be in the 'know a little' room. A good CMS should allow for security and user account settings to be configured in such a way as to protect your sensitive information on the back end of your site, as well as on the front end. The system should only show users what they have been authorized to see. No more. That way, your disgruntled intern can't mosey on over to the professional bios section and add a line about Mr. Smith's rumoured fetish for bacon wrapped sprouts ...or something like that. You get the idea.
If you want your team to do something, willingly, proactively even, then that "something" better be pleasurable to engage with.
Have you ever had your team say "no thanks" when you've invited them down for a coffee and cake/brainstorming session?
You make the brainstorm process more pleasurable by including the coffee and cake. A little pleasure goes a long way, which is why we think a CMS's administrative area should be as nice looking as the front-facing website, if not nicer. It should be organized, friendly, use real world language not things like "vars" or "default" that only make sense only to programmers. It should help you if you make a mistake, allow you to play without fear of crashing, and inspire you to log in and keep creating great content!
A CMS is essentially tools for the creative process, same thing as Photoshop to designers, or paint and brushes to a painter.
Who wants to create something in a sterile, threatening and confusing environment?
This is the most important element for a good CMS. Simple does not mean weak or limited.
Simplicity is difficult to achieve and requires great effort and restraint to get it right. Sure, we could probably add modules to the "MIQWAI" that would allow our clients to do some crazy stuff, but they don't really need it. And, if they do, it's one client out of a million. In that case, we do something custom just for them. Keeping the CMS simple allows you to build a solid foundation first. Then you have time in real world scenarios to determine if you really need it to "do crazy stuff" or not.