Wait, no one even mentioned TYPO3?
It's weird, complicated and often comically redundant but nothing makes it as easy to tailor to your clients needs without ever touching coding.
Also one word: "typoscript" - because what the world needs are more scripting languages that write like visual basic and original basic had a horribly disfigured kid with mental problems. But it gets the work done and no mistake.
I made a living off of this for years, it just looks corporate and sells like hot potatoes. Probably something more for the european crowd though.
My favorite feature: Handles multiple domains and multiple languages fantastically, version level shared installation.
It depends on how you installed your site. Is it composer installation or did you download the files from the typo3.org? If composer based - did you use helhum's secure installation?
But most importantly - why would you want to access index.php? Do you want to change the template? If so - you are not looking for index.php, you are looking for a template defined in sitepackage. Look inside sitepackage/Resources/Private/Templates...
I'm cooperating for around 6 years with German-language companies (Germany, Netherland, Liechtenstein) and they were very often using TYPO3 CMS (PHP) and in second place WordPress (PHP) (of course).
I personally don't like TYPO3 but they did :)
I would use Drupal since it has everything you need. You will need to learn a lot. However, the documentation is much more complete, at least in English, than things like Typo3 and there are tons of free extensions. I do not think Wordpress is a great option but I do not have tremendous experience with Wordpress either. Joomla seems too simplistic for your purposes here. I would put it between Drupal and Typo3 though if you want something truly capable of a huge website with very little effort. I will say the Typo3 documentation has improved a lot since I last attempted to use it and a lot of big companies do use it but I think Drupal is a bit simpler to put into use for a beginner. Some things I never could figure out in Typo3 but I had working in Drupal within a few hours.
Use TYPO3.
Designed as an Enterprise CMS.
Very popular in German-speaking countries, not least because of the stability and the possibility of scaling. Decoupled frontend and structured content out-of-the-box.
You shouldn't need to. The export module should take care of that as well AFAIK. But the best place to get help is probably slack - https://typo3.org/community/meet/how-to-use-slack-in-the-typo3-community/
They changed to a more agile development model and publish a new version every 1,5 to 2 years, have come up with a comprehensive norm how extensions are build and have streamlined about everything.
That said, it's still a monster. It's so feature heavy that most people won't need it and is geared towards multidomain corporate stuff (that's why we use it) with granular rights management and many different user roles working in tandem. Feeding content into staging-areas, version-control and having supervisors publish the content editors create.
Still we use it for the tiny stuff like onepagers for a restaurant-ad to the main websites of the biggest players in our corporate group.
Introducing TYPO3 into the group I have managed to reduce developer workload from managing ~50 seperate Joomla! installs with all kind of differing extensions on different versions into managing 2 TYPO3 installs (Dev and Production) with a single set of extensions that can be used on every page I damn well please.
Instead of having 20 people a day call me to change something on some website, because nobody ever bothered to even try and learn to do something in Joomla, they have now been given editor accounts they simply cannot fuck anything up with. They make their changes, then push it into review where their individual bosses can check how the changes would look and then publish them.
It might just be the change in corporate culture this has made necessary and that I pushed through, but damn it feels good to do actual development work again and not being a glorified secretary hunting down typos on our 50+ websites.
It's nothing I would ever sell to a client, who just needs a wordpress with a template, though.
Yes you could do that.
Do you want to test all the versions? Or just "current" i.e. 7
?
user@host $ curl -s https://typo3.org/download/ | grep -P -o 'https://get.typo3.org/\K[^"/]+(?=")' 7.6.16 8.6.1 6.2.30
You could use -m 1
like the previous grep
command if you only want the first result i.e. "current"
Well, a good start might be the TYPO3 books, like this one: https://typo3.org/news/article/book-modern-extension-development-for-typo3-cms-with-extbase-fluid/
This should get you covered on all the recently developed extensions as well as most of the modern core (version 6.2). Also good reading is the frontend rendering process explained here: https://buzz.typo3.org/uploads/media/TYPO3_Frontend_Rendering_Process_v1.5.pdf
However I have been mostly developing TYPO3 websites, so I do not know what kind of things you are referring to. (Optimalization or refactoring or adding small features?)