EllisLab Seeking New Owner for CodeIgniter


EllisLab prepares to say farewell to a much beloved product.

CodeIgniter is one of the world’s most popular Open Source PHP frameworks, used by thousands of developers powering hundreds of thousands of sites, in addition to being deployed as the underpinning of every ExpressionEngine installation. As of this writing it is the second most watched PHP project hosted at GitHub, surpassing Slim, Yii, CakePHP, Zend, and Laravel in either followers, contributors, or both. It has the highest number of forks of any PHP project at GitHub of all time. It is used by everyone from AT&T to Home Depot to Dictionary.com, to Rachael Ray to Magento to the Mail & Guardian, to the Universities of Missouri, Michigan, Texas, Georgia, and more (Sources: builtwith.com, wappalyzer.com). And it is used as the server-side back end for many mobile apps.

Throughout its seven year life thus far, CodeIgniter has consistently received praise for being both speedy and surefooted. Small and lightweight, resistant to feature bloat, retaining compatibility with contemporary technology, the framework earned the reputation of being low-risk and high-gain, which fueled its worldwide adoption.

So why are we we looking for a new home for CodeIgniter? At EllisLab, our overriding goal is to relentlessly pursue only the things that are both right for us and that best serve our customers’ needs. Everything we do must utilize our resources properly and must fit within our business model and goals. If we cannot give an opportunity the proper attention it deserves without sacrificing from elsewhere, the responsible action—even if it’s difficult—is to say no.

In the last few years we moved CodeIgniter’s development truly into the open and assigned lieutenants from the community to help manage the repository.  Yet, we are not a services company so funding models that would allow us to dedicate significant resources to CodeIgniter, such as those used by Linux, Mozilla, Zend, Magento, etc., would not work without radically changing our focus. As a result, we have always been unable to be involved to the degree we feel the project owner should. That means this project is not the right fit for EllisLab. So beginning today we are officially seeking a new home for CodeIgniter.

We love CodeIgniter and want to see it continue to thrive. PHP as a language is maturing, and CodeIgniter deserves to take advantage of its new stabilized features. CodeIgniter’s community deserves input and interaction with the people minding the gate. CodeIgniter will be best served by someone with a focused vision for it, along with the resources to achieve that vision. It needs someone to skillfully utilize the brand’s immense traffic, and direct the thousands of voices of input towards common goals. EllisLab can’t provide those things without adopting a fundamentally different business model or taking attention away from our primary flywheel. CodeIgniter deserves to be someone’s primary flywheel.

So with mixed feelings of both joy and sadness, we are seeking a new home for CodeIgniter. Our objective is to do what is best for the framework and its community, so we are willing to consider a variety of acquisition scenarios. If you are interested, we’d like to hear how you envision the framework evolving under your stewardship, and what qualifications you or your organization would bring to CodeIgniter. If this describes you and you have a plan and the resources to carry this wonderful framework into the future, please .(JavaScript must be enabled to view this email address).

