Real Estate Website

  • web design for a salt lake city based ski company
  • web design for a salt lake city based ski company
  • web design for a salt lake city based ski company

Strong Connections Functioning Together

Talented programmers who specialize in the MySQL relational dataBase management system, API tools, and front-end languages worked together to create a real estate website. Pixelcrane's experience in the real estate web design field is extensive.


  • Skills:

    • Web Development
    • WordPress CMS
    • API Integration and Data Formatting
    • Custom WordPress Plugin Authoring
    • WordPress Plugin Moidfication

The Short Version

API integration for a real estate website.

The Long Version

This is a website for a Park City real estate agent. About 5 years ago, she already had branding and print advertising – but no online presence, and a limited budget. Be warned. The term “limited budget” for a Park City real estate agent is a very subjective term.

In the beginning, we started with a premium WordPress theme, but I knew we needed to manage listings dynamically through the Park City Board of Realtors database. As this was my first time managing the integration of an API, it took a little time to identify the correct resources. Ater I partnered with the right colleagues, the rest of the configuration and formatting went very fast.

My client’s listings on the site are displayed via a custom plugin which grabs a home’s unique MLS number. This allows us to quickly add and delete properties as well as control the order in which they are shown. Homes for sale can be displayed by neighborhood because the data feed includes a hook for that attribute. Users can search for homes using filters for location, price, etc. and the results are dynamically displayed through the data feed/API.

Another upgrade to the site was installing, configuring, and customizing a calendar plugin for Park City events. My client wanted additional control over how data from the plugin was presented. The default display for an event that took place over 2 or more days was was originally displayed as…

[startingDay] [startingMonth] - [endingDay] [endingMonth]

In plain text it would look like: “December 26 - January 15”

My client wanted dates like this to be formatted like “Through January 15” at 00:00:00 of the the start date. We took apart the plugin and added the functionality the client desired.