CMS
Applications

WordPress, unless you have a specific reason not to. It has the largest plugin and theme ecosystem, automatic background updates for security releases, and the most developers who could pick your site up later. Choose Drupal or TYPO3 when the site has real editorial workflow, many contributors and strict permissions. Choose Craft CMS, ProcessWire or SilverStripe when the content is structured data rather than pages and a developer is doing the build. Choose Joomla if your team already knows Joomla, which is a better reason than it sounds.

b2evolution and PHP-Nuke, on the evidence of their own repositories, with Geeklog close behind. b2evolution released 7.2.5 in September 2022 and has committed nothing since. PHP-Nuke has had no real code change since 2022. Geeklog is a softer case: there are commits from 2026, but no tagged release since September 2022, so there is activity without a release schedule. All three still install and will still run, and anything you build on them is your own risk. If you already run one, plan a move rather than a rebuild in place, and map the URL redirects first.

Shared hosting runs both perfectly well for most sites. Drupal 11 needs PHP 8.3 or newer and TYPO3 14 supports PHP 8.2 through 8.5, and you select the PHP version per package in the My365i control panel. Move up to a managed cloud server when you have many concurrent editors, a large multilingual build, or you want Redis object caching, which is a Managed Cloud Servers feature rather than something available on the shared plans. StackCache is the caching layer on shared hosting and covers most sites comfortably.

Yes. Our hosting plans include SSH access and unlimited cron jobs, which is what Composer-driven platforms need for installs, updates and scheduled tasks. Craft and Winter both expect to be managed from the command line rather than through a web updater, so budget for somebody being comfortable there. Worth repeating: Craft Pro is a paid licence per project on top of your hosting, renewed yearly for updates, which is unusual in this category and catches people out at renewal time.

PHP memory exhaustion, nine times out of ten. A 12-megapixel phone photo is a few megabytes on disk but needs several hundred megabytes of memory to decode and resize, so the upload dies with a blank screen instead of an error message. After that it is cron not being configured, so scheduled posts never publish, and upload size limits blocking a plugin or theme install. All three are settings, and we set them at install rather than leaving you to discover them.

Yes, but expect to rebuild the templates rather than import them. Hosted builders export content unevenly and never export their design, so what really transfers is text, images and a URL list you can redirect from. Moving between self-hosted hosts is a different job: the Migration Centre in your control panel copies files, databases and mailboxes from most Linux hosts, you run it yourself as often as you like, there is no file size limit and it costs nothing. Builder to CMS is a project. Host to host is an afternoon.