Skip to main content

Community

Description​

Community pages (as well as child plan and spec pages) should be dynamically created.

When User creates a new Community this should also create a new front-end page automatically under corresponding division.
For example:
.com/new-homes/Austin/[city_name]/[Community_name]/[community_floor_plan_name]/[spec_home_name]

Community Pages should be auto-grouped in Pages/Nav tab, under division/city (and can’t be re-arranged).

Page visibility should be based on the Community status.
If active - page is visible.
It Inactive - page should also not be visible (hidden/redirected)

When user sets community to Inactive - this should also redirect community page to division page.
For example this:
.com/new-homes/austin/[city_name]/[Community_name]/[community_floor_plan]/[spec_home]
Redirect to this:
.com/new-homes/austin

Components:​

Community page will have a set of pre-defined, fixed components (which user can't change/edit/remove), shown in prototypes.

  • Breadcrubs
  • Info Header section
  • Navigation Tabs:
  • Overview
  • Floor Plans (if any)
  • Spec Hones (if any)
  • Community Map (if any)
  • Directions

++++

  • Editable section where user can select additional fixed content components allowed by CMS.