Where it comes to Enterprise-Level clients, your definition of them will differ from mine, most likely. For the last year I’ve been dealing with some Schools and getting WordPress up and going within their environment. I’ve been a part of a large migration project for moving sites from ModX to WordPress. It’s been a tough project, it’s been challenging but we’re getting it done. The light is at the end of the tunnel.
So what makes a client an “enterprise-level” client? This is hard and there’s not one conclusive answer. However, I can tell you what I think qualifies:
- An organization that has more than a few units/teams/departments that serve different functions and business units (HR, Accounting, Admissions, Tech Support etc) outside of just making money
- An organization that has more than one line of business to support their growth
- An organization that uses many tools that tend to accomplish the same functions. Work with me here, but an Enterprise will often have different teams using different tools to accomplish the same thing. We have people Using P2 blogs, Google Sites and internal Wikis in addition to effing Sharepoint (I hate you, Sharepoint).
- You serve thousands of customers daily, hourly, to the minute and beyond
Notice I didn’t mention anything about ‘volume’ of business as it relates to how much a company earns? That doesn’t matter, in my opinion. The complexity of the systems and infrastructure is what matters most, I believe. Karim Marucci over at Velo Media works with many Enterprise level accounts and his experience and opinion differ greatly from my own, I’m sure. The Enterprise I work with is likely rather small comparatively speaking. And that’s fine, but it’s no less complex and requires no less consideration to “get it right.”
How is Working with WordPress in Enterprise Different?
Fucksocks! It’s really different. It requires lots of planning, lots of testing and lots of cussing…
Shit for you to think about:
- You will have to worry about content admins, you will have to worry about site admins and how they interact with the site.
- Your end-users will differ greatly.
- Will they use WordPress’s native login?
- Will they Require LDAP?
- Will you be connecting with external Web Services to pull data into your WordPress site?
- Can WordPress really DO THAT thing that you’re being asked about?
- How will your choices affect the future-proofing of your site?
- Should you use Multisite?
- How thoroughly will you test?
- What kind of resources are available to you?
- What will your development/staging/testing/production environment work?
- How will you interact with other developers on the project?
And this isn’t even have of the shit you have to think about… Sorry about all the cussing folks, I’m just really hyped up on caffeine and peyote… Fuck.
WordPress for Enterprise is Like Playing Life on Difficulty “Hard.”
It just is, people. There’s a lot of moving parts and a lot to think about. But let me tell you something: You’re going to fuck up. Your early fuckups will inform your wisdom down the line. Fuck up often, just try not to do it in production.
That said, the past year has taught me that WordPress is more than ready and more than capable for Enterprise and I’m really excited to see where it all goes from here.
I plan to write some bits and bobs about my experience with Enterprise level WordPress and share what I’ve learned and failed at…