After months of work I just launched a new web site for my photography. The reason I think it’s of interest here is because of the role Panorama X played in building it - and in making it very easy to generate updates.
The site has numerous galleries and slide shows consisting of many images each.
The galleries involve a very precise chunk of html per image; html table structure, css styling, a few links with some tying to javascripts and the image. With a single click I can trigger a procedure that builds those chunks of html as an array, and merges it all into an html or php template for the overall page. A second array is inserted into the page head with javascript specifically applicable to some of the links included with each image. Then the entire page is saved, ready for uploading to the server.
The information built into these arrays is all derived from entries in my ImageLog. The procedure refers to captions, keywords, orientation and such to build a unique array element for each image. Based on the keywords, a single image may end up in more than one page for the site. For instance an image with keywords of landscapes, sunsets and rivers could end up in three separate pages, each consisting of images with common keywords.
The slide shows are a bit different but also built from the entries in my ImageLog. In this case, an array is built for a selected set of images, but this array is purely javascript. Besides being able to build a new javascript from scratch, it can load an existing javascript for me to make a quick edit to a caption within the show and resave it.
Consistency of the coding within the site’s pages is complete; a rarity.
For either galleries or slide shows, whenever I add new images to my ImageLog, it takes just moments to generate whatever pages need to be replaced or added. If I make a change in page layout or function, the whole site can be modified within minutes.
In the near future, ftp’ing the pages to the server via curl will be part of the PanX automated process. Then I’ll also be able to use my PanX file to do some live editing on the server to quickly correct a typo or to enhance a caption.
While all of this involves photography, the same idea can be applied to anything being published to a web site. Product catalogs, price lists, real estate listings, personals, classifieds, meeting minutes, financial reports… New or updated pages can be generated in an instant and loaded to the web server.
Of course, Panorama as a web server takes it all to another level. Here I’m describing static but easily replaced pages. Using Panorama Server, pages can be generated on demand on the site. For instance, instead of a prebuilt page of images with a common keyword, the pages can be built as needed in response to a far greater variety of keywords and criteria. Much like real estate listings could be tailored to price, square feet and other specifics defined by the site visitor.
You can see my galleries and slideshows at JamesCook.biz. Take a look at the page source to see what Panorama X has allowed me to accomplish. ImageLog is available in the Panorama Database Exchange, but does not include the procedures I’ve described above. Those are in a separate PanX file I’ve built to access and utilize my entries in the ImageLog.