Beyond the site, however, the real reason for this post is, well, I wanted to share something I realized while working with him. While I’ve known a few folks that claimed, or actually were, photographers, Ron’s work was the first time I really understood photography as an art form, aside from the Ansel Adams prints we all see around. These images, really, made me see a camera in his hands is very much like a brush is to a painter. The quality of work here isn’t in the equipment, it’s in the eyes, the artist’s perception of the moment they are trying to capture, and that the true artistry in photography is in actually being able to capture that moment exactly as the photographer intended. If you would like to see some amazing stuff, pay his site a visit, you won’t be disappointed.

You can view this site here.

Take a look for yourself here.

The first is Dropbox.  No matter how easy software and hardware manufacturers  try to make computer networking and file sharing, the technology still remains out-of-reach for most normal computer users without help from technology professionals.  Dropbox pushes all the complexity aside, allowing people to share files with different devices, and different people, all by installing one little program.  It also acts as an off-site backup, giving an additional layer of security for your important files.  Easy-to-use, accessible from computers and smart-phones, and a great, cheap, safe backup solution, Dropbox always makes my list of most-recommended products.

The next must-have software is Malwarebytes.  Without question the most important tool in my, and many other technology professional’s arsenal in the fight against viruses and malware.  Nothing, and I mean NOTHING is better when trying to clean an infected computer.  Take it from someone who makes their living removing malware, anti-virus software is not enough.  I’ve never removed a malware infection from a computer that did NOT have an anti-virus product installed.  The first thing a good piece of malware does is either hide itself from the anti-virus, or actually disable the anti-virus product.  The first thing I do when confronting an infection is install Malwarebytes.  In over 70% of the cases, it’s all I have to do.  Save yourself some time, and money, get Malwarebytes.   If you ever are the unfortunate victim of a malware infection on your computer, before you call the professional, do yourself the favor of running Malwarebytes.  You might just find that you fixed the problem yourself.

As malware removal accounts for almost half my business here on Pine Island, I have one more product that I strongly urge anyone who uses the internet to take advantage of.  OpenDNS.  While the subject is rather complicated, and full of technical jargon that is bound to bore most normal folks to tears, I feel that the OpenDNS service is important enough to risk it.  Without delving too deeply into the subject, OpenDNS offers a method of filtering your web traffic before it ever reaches your computer, providing a way of stopping a potential infection before it starts.  Their website does an incredible job of explaining what it is, and how it works, and most importantly, in easy to follow steps, it will show you how to take advantage of their free service.  An important thing to keep in mind is that when dealing with malware, there is no silver bullet that will keep us 100% safe.  Everything we can do, anti-virus, firewalls, Malwarebytes, and OpenDNS, all of these things provide only a paper-thin layer of protection.  But when used in conjunction, all of these products add up to a thicker layer that can help mitigate the threats that await us.  Keep in mind, however, the thickest layer of protection is us.  Learning how to develop safe web-surfing habits, and learning how to recognize suspicious activity, is the most important defense in our fight.

My last recommendation is directed mostly at small business owners.   Many of us already use Gmail, it is a great free email service.  Many people do not realize, however, that Google has really taken things to a whole new, business-friendly level with Google Apps.  The service is free for up to 10 users, making it ideal for small business looking for a robust, flexible,  easy to use email and calender system.  It allows you to use your own domain name, such as mine, tarpontech.net, as the basis for your email accounts, like my adam@tarpontech.net, but your email is handled by gmail, so that you can log into any computer or device to check email.  But that is only the beginning.  I work with many small businesses that are looking for a method of sharing calenders and documents, as well as have the ability to share email and email account access.  In the past, we had to rely on expensive hardware and software solutions, often running into the ten’s of thousands of dollars. Now,  Google Apps does everything these other solutions accomplish, and more.  Whether you are a service manager looking for an easy way to keep appointments scheduled for multiple employees, an executive assistant trying to keep your employer organized, or a small office who is just trying to look more professional, Google Apps is the answer.   On top of ease of use, and the ability to access it from anywhere, it removes the concern of backing up your email, as everything is hosted by Google, so even if a computer dies, you won’t skip a beat when you need to get to your email or scheduling calender, all you’ll need is another computer with internet access.  While I strongly recommend you leverage an IT professional to help set-up your Google Apps account, if you have a little tech savvy, and a little bit of time, I found the setup process relatively painless.

