Considering Java CMS
The first step of getting over Wordpress is finding a CMS that is Java-based, so "templating" will be a bit easier for me.I searched and learned all Java-based CMS around but threw them all together because apart from the learning curve that I need to spend time on, they have too much features that I don't think I need yet.These CMS tools, were made because somebody got tired of editing html/xml files and/or copying media files manually. Somebody felt the need for automation because that somebody got tired. I want to feel that first before I go to the CMS route. I want to be that "somebody" first! I know someday it will change but I'm feeling it right this moment so let me be.Also, I'm pretty sure a non-programmer-person in some company wanted to edit the content without learning all these markup or these other programming languages. It made me remember those ads of sorts about these CMSs who tells you that "You can do this thingy without touching code!". Unfortunately for me, at this moment, I want to touch code! I know it's pretty sadistic, but it makes me appreciate the tool more.CMS truly saves time. Let me speak about Magnolia CMS for now, because it's the only Java CMS that I've tinkered on. The biggest reason that made me stop pursuing it is that I can develop a full-stack application faster than studying the plumbing and workings of Magnolia CMS. I know it will get better when you get the hang of it but then it always depends on the need. And my need is to get this site out there as soon as possible (I've waited 10 years already to remove my "i-can't-do-this-blocker"). I can't wait another minute more. Like all applications known to men, it doesn't have to be perfect on the first deploy. There is always room for improvement (my improvements actually are listed on my Agile board). It's going to be a fun crossing them off, and I want to do it while I still can.I worry that when the time comes when I feel lazy on doing all these posts manually and finally open up again on a CMS, the migration is going to be a pain! I'm sure it will be. So I listed out all the features and improvements that I am going to do so that my migration will not be as bad. More on those in a separate post/s.