Roadmap

Focus Areas

Priority Level (low, medium, high) or Version to aim for (V 2.1, V3, V4 etc.).)

Appearance (design and styling, accessibility, SEO, management and use of graphics, photos, responsive design etc.)

Responsive: Style sheets will be available for all common devices - PCs, tablets, phones, accessibility devices (readers).

Accessible: Entire site will meet current accessibility standards.

Readable: Styling will emphasize ease of reading and viewing.

Graphics: Graphic elements and photos will be handled in a consistent standards-compliant manner.

Have a primary "page image" which can be resized and used in various places. Allow for multiple images on each page. Perhaps allow for galleries attached to the page.

Database (data entry/modification, queries, reports, displays, interaction.)

Searching

Any user can easily make complex, multi-faceted searches.

Share and save searches.

Automatically repeat searches and alert user to results via text/email.

Architecture & Schema

See draft schema here.

Migration from V. 1

Mapping & GIS (a subset of database, but important and significant for attractiveness and usability)

Map any geo data.

Share/save maps.

Maps are one result of a search.

Interoperability (APIs, data import/export, getting along with similar databases, internal & external standardization.)

Security and Authorization (security policies, single sign-in, admin/editor/user/guest levels, password management.)

Webpage

Allow any page to be redirected. Allow for 301 and other such status.

Clean, human-readable and portable URLs.

Adhere to current web standards and use current web technologies, with an eye to future developments if possible.

Responsive theme to run on all screen sizes.

Page Creation, Editing and Workflow

Task assignments, for both editors and others ("research and complete these pages", "here's a list of buildings on Genesee - go take photos and assess building condition")

Editor tools, such as discussion pages, metadata and links to useful resources for editors.

Users can submit new pages or changes to existing pages via a web form. Depending on their editorial level, from anonymous to managing editor, their submission will enter a queue for editing by others.

Social Media integration or internal features (probably just Facebook, Mobile and Twitter, but possibly some internal "social" features.)

Policies & Legal Issues

Copyright, trademark, privacy, editorial.

Consider making it an open source project.

Clarify legal ownership, editorial control and liability.

Hosting & Servers

Minimum performance standards.

Disaster recovery, backup and restore.

Blue-Sky Stuff (Nice to Have, Completely Preposterous and Cool, Waiting For the Next Technology etc.)

Ideas for Version 2.0

• Write python program to data-mine the current wiki site of all data, arranged into arrays
• Create back-end database tables (Buildings, Owners, Categories, etc).
• Write python program to populate new database with existing site info
• New site would have standard stylesheet
• Pages are built dynamically using submissions to the database using PHP forms
  • Current links have a hardcoded search - i.e. Click on Lost Buildings, it generates a page with up to date building list
  • Upgraded search page allows user to select multiple options (i.e. all At Risk, East Side, Broadway Fillmore Commercial Properties built before 1937)
• Authorized users enter/append data through a standardized form page in same format as current template
  • Guests to the site can fill out a similar form, but submit button of this page turns their info into a mailto : webmaster
• Python program to parse, submit, and update InRem auction results as soon as they are available.
• Limitless reporting capabilities (i.e. how many buildings in tax district 4 have gone through 3 auctions before being purchased for > $4,375.45 in the EL council district)
• Track owners and sale prices of auction results
• Addresses all come up in one search result for future mapping feature v3.0
• Could have a trackable section, with dates, on which properties our authorized users are contacting owners or buyers about MarkP January 22, 2013, at 04:21 PM EST
• Persistent URLs: Web addresses will have a human-readable, "clean" form that will be able to persist without too much effort no matter what the web platform or underlying database is. Example: All buildings - www.preservationready.org/Buildings/3435MainStreet, www.preservationready.org/Resources/Links KevinH March 21, 2013, at 10:34 PM EST
• Multi-city/Multi-site option: Sites for individual cities or areas will be accessible from the same database, probably with a subdomain structure to the URL. Example: www.buffalo.preservationready.org, www.niagarafalls.preservationready.org etc. KevinH March 21, 2013, at 10:34 PM EST
• Sign-up for email that notifies someone of a change/addition to a search they like. (example: they are notified each time a commercial building for sale comes up in 14211, each time a preservation agenda is released, or each time we add a note to 595 Fillmore's page)MarkP March 29, 2013, at 08:26 AM EST
• Have a "related buildings" field, to link one building/page to another. For example, Public School 75 is one block from Sacred Heart Church; Ardmore Place adjoins Lafayette High School. Some of this could be achieved with mapping/geolocation functionality, i.e., "other At Risk buildings within .5 miles"KevinH August 08, 2013, at 07:44 PM EST

Must have before initial rollout

• Public comment feature
  • This would be a way for non-editors to comment on a page, probably via email. ["Email about this page" link on every building page is in place]
  • Examples here
  • "Nominate a Building" form to propose new entries.
• Working mobile skin for phones and tablets [in process]
• Install Google Analytics
• Discussion tab for editors
• Page templates [will change as we go along]
• User Authorization
• Section editing [not needed yet]
• Appropriate page headings
• Category links
• Map integration
• Editor menu
• Navigation
  • Sidebar
  • Portal Pages for each main section
• Content
  • Cheat Sheet/Help Page
  • "Getting Started" page for editors and for users
  • Writing and editing guidelines - Style Guide
  • Intellectual property guidelines [in process]
  • Introductory page
  • Page templates [good for now]
  • Building pages
  • Map pages
  • Editorial Discussion pages [no need for template, link is in place]
  • Example pages
  • Contact information

Nice to have

• Nested categories, for reporting, i.e. list buildings At Risk in Allentown.
• RSS feeds
• Breadcrumb navigation
• "I wish this place was..." section for each building (Darren Cotton's suggestion). Another name might be "Possibilities".
• Page watchlists
• Standardized Info-box [this is done via page templates]