Thread

The thing that has kept me away from EE is simply price, by the time you consider the cost for say 20 websites, its cheaper to develop your own version, is this something that will change in 2.0 ? as i understand the current EE is not developed on CI if i remember what i’ve read…

If your clients can’t afford $250 for a CMS then you have the wrong clients.

Plus the fact you have to support your product, expand on it and document it. Oh and teach someone else how it works if you expand. It will cost you more in the long run.

I agree with this completely.  EE is a bargain!  Also, EllisLab does provides a discount on more than once license.

If it seems expensive, then you’re probably not taking full advantage of the tool or understanding the amount of development effort it takes to create such a tool.

There was no demo version so I had to acquire it for testing another way…

Seriously?

The thing that has kept me away from EE is simply price, by the time you consider the cost for say 20 websites, its cheaper to develop your own version, is this something that will change in 2.0 ? as i understand the current EE is not developed on CI if i remember what i’ve read…

So you’re saying you can develop a CMS with similar features to EE, document it, and support it for $5K?

I’ve never understood the pricing argument when it comes to EE.  $250 is a drop in the bucket compared to the integration and design costs for a custom site running on EE, and if you wrap it into the project costs so the client pays, IMHO it can’t be beat.

As a one-man shop, I’ve also appreciated (and sold clients on) the fact that if for whatever reason I go out of business or get hit by a bus they are left with a tool that other professionals can pick up and work with vs. a custom product.

I have no quibbles over cost as such, the minimum cost of a project with us is £2,000 and max so far has been £20,000, and we have many clients, my problem has been that i have used CMS after CMS and they are never simple, so we use our own, i haven’t been able to fully test EE and im more impressed with 2.0 than the current version which seems over complex… i love CI and i am looking forward to seeing the bridge between the two…

The thing that has kept me away from EE is simply price, by the time you consider the cost for say 20 websites, its cheaper to develop your own version, is this something that will change in 2.0 ? as i understand the current EE is not developed on CI if i remember what i’ve read…

You could develop an application on par with EE for under $5k? You should then.

I suppose i just have to try it out and see whats what, i’m not saying i can create a product like EE, but the features that my clients use on the majority of sites, we have built from our 5 years of developing websites, so i’m looking for the HOOK here (i love CI, so i want to love EE) ... i’ve tried many systems, which are very complex looking for your average client who barely knows how to switch the computer on….perhaps i just need to buy a copy and see how customizable and easy it is to tie into a website…

Excellent news!

I’m looking forward to the new version of EE which will allow me to leverage my favorite open source PHP framework, CI. Unfortunately I recently had to ditch an EE project I really wanted to build a custom app out of , because it was far less time consuming extending CI to a customized PHP application. Having the best of both worlds with EE now though, there is zero reason NOT to buy it!

/sf

Oh god thank you! I love, love CI. It’s what led me to EE actually (or, how I found it I should say). I prefer CI, of course, as a developer, but like EE for certain things.

Having them both together is amazing, and certainly a big step in the right direction. I can’t count how many times I’ve been working on an EE site and have wanted to use things that I rely on in CI but don’t have in EE.

While EE is great for the “I can setup WordPress/Joomla/etc.” crowd, it’s nice to see it merging with, IMO, the best PHP framework out there.

Looking forward to the EE/CI merger and EE 2.0 :D

While EE is great for the “I can setup WordPress/Joomla/etc.” crowd,

Hey! Some of us out here aren’t afraid to get our hands dirty, pal. 😊

I’m looking forward to the change as well.

While EE is great for the “I can setup WordPress/Joomla/etc.” crowd,

Hey! Some of us out here aren’t afraid to get our hands dirty, pal. 😊

I’m looking forward to the change as well.

Haha, well let me rephrase, because what I originally said wasn’t correct. While EE is great for the majority (e.g. the “I can setup a WordPress install” crowd), it’s nice for us that “like to get our hands dirty” to be able to use EE for some of it’s great core features and GUI backend, but still take advantage of the amazing features found in CI.

😉

Yeppers…this is going to be a good year for anyone and everyone involved with EE or CI. I’m stoked!

Yeah, this is a wee bit of a game changer eh. Hopefully it will mean the best of a polished, commercial product, the OS developer community, and a marketplace for new apps/modules/add-ons given the userbase of professional designers/developers prepared to pay for good stuff.

I’ve just got my fingers crossed for nested template groups, or de-coupled url’s & templates 😉

@swanweb, you definitely should check it out 😊 You can strip the backend down quite a lot (you don’t have to give clients the admin keys), and if it’s still too much you can build out entry/edit forms on the front end. Sure there’s a time investment to get your head around it all, but otherwise bill your clients for a few extra hours and enjoy the benefits 😊

While EE is great for the “I can setup WordPress/Joomla/etc.” crowd
rephrase…(e.g. the “I can setup a WordPress install” crowd)

I think I’d quit while your ahead 😉

So my question for this.  I have a personal site I used CI for the framework and little overhead and all the other stuff CI people enjoy.  I want to get a blog going for it.  Choices are either shoehorning something like wordpress into it, building my own, or some still begining modules.  With EE having CI backend, that should mean I’ll be able to use the core component with the blog and have it integrate into CI just like another plugin? Or I guess I’d run EE and then move all my CI stuff into EE?  either way, if that’s possible, I can’t wait.

So my question for this. With EE having CI backend, that should mean I’ll be able to use the core component with the blog and have it integrate into CI just like another plugin? [...]if that’s possible, I can’t wait.

From what I understand, that’s the way it’s supposed to work.