Content Editor Guide
Creating a New LCS Microsite
All examples use The Delaney at Georgetown Village (Georgetown, TX), the first real community microsite.
Recommended best practice: instead of building a site from scratch, duplicate an existing sample microsite. This copies over the complete structure of pages, navigation headers, footers, and form sections, so you only need to update the branding and content for the new community.
Steps
- Duplicate the sample site
- Base template
- Reassign pages
- Template widgets
- Form pages
- Content
- Roles & permissions
- Review
- Go live
1 - Duplicate the Sample Site (In Process of Development)
- In the top-left corner of the Sitefinity admin panel, click the current site name and select Manage Sites.
- Click Create a site.
- In the Site properties window, fill in:
- Name - [Community name]
- Protocol - https://
- Domain - The full detail URL path of the community from the main site, e.g. www.lcsliving.com/location-finder/texas/georgetown/the-delaney-at-georgetown-village
- ✅ This site is in process of development - This checkbox MUST be checked.
- Testing domain - e.g. dev/the-delaney-at-georgetown-village. Use this address to view and review the site while it is being built.
- Select Duplicate pages and settings from existing site... and choose The Delaney at Georgetown Village.
- Click Continue.
- On the Configure modules screen, enable these modules and set their sources (providers):
- Libraries - Default Libraries and a new provider for this site ([Community name] Libraries)
- Events - new provider for this site only ([Community name] Events)
- Media Galleries - new provider for this site only ([Community name] Media Galleries)
- Articles - new provider for this site only ([Community name] Articles)
- Testimonials - new provider for this site only ([Community name] Testimonials)
- Staff - new provider for this site only ([Community name] Staff)
- Communities - ⚠️ Default only. Do not use a new provider.
- Leave unchecked (not used): Blogs, Vendors, News, Lists, Schemas, GenericContent, Navigations
- Click Save changes.
⚠️ Communities is shared with the main site. The microsite uses the Default Communities provider, so it works with the same Community items as the live main site. Any change you make to the Community item is published on the main site as well. Edit the Community item carefully, and only change what is correct for both sites.
⚠️ The site must stay "in process of development" until go-live. The real domain can be set from the start. It does nothing on its own while the Community's Has microsite checkbox is unchecked: the main site keeps serving the community's detail page. Do not check Has microsite at this stage.
2 - Create a Dedicated Base Template
- Switch to your new site using the site selector in the top-left corner.
- Go to Design → Page Templates.
- Find the base template that was duplicated from the source site.
- Click its actions menu and select Duplicate.
- Give the new template a clear, distinct name: [Community name] Base Template.
- Important: Open the settings of the original template and remove the new site from its site sharing so it cannot be accidentally applied here.
3 - Reassign Pages to the New Base Template
- Go to Pages in the new site.
- Select your pages (or open each page → go to Actions / Title & Properties).
- Under the Template selector, choose [Community name] Base Template.
- Click Save changes.
4 - Configure Widgets in the New Base Template
Go to Design → Page Templates and open [Community name] Base Template for editing.
Brand Colors (MicrositeTheme widget)
- Locate the Microsite Theme widget at the top and click Edit.
- Choose the colors for this community (Primary, Secondary, and Accent).
- Click Save.
General Community Scripts (MicrositeScripts widget)
- Find the Content list widget with the Details.Communities.MicrositeScripts view and click Edit.
- Under Which items to display, select Selected items and choose the new community.
- In Advanced settings, ensure the display mode is forced to Detail (ContentViewDisplayMode set to Detail), so Sitefinity directly renders the detail view instead of a list.
- Click Save.
Logo and Navigation
- Update the header logo image widget with the official logo of the new community.
- Click Publish on the template.
5 - Configure the Contact Us (or Any Other Form) Page
On any page containing a form (such as the Contact Us page):
- Open the Contact Us page for editing.
- Locate the Content list widget using the Details.Communities.MicrositeFormScripts template (placed next to the form).
- Click Edit.
- Under Which items to display, select Selected item and pick the new community.
- In Advanced settings, ensure the display mode is forced to Detail (ContentViewDisplayMode set to Detail), so Sitefinity directly renders the detail view instead of a list.
- Click Save and Publish the page.
6 - Update the Content
Go through every page of the new site and replace the sample content (texts, images, galleries, testimonials, floor plans, links) with content for the new community. Publish each page when done.
7 - Configure User Roles & Restrict Site Permissions
This can be done during development, so the community editor can help fill in the content. It ensures a community editor only has access to their specific microsite and cannot view or edit other sites in the project.
Create the Role & User
- Go to Administration → Roles → click Create a role (e.g. [Community name] Editors).
- In Administration → Users, assign the user to this role and ensure "This user can access site backend" is checked.
Grant Permissions for this Microsite
- Go to Manage sites → click Actions on the new microsite → Set permissions.
- Click Break inheritance.
- Grant access to the [Community name] Editors role for Access the site and Configure this site modules.
Deny Access to Other Sites (Crucial)
- In Manage sites, click Actions → Set permissions on the main site (and any sister sites).
- Click Break inheritance (if not already broken).
- Under Access the site, click Change → check "Explicitly deny this to selected roles and users" → select the [Community name] Editors role → Done.
Set Page Permissions
- Switch to the microsite → go to Pages → click Permissions for all pages.
- Click Break inheritance → grant the [Community name] Editors role permissions to View, Create, Modify, and Delete pages.
8 - Review Before Go-Live
Open the microsite on its testing domain and check:
- ☐ All pages are published and use [Community name] Base Template.
- ☐ Brand colors and logo are correct.
- ☐ No sample content is left (texts, images, phone numbers, addresses, links).
- ☐ Forms submit correctly and are linked to the new community.
- ☐ Footer license and community scripts show the new community's data.
- ☐ Header navigation and footer links work.
9 - Go Live (Last Step)
Take the Site Out of Development
- Go to Manage Sites → open the settings of the new microsite.
- Check that Domain is the full detail URL path of the community from the main site.
- Uncheck This site is in process of development.
- Click Save.
Enable "Has microsite" on the Community
- Go to Content → Communities.
- Find and open the community for editing.
- Locate the Has microsite field (checkbox) and check Yes.
- Click Publish.
Why this is the last step: once this checkbox is checked, the main site no longer resolves the community's default detail page, and all links across the main site and the Community Finder point visitors to the microsite. Checking it before the microsite is ready breaks the live community page.
Verify on the Live Site that the community's detail URL opens the microsite.
Rollback: if something is wrong after go-live, uncheck Has microsite on the Community and Publish, then check This site is in process of development on the microsite again. The main site's detail page will serve the community again.