Here’s a list of links for the products

• Dropbox
• Malwarebytes
• OpenDNS
• Google Apps

Its All About the Search!

Nearly 90% of site visitors go directly to the property search. Therefore, not only should the search be prominent, it should be the first thing they see, the last thing they see, and if you wanted to go really crazy, it could be the only thing they see, as they’re not likely to look for anything else. Well, except, of course for home valuation data. Zillow.com makes it quite clear what their site visitors are doing. According to them, if their visitors aren’t looking at listings, they’re looking at property valuation, something to bear in mind when trying to come up with ways to extend a visitor’s stay.

Keep the Word Count Down, and the Image Count Up

When displaying property listings, precious screen real estate should be dominated by pictures, with perhaps 10 words or less of supplemental text, and this includes the standard property stats

Extended property descriptions should be put off to a separate page dedicated to each listing. There are only a few key questions that most people are trying to get answered as they scan a large selection of listings.

• What does it look like?
• Does it have adequate facilities?
• What’s the asking price?

Most home shoppers do their research on multiple real estate sites. I’ve seen many sites laid out in such a way that they are nearly dominated by walls of text and superfluous home descriptions, in what I believe is a misguided attempt to improve SEO. SEO in my experience is about quality, not quantity.

Keep It Automated

Something I’ve learned from direct experience as well as anecdotally from other site-designers working the Real Estate market. Asking your average agent and site owner to create a blog post can be challenging, depending on their inspiration and dedication to the task. Asking them to manually create resized thumbnail images, then enter the URLs in 3 different fields, or using more than 4 or 5 custom fields in general, to where creating a blog post resembles a multiple choice quiz for computer enthusiasts, is not going to help keep your agent productive on the site, improving their SEO, site traffic, and potential for online success. Image dispersal needs to be completely automated, as should excerpt creation, seo fields, anything and everything that can be done automagically will improve your site users productivity, helping the site achieve maximum potential, and making you look like a superstar!

A Final Word and a Link to the Work-In-Progess

I’m also trying to build this theme to be more modular, to allow for changing design trends, as well as to allow me to use the site as more of a framework, knowing that reusable code is the greatest gift a developer can give themselves. The most challenging part of this, to me, is not making it LOOK modular, but more… organically designed. Perhaps this is where I’ll show my greatest strengths, or weaknesses, in both development and design. But, I suppose its good to have ideals to strive for.

For now, I’m hosting my test copy at realestatic.tarpontech.biz. I’m using it as a blank canvas, so it is, and will be, rather bland. Real Estatic is being developed primarily to work with the WordPress real estate plugin WP-REALTY, as its the best software package I’ve found for importing MLS listing data into a WordPress site. In my experience, agents don’t simply want to display their listings, they want to be THE destination site for their clientele, and this requires a full-featured property search based on the local region’s MLS. Sites that don’t offer a complete regional property search are without question the exception, not the rule.

• Justin Tadlock’s Get-the-Image plugin works nicely for digging images out of posts.
• Timthumb.php by McDaniels, Hoyt, and Gillbanks has been the standard in image resizing for a while.

Getting these two scripts to play nice wasn’t too big a challenge thanks to a helpful little post by Morten Skogly over at http://pappmaskin.no, where he shows how get-the-image can be configured to output an array containing the image url you need, then feeding that url into timthumb.

Life was good. Until I tried this method on a 3.0 blog network (mu), and ran head-first into timthumb’s pathing problems with MU formatted urls.

Ben Gillbank’s post on the subject helped me understand the problem, but the fix wasn’t made apparent to me via his fix. Luckily, I stumbled on a post by another wordpress aficionado and Thematic contributor Devin Price, here, that gave me the final piece of the puzzle I needed to put this issue to bed.

First we need a function to rewrite our image url from a relative (mu) path to the absolute path that timthumb can work with. The following is hanging out in my functions.php:

function get_mu_image_path ($img_src) {
    global $blog_id;
  if (isset($blog_id) && $blog_id > 0) {
    $imageParts = explode('/files/', $img_src);
    if (isset($imageParts[1])) {
      $img_src = '/blogs.dir/' . $blog_id . '/files/' . $imageParts[1];
    }
  }
  return $img_src;
}

I have shamelessly ripped this from Devin Price, who in turn altered Ben’s original fix to suit his purposes.

