Skip to content

Instantly share code, notes, and snippets.

@djones
Created April 8, 2012 00:31
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save djones/2333134 to your computer and use it in GitHub Desktop.
Save djones/2333134 to your computer and use it in GitHub Desktop.
Feedback regarding Refinery CMS
An email exchange regarding Refinery CMS
----------------------------------------
#1 Inquiry received on the Resolve Digital website
From: X
Email: X
I really cannot stop wondering how can you even dare to call something
like Refinery "a CMS". It amazes me even more that you combine that with
the word "awesome"...
#2 I respond to find out more details
Hi X,
Why do you say that exactly? Interested to know.
Thanks,
David.
www.resolvedigital.com
#3 The Response
CMS is a short for "Content Management System". Let's go through it...
Content - Refinery doesn't really deal with content, it's just a WYSIWYG HTML editor. It does not actually let you manage content, but it allows you to edit the markup of your pages, which belongs in the presentation layer. I mean, you put HTML and style information in database tables...
Also it doesn't have any content engine or content types.
Management - There's no piece of Refinery that I could reffer to as "management":
you don't have a proper user management
there is no customization of content types
the menu is autogenerated from all the content
you can hide an item from the menu, but you cannot hide it from being accessed via a direct URL
you cannot put some content in multiple locations
the media management part (Images and Files) is just awfully unorganised and unusable
...
System - Everything is completely non-systematic, the basic functionality of a normal CMS is not included in core of Refinery, and a lot of functionality is scatered among various extra engines.
The core engine has a lot of design flaws.
How would refinery handle a site with 1000 and more pages? In the administration you would get an anourmos unusable content tree in tge "Pages" tab.
...
I believe this sums it up well.
#4 The Second Response
Ah man I can't belive it... your editor is removing the HTML5 <video> tag when you put it in the HTML of the page!
I really must give you this advice...
Please stop what you are doing. Forget about making a CMS, and start spending your time in a more usefull way. You'll be doing the world a big favour.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment