Iāve used both cms and html/css hard coding.
Using a cms will get you up and running quickly. But, as soon as you want to do anything slightly out of the ordinary you will find yourself searching for add-ons and plug-ins - some of which are ten times more complicated to implement and understand than html/css. Also, if something goes wrong with your cms, without a background in html/css you will be totally lost - unless you can find someone who is willing to sort out your problems for free.
Using html/css will involve a steep learning curve and on-going learning as both html and css evolve. But, when you have mastered the basics, you will be able to sort out yourself many of the problems that you are bound to encounter. You will also find that you have more flexibility to make your website look and perform exactly how you want it to. However, you will need to spend a good deal of time and effort up front before you actually start creating your website.
Personally, I wouldnāt touch any cms with a dead flash stick. In the long run, I found them to be too much like āa solution dictating the original questionā, or, āthe tail wagging the dogā.
For instance, embedding a YouTube video into a raw html file is a simple copy and paste job - all done in 30 seconds.
Getting that same YouTube video into a cms can involve a major project. How do you decide which plug-in/add-on to use? Are they compatible with the other plug-ins/add-ons you are using? Do they actually work? Are they compatible with your cms version? Are they still supported by the author? Are they free? etc. etc. etc.
Unfortunately, I have worked for clients that have used Joomla, modx and Wordpress. Out of these, I prefer Wordpress as the best of a very poor bunch.
Having said all that, if youāre not really bothered the form your final website takes, how it performs its functions, and you are willing to abandon any feature or function that really isnāt suited to the underlying platform, then you might just possibly make a case for using a cmsā¦