Not signed in (Sign In)

SkillShare - A place to discuss Web Standards and Web Design topics

Categories

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthoronecreative
    • CommentTimeNov 2nd 2006 edited
     permalink
    My good friend Mike has been at it for years now, providing a custom solution for his clients that is built just the way it needs to be... Proprietary and Simple - Page editing at it's simplest, along with apps he's built himself.

    However, I don't have nearly the patience, or brainpower - I'm definately more a graphic/css designer - still learning the ropes, and don't currently have the strength or experience to build my own. So I wanted to get the voice of the community here and see what your solutions are.

    To note some CMS/Blogging Engines I've used and *customized for clients are: Wordpress, Text Pattern, Joomla, and soon to try ModXCMS - http://modxcms.com
  1.  permalink
    I'm curious, when you say you've "customized" engines like Wordpress for customers, what exactly does that entail? I've often thought of using Wordpress for my freelance clients, but customization was always a concern.
    •  
      CommentAuthorbenjwalker
    • CommentTimeNov 3rd 2006
     permalink
    Personally I've started building custom CMS's, it's the best option if you've got the knowledge to do it. (It's surprisingly easy to do the basic stuff, the advanced not quite so easy!). It means you have greater control and understanding of what you're playing with.

    Using a popular blog/CMS is a good alternative, but only if it fits the project. In the past I've used CuteNews, that's good if you just want to build a site then shove chunks of editable content in.
  2.  permalink
    chriscamargo - Customizing the front and back-ends so they are branded. Building templates from the ground up and/or modifying an existing theme. These have been heavily documented, and are pretty simple to do. Most clients of mine want to update their content very easily, with little or no html experience. Built in WYSIWYG editors are very good at handling this.

    benjwalker - I am interested in doing this also, and would like to learn more about building my own. Any pointers?
  3.  permalink
    There are so many out-of-the-box CMS and blogging solutions out there, I really don't see a need to custom build one. From open source to high-end enterprise solutions, someone has already built a CMS that will fit your client's needs. If your skills are primarily in design and front end development, I would suggest focusing on learning how to get the most of a few different CMS solutions that your clients may need; in other words hack the Hell out of them.

    Consider the amount of time/money it would take you to build a CMS vs. how much you might charge a client for the licensing fee of a Movable Type or Expression Engine.
    • CommentAuthorMatt
    • CommentTimeNov 3rd 2006
     permalink
    Only time I feel a custom cms in needed is for when you are creating an inventory of products.
  4.  permalink
    Adjustfresh - Sometimes, those engines aren't perfect for the content. Photo galleries, flash, flash video, etc. When you design a blog like site, yeah, a blog engine will work. I've built custom cms before, multiple times. And sometimes, it comes down to xml files, php includes, mysql, etc.

    It comes down to content. The question itself is subjective. And the cost of a custom cms dependant upon rather dynamic and varying content outweighs the cost of a license. Maybe I'm unfamiliar with those systems but a rather unique design calls for something less cookie cutter.



    CSS != blog.
  5.  permalink
    Just trying to survey the land...

    I would definately opt to have my own proprietary solution in the future. Not only would it benefit me as a developer, but also my clients in that I wouldn't be serving them commons.

    For now, for the time allowed, and for the pay - I will use what I have available, but Mike, I want those source files! Catchya latr.
  6.  permalink
    Right now, I'm using open source CMS-solutions, primarily Drupal, while I work on my own full-featured systems to offer later, when I plan to move into more freelancing/running my own small business.

    The benefit to having your own solution is that it is your baby--you know it from the ground up. Sure, like one of my co-workers, you can make things like Drupal your baby, but I'd personally feel more accomplished, and feel like I'm offering a better service, were it my own solution.
  7.  permalink
    Sounds to me like those of you who want to build your own CMS are doing it primarily because it suits your egos rather than your client's needs. The content management systems that I have experience with (everything from open source to very high-end enterprise solutions) have all been very customizable--not cookie-cutter in the least. In fact, the primary CMS endorsed my my company, made by Hannon Hill, runs several of our sites; it is completely customizable (XML/XSLT based) and you wouldn't be able to see any similarities between the sites that are running it to power their content.
    •  
      CommentAuthorbenjwalker
    • CommentTimeNov 5th 2006
     permalink
    Building custom CMS solutions from scratch is more to me about - Creating a fully bespoke solution, Working in technologies and techniques that I personally understand, Knowing the product inside out so you can solve any problems.

    There are some good out-of-the-box CMS's out there... there are also some shoddy ones! Just because the car's already been invented, doesn't mean no-one ever produces a new one :)
  8.  permalink
    I agree... I mean without a doubt building your own system - and supporting it yourself is a great responsibility, however, the credibility you earn among the design community is tremendous. Not only are you a designer that understands standards compliant design, but also a developer building greater momentum.
  9.  permalink
    Well written Ben.

    Adjustafresh - Egos? I have no clue what you are talking about. None of the people that talked about building their own cms sounded remotely. Hacking the hell out of a pre-built CMS is fine if you have the time, but if you have already built a cms that mainly operates on 'widgets' that you have wrote, well it's bluntly not about ego, it is about the client, it's about knowing the system and being INDEPENDENT of others. If you want to talk about client's best needs, then say something like ego... You don't know my clients, and you don't know me well enough to use words like egos. I'm sorry if our words in support of custom CMS might have touched a soar spot.

    I've built a CMS for my own site that OneCreative can attest and say it's brilliant for it's application. I can run any kind of site off of it, expand when needed. Even suggesting I package it up and release it. Rather bogus to suggest the people who can build good CMS systems do it out of ego... Some of us don't want to wait on others, or a widget, a bit more progressive than that. When we have the time, we build what we need for the client. In essence a developer creates a swiss army knife for their client, adding photo galleries, writing their own faq, uploading flvs, but keeping it all simple, not overwhelming to the client.

    But where do you think the CMS applications that people use come from? Making what they need, then broadening it out as people see that it's usable past the developer's application.

    I'm sorry, but suggesting spending time to hack something to all hell can be THE BIGGEST WASTE OF TIME if you know how to build a cms in certain circumstances. Don't be telling people about egos when you are goin off assumptions, it's not in good taste.
  10.  permalink
    the credibility you earn among the design community is tremendous

    Right... not about ego at all.

    Mike - it's unfortunate that you took the word "ego" negatively. The word wasn't meant to have a negative connotation; as in "egotistical". I'm not saying that building a custom CMS is always about the developer. Sometimes a custom solution may be the best option depending on the client. But for "onecreative" to say that building a custom CMS will earn him "credibility" among the design community...well, that kind of makes my point. Doesn't it?

    Let's put this to bed. If you have the time and skills to build and support a custom CMS that will best suit your clients' needs, by all means--go for it. If you're building something just because it looks good on your resume, your client probably shouldn't be footing the bill.
  11.  permalink
    I'd put it to bed, but that last remark about client's footing the bill and designing something just for a portfolio... If client's come because of the work in the portfolio, it's not them flipping any bill just as much as it is having them pay for a license or the time to modify a CMS, it is about the same to the client. Credibility in the design community isn't associated with ego, it's associated with wanting to steer as many people in the right direction as possible.

    Honestly, I tried negating all this talk with making a point that it's subjective and comes down to the client and their needs. I was thrown when the word ego was used, as I've never seen ego used in a good way, and to use it on such a question, with little input on the ones you are using it on. I by no means am trying to demean your best practices Adjustafresh, but please dood, don't ask to put something to bed when you finish the way you did.


    My only point is that is is subjective and that a good CMS comes from a developer or group of designers working that develop a system out of work flow. Once it hits the right spot, it's released for public use. Is it for their ego? To make their portfolio look better? YES, because a custom well built specialized system that takes care of their clients is something to sell and increases productivity and therefore it is for the client. Not for dispute on a forum that has seemingly strong headed views from those who haven't seen a custom CMS from a person on the opposite side.

    I'm not trying to flame you, but the things you've said lead me to believe you are strong in your position and haven't been forced outside of it to see the other side of the grass. Nothing wrong with that, but just don't assume it's ego, then defend ego, then quote someone saying 'proves the point' using it in a negative way. Not trying to teach you internet behavior, but pointing out that your defense of a pre-built CMS is based on negative assumptions from people you do not know, not solid examples of how a pre-built CMS doesn't turn out generally cookie cutter sites. I know they don't have to be, but part of their appeal, is just that. Quick, standard systems to make compliant sites that just look like a blog with box model designs. It's rare to see a pre-built CMS whipped into shape.

    I'm also playing devils advocate.
    • CommentAuthormista3
    • CommentTimeNov 8th 2006
     permalink

    If I was going to build my own CMS (which I won’t being a designer), I’d look into a framework like Django or Ruby on Rails… which has the building blocks already in place…

    Eg: Wordpress clone in 27 seconds using Django

  12.  permalink
    cmsmadesimple (cmsmadesimple.org) is pretty easy to get up and running for basic websites.
    • CommentAuthorekonym
    • CommentTimeDec 11th 2006
     permalink
    Wordpress with lots of custom template pages.
Add your comments
    Username Password
  • Format comments as (Help)