Comments & Feedback

  1. Just put it to rest peacefully! It’s lived a good life.

    Picture of Developer13


  2. So this means CI 3 is dead now?

    Picture of bcorcoran


  3. Why is ExpressionEngine only mentioned once in this post given CodeIgniter is “deployed as the underpinning of every ExpressionEngine installation”?

    Does this mean ExpressionEngine will be rewritten in a proprietary framework or another open source framework?

    Picture of Leevi Graham

    Leevi Graham

  4. Have you considered packaging the Forum and Wiki modules along with CodeIgniter?  Would love to see more EL resources directed toward core EE!

    Picture of Ben Parizek

    Ben Parizek

  5. @Leevi - it doesn’t have any code implications for ExpressionEngine, as we have been maintaining that separately from the public version of CodeIgniter for some time. It is also not a signal of a full application rewrite like what happened between versions 1 and 2, so no worries there.

    Picture of Derek Jones

    Derek Jones

  6. I agree with Leevi Graham’s comment.. EE3 will be rewritten without CI… Not good… Probably a new Framework that we will need to learn from scratch… Feelings on both sides…

    Picture of SirCharles


  7. This is actually a positive step for ExpressionEngine. We’ve been developing CodeIgniter very slowly, because as a commercial software company, it has never quite fit into our business model. Some people might not recall, but I wrote CodeIgniter initially as a personal project. I didn’t even tell anyone about it until it was ready to release, so it was not an official product of EllisLab at the beginning. It was more of a “here’s a fun tool I wrote” type app. But as it took on a life of its own we decided to manage it and back-port ExpressionEngine onto it, mostly so we didn’t have to maintain two sets of code. Having never managed an open source product, however, we had no idea what that really entailed. And we didn’t realize that unless you are a true services company, which we are not, it’s very difficult to give an open source product the full focus that it deserves.

    Truly, the only impact this will have on ExpressionEngine is a positive one, as we will be able to devote even more focus to it. And there will absolutely be no rewrite on another framework. Holy cow. That would be insane. As Derek noted, we love CodeIgniter, so we’re doing this so that it can flourish under the development of someone who can push it forward more aggressively than we can, making an already great framework spectacularly better, and giving the CodeIgniter community the tools they need to keep being relevant.

    Picture of Rick Ellis

    Rick Ellis

  8. Thanks Rick, but for a lot of us, we don’t really care about ExpressionEngine at all… we care about CodeIgniter. Obviously EE will continue to grow, but now CodeIgniter will likely languish. What benefit does anyone else have to gain by taking up this now-orphaned project?

    I’m also not sure how this is any good for you guys either, because it means I (and many others) have no reason to pay attention to EllisLabs anymore—why would I/we? None of the work on EE’s version of CI will get backported to the CI project…

    I’d like to understand, but I don’t.

    Picture of bcorcoran


  9. “What benefit does anyone else have to gain by taking up this now-orphaned project”

    We just released a new version of CodeIgniter, so we’ll continue to manage it until the right situation emerges. To say it’s orphaned is not accurate. But to answer your question, CodeIgniter is the most forked project at Github, which should give some indication of how many people are interested in developing it. Furthermore, the worldwide traffic CodeIgniter gets is massive. Someone with the right skillset should be able to leverage the brand and huge community into a successful enterprise.

    Picture of Rick Ellis

    Rick Ellis

  10. “CodeIgniter is the most forked project at Github…”

    I see 2,569 forks. There are many other projects with more than that - or am I missing something?

    Picture of Developer13


  11. @Developer13 - the article says “It has the highest number of forks of any PHP project at GitHub of all time.” Of any PHP projects being key here.

    Picture of Derek Jones

    Derek Jones

  12. I also think it’s a good time to put CI to rest. I guess the devloper came to terms that turning it into a modern framework would require a LOT of rewriting at this point. Independant of the new owner I don’t think there’s going to be much new coming to CI anymore.

    Fortunately there are a lot similar frameworks to switch to, one of them is certainly Kohana ( http://forum.kohanaframework.org ) and PHPixie (http://phpixie.com)

    Both of them have a very similar approach that CI had, while also featuring full-functional ORM. PHPixie is the most modern of the alternatives, it uses namespaces, avoids static methods and properties and is fully unit-tested.

    Though I enjoyed CI, and just finished my last big project using it recently, I must say that both Kohana and PHPixie feel much more fresh and maintained.

    Picture of puzzled


  13. @Derek - Actually I was questioning Rick’s phrasing (a literal quote) and not the article, but I’ll assume that’s what he meant since that makes much more sense smile

    Picture of Developer13


  14. I’m sure this was a hard decision to come to, but it is the right one for the future of the framework. I would, however like to pose an alternative. Instead of looking for a new “owner” of open-source software, I think it would be fantastic if you’d consider working with the community to setup a self-sustaining 501(c)(3) not-for-profit which would run and operate the project. This way, EllisLab can help in the transition, and be confident the project will be run with integrity and a vision Rick would be proud of.

    ps. hi Jones and Rick!

    Picture of Greg Aker

    Greg Aker

  15. I’m sorry to hear this news and I’m not entirely sure if it’s a good decision.  Never the less, at this point in time I suppose I ought to express my thanks to Ellislab for creating CodeIgniter and for bringing it to the web development community.  CodeIgniter has been good to me and I’ve earned a good living from building CodeIgniter websites.  There is no doubt that the brand of CodeIgniter still has massive value.  Anyone who takes up that brand gets instant access to tens of thousands - possibly even hundreds of thousands - of developers, as well as a large assortment of companies who depend on CodeIgniter.  So, good luck Ellislab and I hope you don’t get bullied into giving it away for free.  Thank you! - DC

    Picture of Davcon


  16. Very sad to hear this news, I have a lot of work on the project website or web application using CodeIgniter, where I feel the ease in learning the concept of this framework, and a powerful one, so sad for me. I represent the country of Indonesia to thank you for founding this framework. Hopefully this framework lover get good news. Note: if necessary expenses for the operation, may be made ​​a donation link each country, but be know how to do it

    Picture of anyamanggar


  17. CI is great. Keep it alive.

    Picture of weblover


  18. This is great news!

    Especially for us who have a large web application that can not just switch to a new framework. By the way, I’m really happy for CodeIgniter in its current form. I do not need all the new features in php. There are many - particularly young people - who believe that the latest version of something is always the best. When they get older they will often learn that it is not always true grin

    Let us hope that a large company can see the idea to bring CodeIgniter on.

    Picture of Anders1975


  19. I actually think this could have a positive effect on Codeigniter’s future, providing whoever takes it over doesn’t make a hash of it.

    Lately CI bug fixes have been slow to implement so we might see progress kick started again and CI continuing to punch hard in the battle of the frameworks.

    I’ll be watching with interest

    Picture of Ckirk


  20. I think that the current status of CodeIgniter is mature enough for EllisLab considering keeping it; after all, what new fancy functionality is needed in CodeIgniter?

    The fact that EllisLab maintains CodeIgniter would produce the side effect of making the company’s name known to a even bigger crowd, and that (in some way) might be considered a benefit in itself.

    The current situation of CodeIgniter allows developers to use it in a immense realm of scenarios (even for VoIP applications). Personally, I think you should reconsider staying with it.

    Picture of J.  Pavel Espinal

    J. Pavel Espinal

  21. I would have never believed it if I didn’t read it here.

    Will CI 3.0 still be released by Ellislab?

    Picture of Thorpe Obazee

    Thorpe Obazee

  22. Despite of it weakness, I still like CodeIgniter. CodeIgniter is my first PHP framework. I like it’s simplicity. Compared to some brand-new-technology-framework, CodeIgniter is still the easiest to learn, and easiest to master.

    I understand the situation of ellislab. It must be hard to maintain several products with different natures. So their decision is probably the best.
    Thank you for everything.

    Picture of goFrendiAsgard


  23. Very sad

    Picture of Siavashmusic


  24. It may be sad for EllisLab but not for us developers.

    “Oracle/Sun/whatever, the most recent change where everyone screamed and cried about the death of MySQL which didn’t happen.” -Phil Sturgeon Founder of PyroCMS

    I could not agree more. If anything this will improve the speed of development for CodeIgniter! I’m excited and hopeful that CI will find a new and improved home.

    Picture of henrymb67


  25. Wow, I’d love to see the pros/cons balance sheet on this one!

    I’m quickly going through all of them in my own mind, from an outsider point of view at least and I find it difficult to understand if this was a good decision or not. I realize sometimes reality makes the decisions for us and that may have been the case in this instance though, I have to assume this was difficult getting to the point of this blog post either way.

    For what ever it’s worth, I think making a decision one way or another vs not doing anything at all is usually the better decision so, good on ya, thanks and good luck going forward!

    Picture of Natetronn


  26. All I can say is “CodeIgniter is The Best !!!”
    Let’s pray it will be on good hands.

    Picture of whygod


  27. CodeIgniter is a beloved friend of mine… but I understand the need to: focus for a company.

    Look what Google with with Reader on a larger scale.

    In the light of that, MojoMotor can probably go too.

    Picture of Limey


  28. Btw, Rick, thank you for all the work for this free product!

    Whatever happens with CI, I’m very grateful for the ride.



    Picture of Limey


  29. Will the CI brand, logo, and any trademark be sold to a third party, or gifted?

    Picture of SneakyDave


  30. Well the feelings are mixed!
    On one hand worried how this will advance and on the other hand less worried (than before) of the future of the framework.

    I hope the transition to the new owner will be after carefull consideration.

    My suggestion for now, agree with the new owner that there will be a commitee that will decide about the future of the framework along with key/core developers from EllisLab for the first couple of years at least.
    This will ensure a proper transition because we must admit, you guys no better than anyone else CI!!!

    I feel that I would like to thank you for all these years of your efforts and for producing such a fine framework.

    Thank you,

    George Pasparakis aka David Oster, B.Sc.(Hons), Ph.D., MIET

    P.S. Which version will you pass on? The latest stable one 2.1.4?

    Picture of davidoster


  31. Thanks rick for this framwork for free to developers. For all remain positive, do not let the negative ingested issues of great people who are jealous of this framework. Thanks once again .. can’t wait for the news

    Picture of anyamanggar


  32. Thanks is the first reaction here.

    I can’t say I’m shocked, paying attention to the [small] progress over the last year or so, but hey, the community owes a debt of gratitude to EllisLab over the past 7 years for shepherding so many developers to a better way of developing web applications. Plenty of folks have complained about the lack of updates, limited features, etc. and we can move to Laravel or one of the 20+ PHP frameworks out there if we like.  Rick + co are doing the right thing by giving the framework what they think is the best chance for success.

    3.0dev is pretty solid. Seeing 2.1.4 made many smile.  Some just #######. What can you do?  As Dr. Seuss says, Don’t cry because it’s over, smile because it happened.  And it’s not even over…

    Thanks EllisLab for a framework I could get my head around that brought me years of great projects.

    Picture of Michael Layne

    Michael Layne

  33. Thanks for your hard work and giving us the worlds most popular PHP framework.

    To me, Codeigniter is part of Ellislab as much as Expression Engine is. It strengthens the Ellislab brand massively and i wonder how much affect passing Codeiginter on will have on Expression Engine from a sales and marketing point of view.

    I find it hard to understand this move from a business point of view, but then only you guy’s know the true picture.

    We’ll all be eager to watch this one.

    Picture of Luke Clifton

    Luke Clifton

  34. For me, CodeIgniter was always a framework built by a company that I had trusted to build solid products. It was never a shiny toy. It was a solid tool for getting things done. Why not just offer the framework in some form, bring it back behind closed doors and offer it for free download? Given the choice between a community project and the less sexy framework which ExpressionEngine runs on, I would rather take the Ellislab product.

    This announcement makes total sense to me though. It never did make sense to me to open CodeIgniter to community development. It seemed like once that happened then certainly it would diverge from what would go into ExpressionEngine (I assume it did, I never paid much attention.) I liked CodeIgniter just fine back in the day when it moved at its own pace and people complained about how slowly it was being developed (and whatever else they had to complain about.)

    Picture of John Fuller

    John Fuller

  35. Yes, it was a great 7 years (7 year itch?).

    The 3-dev release is probably something that will be left to the new owner. It would also be interesting to see if CI has the potential to become a community project. A lot of the original supporters and “names” in the community have left CI-development.

    Picture of GDmac - expocom

    GDmac - expocom

  36. Bonjour,
    I do not know if I should worry or happy ones, my wish is that codeigniter opens to the community as does zend or symphony….

    Picture of lunick


  37. ####!!!!!!!!!!, and version ci 3? This could have decided much earlier. And do not be waitin an improvement. For? for nothing.

    Picture of chiqui3d


  38. With many others, I would like to see 3.0 released but I will continue to use CodeIgniter. It’s very stable and mature at 2.1.3. People screaming about new features are probably not the people who should be using CodeIgniter. I use it because it’s light, and stays out of my way… I don’t need an ORM or Auth library built into it… Not all my stuff I build on CodeIgniter uses databases or even needs authentication, so why have all that stuff in the core? Want it, there’s plenty of libraries out there that can accomplish this and fit into CodeIgniter easily…

    I use CodeIgniter because it’s backwards compatible… Sure bleeding edge PHP is cool, and I like to play with it, but the reality is my clients are sometimes still on PHP 5.2, why would I want to distant myself from them, because my framework doesn’t support a perfectly fine version of PHP anymore?

    Picture of Killswitch


  39. I appreciate all the kind comments. This was not a flippant or easy decision, so I’m grateful for the support.

    Picture of Rick Ellis

    Rick Ellis

  40. Sad to see it go :(. However I’ve sent an email to the contact us email listed on this post. I am a professional developer with 8+ years experience hoping I could take it over and advance it by making it supported by latest php versions, making everything much easier for the beginner, expanding the librarys by adding huge shopping librarys, forums, blogs, etc. in addition to some more backend things, making the system completely stable and optimized to be fast & efficient without losing any functionality.

    Picture of cgbox


  41. I have a very strong interest in the future Code Igniter and would like to contribute or at least stay abreast of it’s future. I’d especially like to here from Derek Jones, Rick Ellis, cgbox and Greg Aker about planning a formal way to keep CI moving forward if one hasn’t been determined already or if I can provide additional help.

    My email address is .(JavaScript must be enabled to view this email address)

    I can explain my reasons better in the appropriate forum for CI’s continued success as I gather this thread is not really that conversation.

    Picture of bapfu


  42. Hello bapfu, I’ve sent you an email regarding your question.

    Picture of cgbox


  43. Hi cgbox, I didn’t get it (checked spam.) Please try again or hit me up on twitter (@bap)!

    Picture of bapfu


  44. bapfu: I’ve went ahead and resent it (from: admin @ [cgbox].tk )

    Picture of cgbox


  45. My initial thoughts and feelings about this change where negative. However, after a bit of thinking it makes perfect sense. I just hope that a well funded, forward thinking company comes into play, picks up this great product and gives it the proper attention it deserves.

    Picture of Ric


  46. (cont.) I applaud EllisLabs for having the courage to transition the product rather than kill it or leave it in a state of limbo. I really do. As a customer I sense Ellislabs is moving quickly in a good direction with a greater sense of purpose, especially after the whole Pixel & Tonic debacle. I’m really looking forward to V2.7 especially now that the kid’s gloves are off in terms of developing functionality irrespective of what third party partners may have built or not. I sense the best is yet to come from Rick and Co.

    Picture of Ric


  47. Have you tried already with some company?
    google is a good option .... xd
    I guess not, because otherwise the news would have been direct.
    I also agradeze your great work in the last years.
    Although the last year has been terrible, see how other frameworks are updated without stopping, and codeigniter are vat below, nothing.

    Picture of chiqui3d


  48. That if I will continue working with codeigniter, is still the best. Of course, if in a year does not advance. We will have to look laravel. But yeah, codeigniter up!

    Picture of chiqui3d


  49. First of all I hope CI never dies.
    Second Thanks allot Ellislab for your unlimited support during the 7 past years to make CI the most wanted php framework ever, in my Company it’s been one one of the necessary skill to hire someone, and that’s reflects how successful it is.

    for me I can fully understand why you want to sacrifice of CI,this blog: http://ellislab.com/blog/entry/competition-ethics-and-add-ons can tell why.
    you need to focus on your business plan and growth for ExpressionEngine.

    for whom has the chance to see the Competing products such as (Craft) will feel EE looks much older, slower, messy, Minus, heavier and retro In comparison with them

    I’ve been a good customer for Ellislab and CI master developer, so I won’t be selfish.
    Ellislab has the right to focus on their commercial product, rescue their business and prepare for the Competition.

    I support your decision, but be selective for whom will be next owner for this brand smile

    Picture of AkwadNet


  50. Let’s hope CodeIgniter falls into the right hands and gives this splendid framework a new lease on life. I’ve been frustrated with the progress of v3 over the last year, so this may be a blessing in disguise.

    Picture of ci_user


  51. Since using CI 3.0 was never an option for me, due to the license, I started working to convert all of the CI 2.1.X classes to stand-alone classes, for use in Slim and Laravel. I’m mainly using Slim, and Have about 50% of the classes converted and tested. It’s pretty sweet, because everything is autoloading, and I’ve cut out a lot of the bloated crap I never used or didn’t think I’d ever use. The result is a smoking fast framework and no more $this-> $this-> $this->.

    Picture of Alucemet


  52. This post has urged me to move forward.

    For long years I’ve been using CodeIgniter and was very sceptical about new things that happened in PHP world. I though namespaces were a bad idea and traits even worse. I also though that Composer was only good in theory and continued developing just like I always was.

    But after reading this I though that old things have one huge problem: they inevitably die, so if you want to stay productive you need to keep up with the times.I also thought that were I to start my carrer a month ago would I have chosen CI? Probably not, as features of other frameworks would sound more appealing to me.

    So why did I stay with CI for that long? Probably because I was used to it and am too lazy to lear new things if I can work with old ones.

    I decided to try http://phpixie.com and http://kohanaframework.org/ suggested in a comment above and I’m getting largely positive experiences, they are both fairly similar to what I’ve got used with CI and are far better and simpler than symfony for my projects.  The only real difference is that arent backed by a company like CI was. But maybe that’s a good thing? Maybe focusing on building a community instead of licensing is a better approach for longevity? We’ll just have to wait and see.

    Picture of phpgeekboy


  53. phpgeekboy: join date - 07/14/2013
    @puzzled Why you registered another account? to write a similar comment about phpixie and kohana?)

    Picture of drake


  54. Very sad..

    I think that is one big mistake for EllisLab ..
    Many percentage from your “Positive popularity” comes from the CI and now you want just to clear your hands from it ?
    ExpressionEngine wouldn’t be what it is if there was no CI !
    Really strange decision!

    R.I.P CI :(

    Picture of sv3tli0


  55. Does this mean that you’ll have to ship a separate updated code documentation with every release of EE for us add-on developers to know what kind of build in core functions we can use?

    .... which is the case today with CI. You just go to the CI documentation to see what’s there and what’s not.

    Picture of esset


  56. OH NO!! please not let him die

    Picture of outlandermx


  57. @drake
    It’s because puzzled phpgeekboy wrote phpixie. Dubious I think.

    Picture of nick2013


  58. It makes sense. New ownership will inject life into a project that is hard to maintain without putting dedicated resources into it (which, when looking through a company profitability point of view, is tough to do - especially for a small company like EllisLab). I’m sure whoever takes over will be well-vetted and excited about a new direction while maintaining the things that differentiate CodeIgniter and make it what we all love.

    Thanks for all your hard work over the years! Here’s to 7 more years!

    Picture of redcore


  59. I´m not sure how I feel about this for this reasons.

    Its clear that Ellis Lab is a software company and want to focus on their core products that give them money. They don´t have resources to spend on maintain the open source project. So in this regard is positive.

    All Ellis Lab products are based on CI core. This is bad. Because if the new owner makes an awful job, like in security or bloated features, their own products will hurt. They are saying bye, bye to the core that is the mother of the commercial projects. Not sure how I feel about this.

    Rick mentioned “o that it can flourish under the development of someone who can push it forward more aggressively than we can, making an already great framework spectacularly better,”

    If this is true, its positive. But this depends on WHO will be the new owner or maintain the new product. Democracy in software usually does not work. It ends up with a bloated products that tries to do all things that shine under the sun, and does not do anything well, Jack of all trades, master of none.

    So if the new owner/s make a terrible job, its the end of CI and probably the end of EllisLab products, since they would need a full rewrite, probably even their end as a company since I assume must people use their products because its done on the same open source framework, it they where forked different projects, im sure must companies would not buy a proprietary web systems. Done that many times, and closed code is something most companies want to move away.

    On the other hand, if the new project ends on the right hands, that keep developing working, fast, clean, simple, secure and stable, this will be very positive. EllisLab can focus on their products. The new owner can focus on CI and keep it moving forwards. Everyone benefits. Not sure if EllisLab will be able to adapt there, maybe the new owner, develops it to fast or to slow and they cannot keep up.

    So all this speculation depends on WHO will maintain the code now. As a code, software or even company is just as good as the people that are behind them. So I don´t care to much about the decision. I would rather care on Who will be the new owner. If its going to be a huge IT company that has the resources, or its going to get rip off by some amateurs coders….

    So before everyone makes speculations I think we can´t know anything until we know who will be the new daddy of CI. Reputation of course will go to the new owner, and if they offer commercial products as well, it makes sense they will use CI for their own products creating actually competition to EllisLabs.

    Picture of Nibb


  60. On a side note, I read most forums online and most of them are saying RIP, so the decision alone is hurting it already. And I do agree that most of the popularity of EllisLab and probably customers comes from CI. I do agree with some commenter that EE and most of its products would not even be what they are today without it. Its the logic step for developers of companies to follow:
    Open code
    Open Framework
    Commercial product with support based on the previously.

    I think that a huge %, probably most of EllisLab customers came indirectly via CI. So what will happen if they lose their main core business advantage?

    This are interesting questions. For me personally im more worried about what will happen to EE.

    Picture of Nibb


  61. They are saying bye, bye to the core that is the mother of the commercial projects.

    Actually CodeIgniter was created from and would not exist were it not for ExpressionEngine, not the other way around. ExpressionEngine 2 brought the two together for the reasons Rick cited.

    For me personally im more worried about what will happen to EE.

    It should get you excited about what will happen to ExpressionEngine, as our growing team (we are currently hiring) will have even more focus on our flagship product. Our whole team is ecstatic at the opportunities in front of them.

    Picture of Derek Jones

    Derek Jones

You must be logged in to comment on this blog post