Codeistry

Archive for September, 2008

Creating a new support contract

Friday, September 26th, 2008

I’ve started to put together a new support contract, for supporting my existing customers. I’m trying to come up with a contract which will allow me to provide excellent support, without going out of business in the process.

I also don’t want the support contract to be onerous or expensive – it should be good value and you should only pay for what you use. I want to create the kind of support contract that I’d want to sign up to myself, basically.

Only pay for what you use

There will be no monthly fee or retainer – you only pay for what you use. I’ll keep track of the support time spent and invoice you at the end of the month. If you don’t need anything for a few months, that’s fine – no charges & no invoice.

I’ll provide a fully itemised list of all the support incidents and follow-up work done, so that you know exactly what’s been going on and where the money went.

Free stuff

I think it would be nice to offer some free pro-active support, on the same pay for what you use principle.

Periodic website health checks might be something that people would find useful.

Section from the Codeistry sitemap/graph, showing a few pages (as circles) and links as lines linking the circles together.

This would consist of an automated health check, making sure that the site is available and that all the links, pages, images and files are present and correct. This report would be automatically supplied to you, for nothing. I’m thinking that a sitemap, with broken links highlighted in red, plus a text report, might be quite nice.

Optionally any issues (missing pages or whatnot) could be followed up, on a pay-as-you-go basis.

New version of MODx CMS out – 0.9.6.2

Wednesday, September 17th, 2008

A new version of MODx has just been released – 0.9.6.2, with a whole bunch of fixes and updates. There have been loads of fixes and updates checked-in by the MODx team & the community since 0.9.6.1 and lots of code clean-up and multi-language fixes done.

See here for MODx forum announcement and here for the complete (long & technical) changelog.

I’ll be upgrading the Codeistry site over the next few days and and then rolling the update out to all client sites as soon as possible after that.

My highlights amongst the many changes are:

Allow weblinks to have summary (introtext) fields

Weblink documents can now have an introtext summary, like normal documents, which is quite handy.

Set the published status of duplicated documents to unpublished

When you duplicate a document, it will now be set to un-published. Previously it would copy the published status of the document that you were duplicating – which was almost never what you really wanted.

Updated @INHERIT TV command to see through un-published pages.

Template variables which inherit their values from their parent documents, will now do so even if their parent document isn’t published; this propagates down through the site structure.

Added a manager role for emptying the trash/permanently purging docs

There’s now a manager role for permanently deleting documents which is handy in setups with lots of users.

Added plugin to show image previews in the manager for Image TVs

Screenshot showing Template variable Image plugin working.Really nice feature which shows you a thumbnail preview of the image being used by a template variable while you’re editing the page.

TinyMCE 3.1.0.1a and MCPUCK file browser improvements

This is great – the document content editor component has been updated to the latest version – which saves me from doing it on every install. This newer version of the editor is a big improvement on the previous one shipped with MODx 0.9.6.1

Updated ‘built-in’ snippets:

  • Updated Jot snippet to version 1.1.3
  • Updated Breadcrumbs snippet to 1.0.1
  • Update AjaxSearch to 1.7.1 and Search Highlighting plugin to 1.2.0.2
  • Update Ditto/Reflect to version 2.1
  • Migrated Mootools to 1.11

Patches to Ditto 2.1 to fix sorting and change default docs displayed number from 3 to “all”

Ditto will now display all documents it finds by default, instead on only the first 3, and sort order fixes for MySQL 5.0.31a

Added the ability to easily add custom help pages to the manager.

Screenshot of the help MODx manager help page, showing a new test tab.This really is simple – just create the HTML files in the /manager/help folder and they appear at tabs on the Help page. Neat – I’ll be taking advantage of this in due course.

Fix to alphabetical sorting in MCPUCK browser

Fix for sorting images alphabetically in the image browser. This now seems to work properly, the image browser sorts images alphabetically, making it much easier to use, especially if you’ve got lots of images in a folder.

Added XML doctype and header to MCPUK for file uploads

This should fix a very annoying error when uploading files via the resource browser, especially in Internet Explorer.

Added RSS Feeds of the Security Announcements and Important News to the Manager Login Welcome Page.

Screenshot on the new MODx Manager Welcome page, showing new RSS feed tabs.This is quite useful – it helps keep site administrators up to date with the latest MODx releases and security updates.

Fix ‘Allowed Days’ checkboxes for Manager users

These were previously the wrong way round – unchecked when they should have been checked, as I discovered the other day during a live demo.

Colour contrast & accessibility

Tuesday, September 16th, 2008

Zoomed in composite screenshot showing the Codeistry website before and after the contrast tweak.I’ve been playing around with the Codeistry website’s colours, to improve the contrast and accessibility, whilst retaining the same feel.

The changes are subtle but move the site from mostly failing to almost completely passing the contrast and luminosity tests from JucyStudio.

It might seem obvious but going through this process brought home to me how much the perceived contrast of text depends on the background colour behind it. Text that looks fine on the normal page background might have insufficient contrast when used in a footer, link or menu – where the background colours are different.

The changes included changing the body text to use the old heading colour, using a slightly darker colour for headings and links, and a slightly lighter shade for the page footers, to increase the contrast with the footer text.

I actually think that this has helped the design too – not only for accessibility but it also feels stronger, with more impact and weight. I may even revisit this in the future and punch it up a bit more.

Colour contrast testing tools

http://juicystudio.com/article/colour-contrast-analyser-firefox-extension.php

Codeistry blog is proudly powered by WordPress Entries (RSS) and Comments (RSS).