Next we need to use get-the-image to, well, get the image, take that image (path) and run it through this function to make it timthumb-able. With that out of the way, we’re free to take our image url (as a variable) and run it through timthumb!

<?php
//first crank up get-the-image, and ask for it's output as an array
if ( function_exists( 'get_the_image' ) )      
$get_the_image_as_array_feature = get_the_image( array( 'image_scan' => true, 
'format' => 'array','default_size' => 'full' ) );
//take what we want, the url, and turn it into a variable we can play with
$the_img_src = $get_the_image_as_array_feature[url];
//scrub the url path
if(!empty($the_img_src)) {
$the_img_src = get_mu_image_path($the_img_src);?>
<div class="postacular"><!--pass our image url through timthumb
<a href="<?php echo $get_the_image_as_array_feature[link]; ?> ">
<img src="<?php bloginfo('stylesheet_directory') ?>
/includes/plugins/timthumb.php?w=480&h=274&zc=1&src=<?php echo $the_img_src; ?> " 
alt="<?php echo $get_the_image_as_array_feature[alt]; ?>"/></a>
</div>
<?php }
?>

Couple things to note:

• this snippet is being used directly in a page template loop inside a child-theme (hence the “stylesheet_directory”)
• I’m using additional get-the-image variables for things like the image alt tag and link url.
• please note the custom path to timthumb.php

This snippet can be turned into a nice content filter for functions.php without much hair-pulling, and i’ll most likely do this too, and I’ll try to remember to post it here.

As a final word, this is unfortunately not a cut-n-paste post. If you arn’t familiar with get-the-image and timthumb, you gotta read their instruction manuals, what I stuck here is a basic example of how to use it, but there’s a few switches and options to play with in order to suit your needs. Consider this “proof-of-concept” for helping to make wordpress posting more accessible for those of us less technically inclined.

Here’s the story…

To those who know Thematic, they’ll immediately recognize what Shabadoo really is. It’s Ian Stewart’s Feature Site theme, just wearing a pretty dress and some lipstick. I converted Feature Site from it’s original 988px grid layout to Thematic’s more standard 960grid 2 column right-sidebar layout. Working in the 960grid was easier on me for graphics work.

I shoved in a featured content slideshow using Niall Doherty’s Coda Slider. While I’m not in love with it, as it needs some work, it does do a decent job of pulling posts from a theme-option’s specified category and displaying them. I had to use Justin Tadlock’s Get-The-Image plugin to get the images pulled correctly, as I hadn’t yet figured out how to get TimThumb working on a WordPressMU site.

More than anything, Shabadoo was an experiment. An experiment in jquery implementation, things like Cufon fonts and little eye-candy add-ons, in creating theme-options to make the theme more user-friendly to customization, and also regarding Thematic filters, in order to get the blog, category, and archive pages displayed the way I wanted.

At the sake of being a broken record, remember, its an experiment, and an incomplete one. Some area’s, like the footer, haven’t been touched from the Thematic core. The code is 99% WC3 valid, there’s just a couple bugs that are easy (i was too lazy) to quash. However, the biggest issue is with the content slider. For some reason I can’t seem to get the coda slider to operate properly when calling the jquery from wp_head. I had to call it from thematic_before, and that isn’t all that great. It works, and I’ve tested it against quite a few plug-ins, but I have a funny feeling about it. I may return to the project and implement a different slideshow, most likely jquery_cycle, incorporating timthumb to help make certain the thumbnail’s get cropped properly.

All-in-all, however, I think its a great launch-point for someone just getting their hands dirty in Thematic child-theme development. It gives some good insight into how to implement Hooks and Filters, and how to go about taking the sample theme-options page, so graciously provided by Ian and the Automattic team, and putting it to work.

Lastly, I’d like to give credit again to Ian Stewart for, well, everything. He’s the primary reason I’ve come as far as I have in theme development. I’d also like to thank Cristian Antohe over at Cozmo labs. I completely ripped off his totally awesome theme-option code for adding a custom logo to a Thematic child-theme. Don’t worry Cristian, I left your comments and credit intact! Thanks!

You can download the Theme here. The zip includes the theme, a layered Fireworks .png (sorry photoshoppers), all the plugins (all one of them), and all the images from the sample site.

You can view the sample site here.

Instructions for use

This thing is running on the latest Thematic development release, which you can download from here if you’re not already using it. The latest and greatest adds WordPress 3.0 support, which you’ll need since I’ve added 3.0 menu functionality.

You’ll first need to create a page called “Home” and give it the “front-page” template. You’ll want to set this as your front page in the WordPress Reading options, and create a new page for use as the main blog index.

Next, create your new custom menu so you can navigate around You can have as much sub-page navigation as you desire for the main menu. You’ll want to create a second page navigation menu, and be sure not to have any child pages, keep all pages on the same level, this menu can be used for side-bar page navigation, which you can add via a widget. I formatted the ul structure in the sidebar in such a way that if you have sub-pages (li li), you’re gonna have some sidebar style issues.

I’ve tried to make the Shabadoo theme options pretty straight forward, time will tell, however…I’ve supplied all the images used on the sample site, which should give a pretty good idea of what goes where, and how.

With a little work, this could become a working site, but I think it works better as a learning demo. There are so many things that can be done better, cleaner, and prettier. I use this site as a hooks and actions reference, hopefully you’ll be able to do the same.

1. How to configure VieleRETS for use with WP-Realty
2. How to configure a batch job in VieleRETS
3. How to configure a batch job to run in CRON

What this does not cover:

1. How to install VieleRETS and perform general configuration (i.e. communicating with your RETS server)
2. How to install or configure WP-Realty

For general VieleRETS setup information, Trent Richardson created a terrific blog post that I found invaluable when starting out.

Creating Sources: Telling VieleRETS what to download, and planning ahead for WP-Realty integration.

Setting up your initial sources can be…problematic if things don’t go well out of the box, but between Trent Richardson’s blog posts and the VieleRETS message board, hopefully you’ve been able to get communication up and running between your RETS server and VieleRETS. We’re going to focus on issues that directly pertain to getting VieleRETS and WP-Realty to play nice.

The first thing to know is that you will need to create a Source for each of the property types you wish to display listings for, examples being Residential, Commerical, and Lots (land). Make sure to name your Sources per Property type, don’t just call them Default, Default_1. Name your Sources Commercial, Residential…ect…you’ll thank me later.

You’ll notice that part of the process of creating a source is choosing which fields to download. It’s entirely up to you what fields you wish to use and/or display, but take note of what you pick. You’ll need to create the listing fields within WP-Realty that correspond to the fields you are downloading from VieleRETS. This step is VERY, VERY important. Take your time, think it out, consult with your clients/agents/friends/family, whatever, but don’t take this step lightly. Save yourself A LOT of additional time and work, and make certain you’ve selected every RETS listing field you may, possibly, ever need, and make certain that you’ve created a corresponding listing field inside WP-Realty. Missing a field at this stage will cause you to have to start all over again if you decide you really needed that “other rooms” field a month from now. You’ll need to purge your database, recreate all of your VieleRETS configuration, and then download the whole database again.

The fields inside WP-Realty don’t need to match exactly what they’re called in RETS, such as, the field in RETS is called Subdivision, I called it Neighborhood in WP-Realty, but it’s recommended to keep things the same. It makes things a lot easier when you are sorting through 120 fields to match them up. You’ll see why when we get to creating Extracts.

Lastly, while I can’t help with the myriad different ways VieleRETS talks to different RETS servers, I will give a little advice. RETS servers like for folks that are querying it to ask for certain minimum information. In my case, most servers like you to at least query for City, ListPrice, and Status. If you can’t seem to download anything, I’d check to see what fields you are using to Query, first.

Ok, so, we’ve got Sources set up to match all the Property Types we’ll be using, and we’ve selected all the fields we’re going to download for each Source, and we’ve created all the corresponding fields inside WP-Realty.

Creating a TARGET: Telling VieleRETS how to find WP-Realty.

VieleRETS needs the full root path to your wp-realty plugin installation. How to determine this depends on your hosting environment. Most shared web hosting accounts stuff all of your files inside of your account’s /home/ directory, but if you are unsure of your root path, save yourself much time and aggravation and call your hosting tech support and get the right answer.

Once you’ve determined the root path to your wp-realty plugin installation, you have two possible ways of using VieleRETS’ menu to navigate to it. If the server’s permission structure allows, you can just click the radio buttons corresponding to the correct folder you need to navigate into, or, more reliably, just type the full root path into the field labeled “Full path to Open-Realty install”.

It should look something like:

/home/your_hosting_account/public_html/wp-content/plugins/wp-realty

One little trick about VieleRETS is that it may not automatically recognize the path once you’ve typed it in.
By clicking someplace else on the page, such as clicking into the Name field at the top (just don’t change anything!), VieleRETS usually refreshes and will navigate to the path you’ve specified. When this happens, the screen will change to display the list of WP-Realty fields available to be populated by MLS data.

If you don’t see the screen change to show these fields, you most likely have a file permission or php permissions issue, both of which are outside the scope of this document.
Let’s hope you didn’t have a permissions issue. I’ve used this system on 4 different hosting accounts, with different results, but when permissions and PHP configuration are correct, creating a Target is dead easy.

Creating an Extract: Getting VieleRETS and WP-Realty to play nice.

Once you’ve created your individual Sources within VieleRETS, you’ll need to set up your Property Types within WP-Realty, using the EXACT names being used by VieleRETS. Doing this while creating your Extracts is a good idea, as you’ll have the Property Type names (called Class Name Style in VieleRETS) staring you in the face during the Extract creation process. Word of advice: If VieleRETS is using Residential, don’t create Property Type residential in WP-Realty, it’s case sensitive.

Once you’ve established what property types you’re going to use, take note of the Property Type names in use by your MLS. My best example of this is in regards to Multi-Family units such as condos. Many RETS servers will provide you with the option to use Condos/Townhomes or CommonInterest as possible property type names. The WP-Realty database does not play well with Property Type names that use a slash, such as Condos/Townhomes, so you’ll want to choose CommonInterest, or another Property Type name that doesn’t use a slash. Remember, Case Sensitive.

Creating an Extract isn’t difficult, but it is tedious, which is why its so important to have all your fields set up correctly in the Source, and in WP-Realty, not to mention having everything named right.

To start, name your extract per Property type, as well, you’ll need one extract per property type. Each Extract reads from its own Source, but luckily they all point to the same, shared Target (wp-realty’s database).
You’ll need to choose the corresponding Source, (see why naming is important?), I’d take a moment to consider the “maximum images to download” option. Something around 10 images is probably more than enough to displaying a property. Some overzealous realtors can stuff a lot of images on the MLS for a single home, and your server’s storage capacity and bandwidth limitations won’t be so kind to you.

The last setting on the main Create an Extract page is the Class Name Style. We’ve already gone over this at the beginning, but be sure to pick a class name (property type name) that plays well with the WP-Realty database.
Once done with this page you can apply your changes, and you’ll be confronted with a menu of options.

Now is the time for some tedium. The only other area we need to focus on for an Extract is the Data Map. Don’t mess with the (Expert) data map. The Data Map page is self explanatory. Here you tell Viele-Rets where inside the WP-Realty database to put the data it is downloading. If you followed my advice and named your WP-Realty fields the same as the RETS fields, it’s a simple matter of matching names. Once done, triple check, however. You don’t want prices to start showing up where half-baths are supposed to display.

That’s really it for creating an extract. Now you just have to do it a few more times for each Property Type. Enjoy.

The moment of truth

Now we find out if we have any idea of what the hell we’re doing. Time to run an extract.

From the VieleRETS main menu, choose Download Listings.

Choose an extract and Apply.

Your download Criteria are dictated by the “Fields to Query” you set up during Source Creation.

If you don’t get any results, you may have to fiddle with these fields till you get something your RETS server likes. In this test case, I’m using Status, City, and ListPrice. You may want to “Set Download Limit” to 10 or 15 listings to start, we’re just trying to make sure the system works, we can pull the entire contents of the MLS after we know things are a go.

The last thing I want you to take note of before we apply our settings to run an extract is the “Update the Batch Control File” Later on we’ll be talking about automated batch jobs, and using this feature can save us a little time in creating our batches. For now, leave the box checked.

If things went well, the batch will complete, and you’ll see a brief summary displayed at the bottom of the page detailing how many listings and images were downloaded ect…

If you didn’t get a successful extract, but you’ve gotten this far, you probably (hopefully) just need to tweak your “Fields to Query” in your Sources, and adjust what criteria you use when running the extract.

For those of you that got a successful batch, you should be able to view the listings inside your WordPress blog, depending on how you’ve set up WP-Realty.
Or, you can view the listings under the “Edit My listings” or “Edit All Listings” inside the WP-Realty Control Panel.

