Overview on Footer Disclosure Content Variables [Bedrock Clients]

Modified on Thu, 21 Aug at 12:41 PM

Introduction to Dynamic Content Variables in Footers

This feature allows you to dynamically insert personalized content for your office or team into the footer using special variables and macros. By using a specific set of tags and variables, you can display team member information, advisor names, and contact details accurately for each hub. This can be created on a hub level or on global Virtual theme level.

Current Hub Variables

The following variables are available for displaying information related to the current hub (hub owner advisor's and hub office):

{{advisorName}}: Displays the hub owner advisor's full name.
{{officeAddress}}: Shows the complete office address , formatted as "Street, City, State, Postal Code".
{{jobTitle}}: Shows the hub owner advisor's job title.
{{provinces}}: Displays the provincial licenses held by the hub owner advisor.
{{phones}}: Lists the phone numbers of the hub owner advisor's office.
{{facebook}}: Links to the hub owner advisor's Facebook profile.
{{linkedin}}: Links to the hub owner advisor's LinkedIn profile.
{{twitter}}: Links to the hub owner advisor's Twitter profile.
{{email}}: Displays the hub owner advisor's email address.

These variables are inserted into the HTML markup and are automatically populated based on the current office or branch. These variables allow to create a dynamic and personalized footer for each site pages.

Example:

<div class="advisor-info">   <p>Advisor Name: {{advisorName}}</p>   <p>Job Title: {{jobTitle}}</p>   <p>Office Address: {{officeAddress}}</p>   <p>Contact: {{phones}}</p>   <p>Email: {{email}}</p> </div>

Team Member Information

We can also display detailed information about specific team members of the hub using the following variables inside the {{teamMember}} tags:

{{teamMemberAdvisorName}}: Displays the full name of the team member.
{{teamMemberJobTitle}}: Shows the team member's job title.
{{teamMemberProvinces}}: Displays the provincial licenses of the team member.
{{teamMemberPhones}}: Lists the phone numbers of the team member.
{{teamMemberFacebookURL}}: Links to the team member's Facebook profile.
{{teamMemberLinkedinURL}}: Links to the team member's LinkedIn profile.
{{teamMemberTwitterURL}}: Links to the team member's Twitter profile.
{{teamMemberEmail}}: Displays the team member's email address.

NOTE: team member’s index starts from 1. Index cannot be left blank [], be negative or comma seperated multiple values. The order of profile display for all team memebers can be reviewed in team section of My Profile module.

Correct Use of `{{teamMember}}` and `{{end}}` Tags

To display team members' information properly, you need to ensure that the entire HTML markup related to the team member is enclosed within the {{teamMember}} and {{end}} tags. This ensures that any information or layout specific to a team member is hidden if they are not present, or their index is out of range.

Here's a correct example of how to use these tags:

{{teamMember}}[1] <div class="team-member">     <p>Name - {{teamMemberAdvisorName}}</p>     <p>Job Title - {{teamMemberJobTitle}}</p>        </div>  {{end}} {{teamMember}}[2] <div class="team-member">     <p>Name - {{teamMemberAdvisorName}}</p>     <p>Job Title - {{teamMemberJobTitle}}</p>        </div>  {{end}}

Important: If you place any markup outside the {{teamMember}} and {{end}} tags, that markup will remain visible even if no team member is available for the given index. This can result in empty sections or unwanted content on the page.

Here's an incorrect example where leftover markup could cause issues:

<div class="team-member">     {{teamMember}}[1]     <p>Name - {{teamMemberAdvisorName}}</p>     <p>Job Title - {{teamMemberJobTitle}}</p>     {{end}} </div>

In this case, the <div class="team-member"> is left outside the {{teamMember}} tags, which can result in an empty container being displayed if no team member is available.

Handling Out-of-Range Team Members

If you try to display a team member with an index that is out of range (i.e., the team member does not exist for the current hub), that part of the content will be skipped. This prevents empty or irrelevant content from being displayed. The tags ensure that if the {{teamMember}} and {{end}} tags are correctly used, the extra markup is hidden.

Footer Content and Virtual Theme Feature

When using footer content from the virtual theme, any users with an index that is out of range for the current hub will not appear on advisor sites if the {{teamMember}} and {{end}} tags are used correctly within the markup.