However, with that said, you can probably avoid all of that and just use the correct Visualforce Chatter tag. The only real difference between the standard Chatter feed and what you have in your screenshot above is the button. The Chatter button says Share, not Ask. In this scenario, I would use the
Displays the Chatter EntityFeed for a record or an UserProfileFeed for
a user. Note that Chatter components are unavailable for Visualforce
pages on Force.com sites. Ext JS versions less than 3 should not be
included on pages that use this component.
Note: In the past, I have seen Salesforce Communities used in conjunction with Force.com Sites to provide a public facing and authenticated facing site. In this scenario, this tag will not work on a Force.com Sites page.
For adding the other functionality (Message My Advisor for instance), look into Publisher Actions.
The publisher actions feature lets you create actions and add them to
the Chatter publisher on the home page, on the Chatter tab, in Chatter
groups, and on record detail pages. You can also customize the order
in which the standard Chatter actions appear, including Post, File,
Link, and Poll.
Actions let users do more in Chatter, like create records and log
calls directly in the feed. There are four general types of actions:
create actions, log-a-call actions, update actions, and custom
- Create actions let users create records. They’re different from the Quick Create and Create New features on the home page, because
create actions respect validation rules and field requiredness, and
you can choose each action’s fields.
- Log a call actions let users record the details of phone calls or other customer interactions. These call logs are saved as completed
- Update actions let users make changes to a record from the record’s feed.
- Custom actions are Visualforce pages or canvas apps with functionality you define. For example, you might create a custom
action to let users write comments longer than 5000 characters, or one
that integrates a video conferencing application so support agents can
communicate visually with customers.
For create, log-a-call, and custom actions, you can create either
object-specific actions or global actions. Update actions must be
Note: You may find the Publisher Actions Implementation Guide useful.