Is Revo overkill for relatively small site?

Hi,

I never thought I’d be wondering if I should use MODx because it’s too good, but looking at the feature set of Revo (and the size of the unzipped download) I can’t help but feel it might be a might much. I’m about to start a fairly simple site, not a huge number of pages, but needs the ability to post news items (wouldn’t go as far as saying full-on blogging) and add/remove/edit pages that will be products, as well as more standard page editing.

I can’t hep looking at the size of the unzipped download and think ’jeez, that’s pretty damn big’. I guess the simple answer is stick with Evo, but Revo looks so good!

Dan

Hi Dan,

i think i can add my little two cents as part of an answer. Have you ever thought about the size and implications of php and Mysql on Apache... ? i’m sure not, even when planning to build small websites in which php would just be used to include a menu, an header and a footer and/or mysql to store 4/5 news

For me, in that kind of case, MODx comes as a deluxe layer over the LAMP universe to make, even the simplest website completely editable without having to write an admin of my own for that (that would not be as well done as MODx is). Something like when, 10 years ago, i chose to leave apart SSI and use php3 for simple inclusions or so.

why would we refuse some luxury so gently offered here

Have swing
chris

Hey Dan,

I think the use of MODx is very good even for small sites...as virtualgadjo already said: the ease
of editing is just great...and if i were you (this is my personal opinion) i wouldn’t upload an Evo
release for a website anymore.

Revo is better, faster and build for the future. It’s an amazingly fast system that imho supersedes evolution.

And indeed, why refuse the luxury?

If it’s only for simple blogging or only a company profile, keep the Evo.

If you need a HUGE volume pages or a COMPLEX custom manager page (a.k.a. module), try Revo.

Personally, i do not agree with that statement...as i stated above.
I think revo is very suitable for small sites

Thanks for the feedback!

I’ve only just started testing Revo locally and already I’m very impressed, but I think I might struggle to shake the feeling that I’d be only using 5% of such a powerful system. As some people have rightly said though, why should this be a problem? I think for me, some of that boils down to efficiency, or the sense that you’re using what you have appropriately without a load left ’in reserve’ - those more familiar with the architecture of Revo might say this is complete crap though

I WANT to use Revo, don’t get me wrong, and some of the above concerns are purely from browsing the various directories that make up the new release. It’s not necessarily the fact that I won’t be using all that is capable of, but that everything that makes up Revo is a hefty chunk of CMS goodness (my local install is just under 50MB - an Evo install is probably a 1/5th this size).

I think what’s needed is a live test on my hosting package...

The official position is that if you don’t need any of the features or scalability of Revo, feel free to use Evo. That’s why we still have Evo available for download.

Besides which I’d fly over there and have words with you if you didn’t

Quote from: sottwell at Jul 22, 2010, 11:01 AM

Besides which I’d fly over there and have words with you if you didn’t

Ahah! I now have a scheme to finally meet Susan in person!

That seems to sum it up nice and concisely - if Revo is too much, use Evo.

From the point of view of someone who is not a proficient programmer, comparing all the files/dirs that make up Revo and Evo, Revo still looks quite daunting, especially thinking about maintaining/managing multiple installs for x number of clients.

However, something that has just caught my eye (if I understand this right), is the ability to manage multiple domains from just one install. I have seen a couple of articles about achieving this with Evo too, but regardless of which branch is used, that seems very appealing. If you essentially had a handful of ’small’ sites all running off of the same Revo install then that basically deals with my main concern, as I’d only have to manage 1 install.

Have I understood that concept correctly, or am I going way off track?!

Thanks,
Dan