As much as I love ExpressionEngine, sometimes it isn't the right fit for a project, and often it's because it provides more power and flexibility than a site really needs. Sometimes you just need something a bit simpler. Or sometimes you get a project that the site owners don't want a CMS for, but as a developer, it's quicker to build the site with one. So this year, I began looking at some CMSs that I could use an alternative.
It's been a while since I wrote anything on this blog and it's possible that this may be the last post here because from now on I intend to do most of my writing at my new blog. This site is due for a redesign but the first part in that strategy involved setting up a new site. If that doesn't make much sense, please read the first post on the new site in which I explain my reasoning.
I'm not ruling out entirely ever writing articles on this site in the future, but it won't be until after the site has been redesigned and I don't have an exact timeline for that right now. So in the meantime, if you've bookmarked or subscribed to the feed for this site, you might like to do the same for the new one too.
Yesterday I was working on the planning of a new site to be built with ExpressionEngine and was wondering about the best way to let editors link to other entries from within the body of an entry they're creating or editing. ExpressionEngine doesn't have this sort of functionality built into it by default so I asked on Twitter to find out if anyone knew of any add-ons that had been created that might do this.
With ExpressionEngine you give your clients a lot of power and flexibility to update the content of their own site, but at some point in a site's life there's going to come a time when changes will be required that the site owner or his/her staff can't do themselves via the control panel. Changes to a logo or other graphical elements of the site, adding new sections or functionality, giving the site a new 'skin' or theme, or completely rebuilding from the ground up will require a designer of developer to get involved.
Over the years of being a freelance web designer, I've been developing my own processes for the business of designing websites. One of those processes has been compiling a list of tasks that need to be completed before launching a website, whether it be a new site or a redesign. This list is kept in a spreadsheet which I work through, ticking off each item after the client has given final sign off for the site to go live. I view it as my final quality control procedure and I usually find that the process will highlight a few of the 'little things' that I might have overlooked in general development. Usually nothing too major; more a case of 'dotting all the Is and crossing all the Ts'.
Recently I came across a sitution whereby I wanted to call a list of Wordpress posts from inside the body of another post, i.e., not coding it into a template, but embedding into the body of the post itself.
Not a big drama, I thought to myself: I already have the exec-php plugin installed to enable the execution of PHP from within Wordpress posts, so all I needed to do was call the Wordpress loop from the point inside the post where I wanted my list of links to appear, e.g.:
<ul> <php $my_query = new WP_Query('cat=XX'); while ($my_query->have_posts()) : $my_query->the_post(); ?> <li><a href="<php the_permalink(); ?>"><php the_title(); ?></a></li> <php endwhile; ?> </ul>
Håkon Wium Lie's article, CSS @ Ten: The Next Big Thing on A List Apart in August 2007 may have got the (snow)ball rolling, but it seems that it was the announcement of Typekit on May 27 this year which has prompted an avalanche of interest in web fonts. Or maybe I've just woken up to the issue since then and been taking more notice. But I seem to be adding a lot of font and type-related bookmarks lately and thought it would be worth sharing some of them.
If you use TinyMCE in your Content Management System (CMS) projects, you no doubt also give clients the ability to add images and links to their content with TinyMCE's Link and Image buttons. But by default, these popup windows come with a variety of fields into which unsuspecting clients can input values which will translate into unwanted code when delivered to the page.
- The client specifically asked for AJAX to be used.