![]() Tumblr also turned out to be a horrible choice for collective blogging with its primitive user management, non-existing archives, and lack of control over front-end and performance. This decision let us reduce maintenance time and improve stability, but brought its own problems - any change to a marketing website required a developer, and if any of our apps experienced an interrupted service its public website would be unavailable too, so we wouldn’t be able to direct users to a status page or a support website. We built them as parts of our product apps and created blogs at Tumblr (which wasn’t a strange choice in 2009). We aren’t in the business of building WordPress websites and as a small team have to focus on our apps, so it was clear that we didn’t want to use it again on our products websites. ![]() As you can imagine without deep WordPress knowledge we were subjected to all of the problems it is usually blamed for - lack of security, comments spam, breaking updates, etc. In the end of 2009 we redesigned it again, while staying at the same WordPress installation - this design stayed with us for over 5 years. Nobody in our team really knew WordPress or was willing to learn it, so we outsourced its configuration and setup. 2 years later we redesigned both our website and blog and migrated them to a self-hosted WordPress installation. A year after I joined Wildbit in 2004 we launched a blog called Tidbit (see what we did there?) at then-popular service Typepad. To see problems with our previous setup and better understand our priorities and choices, we need to go back in time and explain how things turned the way they did. Short history of marketing websites at Wildbit ![]() This massive project isn’t completely over yet, but enough time passed both to confirm that we made a right choice and to see some of its issues. Within a few months we researched, picked, and migrated to a single CMS moved marketing websites to a single hosting platform from multiple scattered services and created a library of modules that is reused on all of them. As the team had grown, publishing became a nightmare - nobody really knew how to access or update any specific page or a part of a website. A little over a year ago, we had 4 marketing websites built with 4 different frameworks or CMSs, and it was a mess. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |