A first step in any migration is to clean up your entry data. That doesn’t change when moving from WordPress to ImpressCMS.
Cleaning up your content can be done in several ways : removing old or no longer relevant posts (news items get old soon, and Google doesnt like stale news items), looking into content types that perhaps no longer need to be on the new site, and cleanng up your tags and menu structures.
It depends mainly on your content, so it is difficult to automate this step. However, if done correctly at the beginning of a migration, this step can make the difference between success and failure in the end.
One of the big sayings in open source is to ‘eat your own dogfood’, meaning that you need to use the tools you develop also yourself on a daily basis.
It’s the only way you can get a good idea of the strengths and weaknesses of your solution, by putting you in the position of the end-user.
I have been a sinner in that regard, by using WordPress for my personal blog instead of my own project ImpressCMS. That is something I intend to set straight in the near future by migrating from WordPress to ImpressCMS, and documenting the process step by step.
When attending a lunch seminar yesterday there was a very interesting short discussion about thhe use of WYSIWYG editors in CMS-powered websites. The whole discussion was about the amount of options and functionalities you can allow your site editors, keeping into account that your layout nowadays has to adapt itself to a multitude of different screen sizes and orientations.
This is a discussion we need to have in ImpressCMS, as we currently allow as much as possible to the editor. By doing that, we risk breaking the layout of the theme simply by entering content, and that shouldn’t be allowed. Read the blog, and add your comments at the ImpressCMS Community site.
ImpressCMS introduced a AJAX-based redirect system in series 1.2, which makes your site much quicker to work with. By using this redirect system, notifications and confirmation messages (E.g. ‘Thank you for logging in’) don’t show on a new page any more, but they are presented to the user on a text bubble that is loaded dynamically while the user remains on the same page.
Currently, not that many themes are created that provide this, and you need to explicitly enable it before the functionality becomes available. I’ll explain here the two simple steps you in adding this to your site.
With ImpressCMS 1.3 RC2 planned for this week or the next, things are also being worked out on our first ImpressCMS Developer Challenge. This is a big deal for us, both because this is the first contest we organise, and also because it should give us quite a bit of visibility in communities where we weren’t present until now.
On such occasions, it’s a good idea to inspire yourself on similar contests. Let’s not re-invent the wheel. During my quest for coding competitions, I came accross one that was of particular interest to me : the PHP on Azure contest. Two reasons : it’s a PHP coding contest, and it was organized in my region (Belgium).
I contacted the PHPBenelux organisation, and they agreed to assist in making the ImpressCMS Developer Challenge a big success! Thanks guys.
After getting increasingly dissatisfied with the service from Codesion, ImpressCMS decided to switch to another provider. We had few requirements, and so we started searching for a solution based upon those:
free or affordable for our budgets
We also thought of the possibility of doing the hosting ourselves, but that would mean an investment of time and effort, which would be unavailable for other tasks. Overall, we thought it was best to let specialized service providers handle that kind of non-core activity. Lees verder ImpressCMS Trac migration to Sourceforge→
Recently, jQuery 1.4 was released, with a maintenance release 1.4.2 a few days ago. In a move comparable to what we are doing with ImpressCMS release 1.3, the jQuery developers chose the jQuery 1.4 release to be a release focused on speed and cleanup of the codebase. Mostly, just cleaning up the codebase results in quite some speed advancements, so those two efforts are frequently combined.