Feature requests

Add a new page type, similar to the “Committees” page, where a community can list available activities and clubs, along with their current members.

Please add support for conditional questions in surveys and forms. This feature would allow additional questions or fields to appear based on a respondent’s answer to a previous Yes/No question. Current Limitation At present, all survey questions are displayed to every respondent, regardless of how they answer earlier questions. This makes it difficult to collect follow-up information only when it is relevant. For example, our association recently created a survey asking property owners whether they were willing to have their names included with a community letter. The initial question was: “Are you willing to have your name included as a XYZ property owner supporting this letter?” Possible responses: * Yes * No We also needed to collect the respondent’s name or names and lot number, but only from owners who answered Yes . Because conditional logic is not currently supported, the name and lot-number fields had to be displayed to everyone, including respondents who selected No . Requested Functionality Please add the ability to configure conditional display rules for survey questions and form fields. A survey administrator should be able to specify rules such as: * Show Question 2 only when Question 1 is answered Yes . * Show Question 3 only when a particular multiple-choice option is selected. * Hide or skip follow-up questions when they do not apply. * Make a conditionally displayed question required only when the condition is met. Example Question 1: Are you willing to have your name included with the community letter? * Yes * No If Yes is selected, display: Question 2: Please enter the name or names that should be included. Question 3: Please enter your lot number or numbers. If No is selected: Questions 2 and 3 would remain hidden, and the respondent could submit the survey without completing them. ## Suggested Administrative Options When creating or editing a question, the administrator could select: Display this question when: * A selected question * Equals or does not equal * A selected response For example: Display this question when Question 1 equals “Yes.” It would also be helpful to support multiple conditions using AND/OR logic in future versions. Benefits Conditional survey logic would: * Make surveys shorter and easier to complete. * Prevent respondents from seeing irrelevant questions. * Reduce confusion over whether follow-up fields are required. * Improve the quality and accuracy of collected information. * Allow associations to create more professional surveys, applications, registrations, and request forms. * Reduce the need for administrators to manually review and reconcile unnecessary responses. This functionality would be valuable not only for community surveys, but also for architectural requests, event registrations, volunteer sign-ups, maintenance reports, permit applications, and other association forms.

Implement collapsible sections for each committee on the “Committees” page type. Users can expand these sections to view descriptions and members, reducing the need to scroll and making it easier to locate a specific committee.

When creating a survey, add a new question type that would allow members to select multiple answers from a list of preset options. Original post: Sometimes surveys with refilled answers could be even better when respondents are allowed to select multiple answers, for example when the answers are dates. Could an option be provided to allow for that as a survey parameter?

Allow admins to specify to whom a survey is available to, instead of having it always be available to all members. This would function like the page restrictions.

Implement an official online voting feature.

Include the ability for members to attach files to posts on a "Forum" page. ORIGINAL POST: Allow additional attachment types such as video in the Forum page. This would allow users to attach items such as security footage that was captured for a discussion chain.

For survey questions that require respondent to pick from a list, make "Choose one" the default option for the first answer. Otherwise, the first item in the list becomes the default and, therefore, may be inaccurately overweighted in responses.

Provide admins with the ability to move around where items are located on the homepage. This would apply to the rotating photos, news, and upcoming events.

Our current objective is to create and improve upon the world's greatest community website builder. Over the years, we've had many communities request features that fall under the umbrella of resident or community management software. This is a separate industry from the one our company falls into, although we do see the similarities. There are a number of companies that provide this type of software, and they generally don't compete with website builders. Some examples of features that fall under management software include: Task/project tracking, usually tied to form submissions (maintenance requests, work orders, ARC requests, etc.) Reservation system, usually for amenities Resident billing (assessing fines, tracking payments made outside the website, sending notices of payments due, due dates, late fees, etc.) Financial tools (accounting tools, vendor payments, etc.) Document storage (bulk uploading/downloading of files, data retention policies, etc.) Anonymous violation tracking While management software is on our radar, it's not the industry we're currently in. Still, we'll use this post to gather thoughts, ideas, and comments from customers in case we decide to head that direction in the future.