Quadrant Homes

Get Started. It's Free
or sign up with your email address
Rocket clouds
Quadrant Homes by Mind Map: Quadrant Homes

1. Mobile

1.1. ( www.dol.wa.gov/m/ )

1.1.1. General flow and feel of site to match

2. Desktop

2.1. General Look/Feel

2.1.1. Template for search page

2.1.1.1. Map Click-able to link to Community Page

2.1.2. Template for search results

2.1.2.1. filterable by Community, Price Range, Number of Bedrooms, Number of Bathrooms, Agent

2.1.3. Template for single home page

2.1.4. Template for Non-Property (other info) pages

2.1.5. Template for Community pages

2.1.5.1. Map Click-able to link to single Home Page

2.1.5.2. PDF for Community MAP

2.1.5.2.1. ??? When /Where is this coming in ???

2.1.5.2.2. ??? How dependable is it ???

2.1.5.2.3. ??? Should this be "produced via Database" rather than displayed via PDF ???

2.1.6. Facebook to sidebar

2.2. WP database

2.3. Property Database

2.4. ??? How to build URL based on search results ???

2.4.1. qh.com/[Community-Name]/[Plan-ID]/[Home-ID]

2.4.2. qh.com/comunities/[Community-Name]

3. Additional Sites

3.1. Evoke

3.1.1. QH Upper end

3.1.1.1. Non-Related to QH Main site

3.1.1.1.1. Will use Property Database

3.1.1.1.2. Will have own WP Database

3.2. Urban

3.2.1. QH ???

3.2.1.1. Non-Related to QH Main Site

3.2.1.1.1. Will Use Property Database

3.2.1.1.2. Will have own WP Database

3.3. QH Reviews

4. Outbound Property Info

4.1. BDX

4.1.1. XML File

4.1.1.1. ??? Figure out syntax for BDX ???

4.1.1.2. ??? Setup Cron-job to send XML file at least daily (check with BDX to find out how often they can accept the file) ???

4.1.1.3. Only include "current" listing for BDX (none that have been pulled or marked for removal)

4.2. MLS

4.2.1. ?????

4.3. Any Other 3rd party

4.3.1. ?????

5. Property Database

5.1. Back-end interface

5.1.1. Internal Reports

5.1.1.1. Client states no reports will be needed

5.1.1.1.1. Each top-level page with in the db interface will have it's corresponding reporting

5.1.2. Input Interface

5.1.2.1. Add A Community

5.1.2.1.1. Choose Website (QH/Evoke/Urban) for community (allow more than 1)

5.1.2.1.2. Uploads

5.1.2.1.3. Data to be stored

5.1.2.1.4. Assumptions MADE

5.1.2.2. Add A Plan

5.1.2.2.1. Uploads

5.1.2.2.2. Data to store

5.1.2.2.3. Assumptions MADE

5.1.2.3. Add A Home

5.1.2.3.1. Choose the Community that this home is in

5.1.2.3.2. Choose the Plan the home is based on (only 1)

5.1.2.3.3. Assumptions MADE

5.1.2.4. Add A Sales Office

5.1.2.4.1. Will need to set up preview from back-end ( This should be all of the sales office info display neatly (with edit buttons next to each element))

5.1.2.4.2. Choose the community that the sales office serves (ONLY 1)

5.1.2.4.3. Data to be stored

5.1.2.4.4. Assumptions MADE

5.1.2.5. Add An Agent

5.1.2.5.1. Choose the sales office that the agent serves (allow more than 1)

5.1.2.5.2. Uploads

5.1.2.5.3. Data to be stored

5.1.2.5.4. Assumptions MADE

5.2. Database Structure and relationships

5.2.1. Link Here to DB design

5.3. SECURITY

5.3.1. BDX downloads and host images and videos (no need to allow access to properties db)

5.3.2. Any additional sites needing images/video will need to be provided with an XML file and ftp-get from a url. ( No access to properties db)