A yorkshire based web development company have explained how they added automated html validation to their test suites.
The League have written a post on their typical RadiantCMS setup, including any extensions they use as standard. Also the web development company have explained how they have made their workflow process as simple as possible.
I recently finished working on a project at the web development company I work at which involved creating a PDF generation plugin for a CMS.
An interesting article by my web development company on how to get the most out of CSS frameworks without the need to sacrifice your principles of semantic markup and css.
I’ve had a major case of developers block on this project. The reason for this is that I have been struggling with the best way of handling the front end template management.
After spending some time going around in circles I decided the best way to get past these blocks was to try out a few other CMS systems to see how they handled such issues. This has turned out to be a really useful exercise and has really opened up my eyes to alternatives for a number of areas.
So we’ve talked about Membrane’s CRUDController, and as stated most of the time developers won’t need to do anything more than inherit from the CRUDController when writing new plugins. There will be occasions where developers need to overwrite the functionality of the CRUDService though.
I’ve banged on about Membrane having a CRUD Controller and Service quite a few times now. I suppose it’s time to explain this a little more. Especially as we now have some basic Membrane functionality running directly off them. (I’ll talk about the CRUDService in a later post, as most plugin controllers will not have to deal with it).
It’s been a while since I last blogged about Membrane and it really is time to give a progress report and where possible try and encourage more developers to get involved.