My friend Stephan unveiled his new site yesterday at http://sbritt.com. Design-wise, I think it’s top notch and perfect for the artistic content he provides.
I helped him build it over the past few weeks. He sent me folders with all of the pages meticulously mocked up and then each image section sliced and ready to go. This is a real treat, as mostly I don’t receive such precise direction from my usual clients.
In the process of putting the site together, I had to learn a little more about WordPress. I used both hand-built and WordPress pages to power the site. In hindsight, I probably could have used WordPress for everything, but it would have been a clunky affair, especially for the pages with multiple subpages of image thumbnails.
My initial plan did not include WordPress at all. I would simply code the HTML, CSS, and provide a mechanism for Stephan to display his thumbnails and images. I made folders for each section of Stephan’s site, and he uploaded his images into them. Then, I used PHP to scan the folders and display the thumbnails accordingly.
After doing this, I realized that we needed a backend for Stephan to enter the text for non-image pages and manage his news section, and I knew that WordPress would get us there faster than me building something myself.
While I was working on that, Stephan asked for the ability to put unique captions on his images, so I created a database and built a backend for it directly in WordPress. This method is nice, but it is prone to being wiped out by upgrading versions. What I did is not really plugin-worthy, as it’s totally unique to this particular site, and I would have to build many, many options into the plugin to make it useful. For, now, I need to re-upload the backend pages I added after an upgrade and tweak the navigation. At some point, I’ll figure out a way to handle this in the future.
Check out Stephan’s site, leave him a comment if you like what you see. He’s amassed a truly staggering collection of brilliant art.