WHITEonline is the digital home of Gary & Linda White. We’ve been married since 1980 and live just outside Toronto in Ontario, Canada. Linda was born and raised in Toronto while Gary was born in London, England and moved to Canada at the age of 11. He calls himself a $45 Canadian - which was the fee he paid in the process to attain Canadian citizenship.
We have two adult sons - Matthew & Michael. Our oldest son Matthew has been married to Lauren, née Crawford, since 2014 and their daughter Raechel was born on February 20, 2017 - our first grandchild.
We enjoy travelling and taking photos while we travel. WHITEonline provides the opportunity to share some of our photos & experiences.
Updated: August 9, 2019
As mentioned above, all WHITEonline webpages are created using RapidWeaver 8, Stacks 4 and the free-form framework Foundry. The majority of add-on Stacks used on WHITEonline are those supplied with Foundry. The Stacks list above shows all of the other stacks used to create WHITEonline.
For webpage development, we use Partials as much as possible to create and reuse page elements within our RapidWeaver project. As part of that process we've developed a naming convention to make it easier to locate and use a specific partial. The use of Partials has facilitated quick site-wide style and content editing.
All photos for WHITEonline are stored and edited in Adobe Lightroom. For some of the colour images there is occasional external editing done in Colour Efex Pro, Viveza & Define - all part of the Google Nik Collection as well as Adobe Photoshop. The black & white photos are all created using Silver Efex Pro - also part of the Google Nik Collection. Whether the images are edited inside or outside Adobe Lightroom they are always stored in a Lightroom catalogue and the images are colour coded for quick identification and access.
Images for use on WHITEonline are exported from Adobe Lightroom to an export folder. Images intended for image galleries are exported at a standard size of 1200px wide and also at two times that size of 2400px for display on HiDPI monitors. Images are then optimized for website use by being processed through an image compression application. The primary image compression app for WHITEonline is ImageOptim. We have also experimented with Squash and JPEGmini for image optimization but we find that the best results for us come from processing image files through ImageOptim.
Images that will be directly added to the RapidWeaver project file are stored in a source files folder on the editing computer. Images for image galleries are not added directly to the RapidWeaver project, but rather accessed as remote images - known in the RapidWeaver community as warehousing images. These image files are stored in a local export folder for the website on the editing computer. There is more information about that in the publishing workflow.
The method of publishing WHITEonline is something that underwent a significant change at the end of 2016. RapidWeaver does have the ability to publish a website project directly to the live server, but we have found this to be a bit problematic through 2016 as our website project grew in size and complexity. It got to the point where the entire project would not publish in one go - failing at some part of the process. To publish from within RapidWeaver it required publishing manageable sections of the project one at a time until the whole project was finally published - which was slow and frustrating. It also meant that nothing else could be done with RapidWeaver during this drawn out publishing.
The publishing solution for us now is that we only publish the website locally and use the FTP client Transmit to sync the local version of the website with the live version on the server. Local publishing is very fast and once the local publish is finished the sync feature on Transmit copies any added or changed files to the live server. The great thing about this method is that it can happen in the background and frees up RapidWeaver for more editing. The syncing is fast, but it doesn't really matter because RapidWeaver is accessible during that process.
Using Transmit to sync the local and live server versions of the website is also why we only need to store the remote/warehoused images on the local version of the website as we mentioned in the images workflow. The ftp client copies those files to the live server during the sync process.
Transmit can also be used to delete orphaned files during the sync process. This is a nice way to get rid of files no longer being used by the active web pages, but this feature is something that must be done with extreme care - especially if information is added to the live server without going to the local version first.
The WHITEonline Blog - From the Desk of the White House north of the border is now created in Poster Stack by inStacks Software. We gave up the ability of editing the blog remotely with the Content Management System (CMS) Armadillo by Nimblehost to get the look and functionality provided by Poster Stack within RapidWeaver. We shall see how that change goes.
WHITEonline has a custom 404 Error page, but to get it to work properly from any section of the website all links had to be the full URL rather than being relative to the page or root. We were never successful in getting RapidWeaver to generate all URLs as required, so we adopted a process to manually edit the URLS for the custom 404 Error page. This is a page that changes rarely - usually only needs an update after a website style change.
After a style change, the 404 Error page is published locally with the project just like any other page in the RapidWeaver project file. Once that is done, the page is set to Draft mode in the RapidWeaver project file so that it will not be published from RapidWeaver inadvertently.
The locally published 404 Error page is then edited using the text editor application Atom. All URL links are updated to show the entire website URL for each link. Atom makes this a simple process that only takes a couple of minutes at the most. After the edited file is saved then the local version can be synced with the live server using Transmit as part of the normal publishing workflow. With the 404 Error page in Draft mode in RapidWeaver the local page will not get overwritten by mistake. A major change will require repeating the process. In the interim, small edits can be done in Atom as required.
WHITEonline is the digital home of Gary & Linda White. We’ve been married since 1980 and live just outside Toronto in Ontario, Canada. Linda was born and raised in Toronto while Gary was born in London, England and moved to Canada at the age of 11. We enjoy travelling and taking photos while we travel. WHITEonline provides the opportunity to share some of our photos & experiences.