If you’ve got properties, you’re in business.

Creating Viele-RETS batch jobs and running them automatically via CRON

I’m skipping ahead a little bit, and I’m not going to go over how to run a batch from the command line, the VieleRETS message board and Documentation goes over that well enough. What we’re going to talk about is how to fill up your wordpress blog with every single listing your RETS server will allow you to download.

It’s actually really easy, just takes some busy work. First, lets look at a sample batch job:

<VIELE_BATCH>
<EXTRACT> residential
</EXTRACT>
<!--<QUIET/>-->
<UPDATE_BCF/>
<!--<UPDATE_ONLY/>-->
<LIMIT> NONE</LIMIT>
<QUERY_VALUE name="ListPrice">400000+
</QUERY_VALUE>
<QUERY_VALUE name="ListingStatus">|A
</QUERY_VALUE>
<QUERY_VALUE name="ListingID">
</QUERY_VALUE>
<QUERY_VALUE name="ModificationTimestamp">
</QUERY_VALUE>
<QUERY_VALUE name="City">|Watoosee
</QUERY_VALUE>
<LAST_RUN>2010-04-20T17:28:33</LAST_RUN>
</VIELE_BATCH>

If you stare at it long enough, you’ll see that by running this batch job I’ll be running an extract on the Residential property type for Active listings over $400,000 in the city of Watoosee.
The basic premise is that you’ll have to create a batch job file for every query you wish to run.

In my particular RETS, I have 3 price categories, -$300,000, $300,000-$400,000, and $400,000+.
If I want to download all active Residential listings in Watoosee, I have to create 3 batch jobs, one for each price range. Want Commercial Properties in Watoosee? That’s three more files. Yes, you’ll be making lots of batch files. Not only making them, but please name the files something intelligent, as well. You’ll need them named appropriately for adding to your cron script, and for logging and troubleshooting.

You can get started by taking this batch file, however, I recommend running a few real-world extracts from within the VieleRETS interface, this time checking that “Update Batch Job” box in the extract window.

Once the job has completed, navigate to the /vieleRETS/batch_control_files folder via FTP, and grab a copy of the updated batch file so you can get a clear understanding of what naming conventions your RETS server is using for things like price and Status, not to mention how they are spelling the cities in your region.
Armed with this information you can begin caring out your own batch files. Just make sure you save all your batch files to the /vieleRETS/batch_control_files directory for use with CRON

The CRON Script:

Now that you’ve compiled your list of batch files, now you need to create your cron script.
It’s a plain unix file with an .sh file extension.

I called mine rets_cron.sh

Here’s how it looks:

#!/bin/sh
cd /home/your-hosting-account/public_html/vieleRETS-1.1
#residential
php -q ./run_interactive_job.php batch_control_files/residential _1
echo Updated residential_high_1
php -q ./run_interactive_job.php batch_control_files/residential_ 2
echo Updated residential_high_2
php -q ./run_interactive_job.php batch_control_files/residential_ 3
echo Updated residential_high_3

The jist here is that you’re going to list every one of your batch files here, in this format. The “echo” line tells the script to write “updated x” to a log file which gets emailed to me every time the batch runs, you can set this up in cron.

Once you’ve added all your batch files to the script, save it to your web server, you can stick it anywhere you like, but I like to keep it at the root of the directory structure…it makes for less typing when I go to make my cron job.

The CRON JOB

I really wouldn’t recommend running the job more than once a day, even that could be a little excessive, depending on the size of your market. You run the risk of really milking your bandwidth, and if you are in a big market, its going to take a LONG time to download everything, possible degrading server performance during peak hours.

I set mine to run at 3am every weeknight. So the Cron schedule looks like

* 3 * * *

The command run by cron will depend on where you placed your cron script, mine looks like:

/bin/sh /home/your-hosting-account/rets_cron.sh

(note the space between the /bin/sh and the /home)

One thing I’ve done is adjust the time of the cron job to fire off 10 minute from now, that way I don’t have to wait till tomorrow to find out the hard way that I’ve blown something. You can always adjust the schedule of the job again later.

I suppose I’ll be trying to update this from time to time. I’ll try to answer questions if they come up, I’m not a great teacher, but I hope this helps someone hit the ground running. Good luck!