{"id":516,"date":"2023-06-09T09:37:58","date_gmt":"2023-06-09T09:37:58","guid":{"rendered":"https:\/\/www.lasselaursen.com\/?p=516"},"modified":"2023-11-10T07:32:25","modified_gmt":"2023-11-10T07:32:25","slug":"switching-to-wordpress-felt-like-a-visit-to-the-ferengi-homeworld","status":"publish","type":"post","link":"https:\/\/www.lasselaursen.com\/post\/switching-to-wordpress-felt-like-a-visit-to-the-ferengi-homeworld\/","title":{"rendered":"Switching to WordPress felt like a visit to the Ferengi homeworld"},"content":{"rendered":"\n
\n

This post is the first in a three-part series about migrating from a self-built PHP-based Laravel backend to a managed WordPress backend, in an attempt to minimize on-going maintenance and custom code.<\/p>\n\n\n\n

Part two <\/strong>will detail what motivated the switch<\/a>, and the final part <\/strong>of the trilogy will round out what recommendations I’d give to others in my place<\/a>.<\/p>\n<\/div>\n\n\n\n

Welcome to Ferenginar. Need to use the elevator to the 40th floor? That’ll be 7 strips of latinum. Need the front-desk to reach out to the person you’re here to see? One strip of latinum. Seating while you wait? 3 Strips. Standing, is just one.<\/p>\n\n\n\n

This largely sums up a significant part of my initial experience with WordPress. Let me emphasize that people deserve to get paid. Just because something is free doesn’t mean it didn’t take effort to make. This acknowledgement aside, I was still surprised at the number of times that a solution to some design problem I encountered in WordPress had a fee attached to it, including, but not limited to:<\/p>\n\n\n\n