Building the new site
Setting up the new structure using VWCMS proves to be more complex than expected. Even translating the current homepage into VWCMS format is not as easy as expected. However, the kit comes with all documentation in the right format so there is a very god example on how things must be changed.
So I use that as the template, trying to transfer the existing homepage into VWCMS format – and, eventually, at least one of the downloaded templates. But it takes time to find out how it really works…. But taking little steps at a time, I get a good idea how the whole things works. It is q requirement to have a web display and a terminal session at hand, side by side…
Update
But that paid off, soon enough. By applying small changes to a file on the terminal, and immediately refresh the browser, the result can be viewed, and if changes are required, what and where is easily found.
Once the basic layout has been determined (I still need to do some style changes, but these are minimal), the next thing is to change and add content. But that was quite a different matter.
It took some digging why adding or modifying data didn’t really work suing the web-based editor; of course the the data can be added or modified directly in the file (it does have advantages not using a database!) but it should of course be possible to use the supplied editors. As it turned out: there is one file, _included.conf, that holds the [readonly] directive, and ;I placed the $$ADVISE$$ macro (that should show this) a bit out-of-sight, at the bottom….
One this directive was removed, it all worked. For the time being, I have left the documentation that Mark Daniel has written, available for reference.
We’ll get there, step by step. It won’t be very long before at least the home page of the site is renewed!
By the way: IE9 has trouble with the javascript-based editor in WordPress (at least, this version). But although the font is really small, it seems to work with the same editor in VWCMS….