I’ll just get this out of the way. We’ve seen Mika Epstein’s excellent WordCamp talk, “Don’t Use Multisite“. Despite her admirable, best efforts, we’re using it anyway.
To multisite or to not. This is something I have contemplated many times over the last six months as I have been working out our infrastructure. When the project was new, we just assumed it would be a massive multisite network with many, many sites within it. As the project became more clear and we learned more about WordPress, that assumption was challenged.
Continue reading “Why we’re using multisite and multi-network”
There was a tempting dirty joke setup on Twitter the other day. Someone said something that I could have easily turned into a sex joke, or at least innuendo. I let it go by. This was my work-related Twitter account. The fact that I even thought about it was interesting to me.
Back in the heyday of the alt.music.chapel-hill newsgroup, if someone barged in and started berating people (which happened), a regular on the newsgroup would gently explain to them that they’d barged into a conversation, like at a party. It was as if they’d come to a party (and they were welcome!), but then behaved quite rudely, yelling at people who were trying to have a good time.
Continue reading “On letting the dirty jokes go by.”
In which cards are sorted.
I have been going on a bit about card sorting on Twitter. Really, what is the big deal about sorting cards?
An unnatural position.
Our intranet is organized into departmental silos, for the most part. To organize content according to the way an employee would logically look for it is a mark of organizational maturity. It’s not a natural way for a large organization to arrange the content, although it is probably best for the employees. After nearly 18 years working on our intranet I feel as if we are finally being given the chance to fix it.
Continue reading “The sorting of cards”
In which our heroine establishes the process for setting up developer playpens.
Where I work, we intranet devs have playpens that are served by the same Apache servers that serve the rest of our intranet. They are set up by our webmasters, they use the same network and file system environment as the rest of the intranet, and, importantly, they use the same authentication as our intranet. For us this is a better dev environment than standing up Apache, MySQL, and WordPress locally on our desktops.
I wanted to give my team a process that made it easy and safe to delete their entire playpen and then re-install and configure WordPress quickly.
Continue reading “No one’s second WordPress project should be this complicated, Part 2”