Content, Contacts, and Views

Content, Contacts, and Views

Content Creators use links on the Content and Contacts menu to access Brick River Views.

A View is a display that defines, sorts, and filters records in a way that best supports the content management needs of Users.

 Virtually all dynamic data in Brick River is stored as either a Content or Contacts record.

Content records represent ideas and items of information that your site needs to present to your audience. Content records may include news articles, meeting minutes, blog posts, photo galleries, event descriptions, barbecue recipes, etc.

Contacts are records that represent a person, place, or thing that your site needs to keep track of. Contact records may include employees, volunteers, event registrants, conference rooms, company cars, committees, sponsors, etc.

Click any View link on the Content or Contact Menu to open a list of records in the View Window.

Example: the Blog Posts View Window

1 Create a New record.  Click to open a new record in the Content Editor window.

2 Change the fields displayed for existing records in the View window.  The example above displays the Title, Written Date, First Name, and Last Name fields.  This display is determined by the View design and cannot be permanently changed in this window.  It can be temporarily changed for the current session by clicking the Fields button and changing the selection and order of fields displayed.

3 Download the content of the View to a spreadsheet or other file type.

4 Access links to Find Duplicate records, Publish Data, and access Developer Info for the View

5 View Search Feature - each View defines a set of Fields to be included in the dynamic search field.  For example, if the First Name and Last Name fields are defined as search fields - typing aud in the search field would locate records linked to Audery Zabor, Maude Finley and Harold Baudroin.   Common criteria may be saved and chosen from the Saved Searches drop down button.

6 View Filter Features - Each View can be customized to include one or more filter fields. 

7 Links to existing records - Click on any link for an existing record to open it in the Content Editor window.

8 Expand / Contract the display of Filter fields - Collapse the display of fields for a full width view of existing records.

Example: a Blog Post Opened for Editing in the Content Editor

1 Save Options Button - Click to save, or open the drop down list to Save and Return, or Save Current Changes to a new copy of the existing record

2 Return to View window

3 Actions - Click to open a list of Action links.  The link to delete the current record is always available here.  Developers may customize this button to display additional Action links.

4 Highlight web fields - Depending on how Site Pages are coded, new Content may appear on the Site as soon as records are saved.  Highlight web fields displays a list of all record fields that will potentially display on Pages.  This provides helpful reminders if, for example, a User forgets whether the summary field is included in the display of Blog Posts on the website.

5 Jump to a field - type a field name to place the cursor immediately in that field

6 Content Fields - Content fields will vary depending on the nature of the Content or Contacts.  Developers have unlimited power to define content types and control the display and behavior of fields in the Content Editor window.  Developers may also set field attributes such as default values, allowable data types, required data entry, etc.  Fields may be organized into collapsible 'Field Sets' (such as 'Article' in the example above) to make long data forms more manageable.

7 Plain Text Fields - many fields will only accept straight text entry and allow no styling of text or emebedded objects.

8 HTML encoded Fields - Fields defined to allow encoded HTML - display as WYSIWYG fields.  They may contain styled text, images, links and embedded videos.  These fields always display toolbars for styling text and performing other actions.  Entering WYSIWYG content is documented here.

User and Group Permissions

Access to Views is controlled by User and Group permissions.  Users with less than Administrator permission must be specifically granted permission to see the Content and Contacts Menus.  Additional permissions control which Views are displayed on each menu, and, in some cases, which fields on each record are displayed for editing.

Learn more about Users and Groups here.

Custom Views, Content, and Contacts

Developers can create custom Views to define virtually any kind of Content or Contacts.  If your organization uses 'Volunteers' to perform 'Service Projects' - a developer can easily create a new Contact Type - 'Volunteers' and a new Content Type - 'Service  Projects'

Creating Custom Views is documented thoroughly in the Developer's Guide here.


Schedule a demo and see how easy it can be

Give us 15 minutes to hear your situation and share our solution.

Schedule a demo