A feed that only holds posts is a feed about talking. A community that also runs a job board, a directory, a course catalogue and an events calendar has a lot more happening than talk, and most of it never reaches the place members actually open every day.
BuddyNext Pro closes that gap with a bridge for each of four plugins: Career Board, Listora, Learnomy and Eventonomy. When something happens in one of them, the bridge writes a card into the community feed. This post is a plain inventory of those cards: what each says, when it shows up, and when it goes away.
The cards at a glance
Each card has a line of text and a link back to the plugin that owns the thing, and most carry a badge.
| Plugin | Card says | Shown as |
|---|---|---|
| Career Board | posted a new job | Job Listing badge |
| Career Board | is open to work | Open to Work badge |
| Listora | added a new listing | Listing badge |
| Learnomy | completed a course | Course badge |
| Learnomy | earned a certificate | Course badge |
| Eventonomy | scheduled an event | Event card |
| Eventonomy | is attending | Event card |
Everything below needs the matching plugin installed alongside BuddyNext Pro. The bridges read what those plugins already do and link back to them.
Jobs and open-to-work
A job card appears when a job is published. It carries the job title and a short excerpt, plus the featured image when the job has one, and it links out to the job itself.
The card follows the job. If the job moves to pending review, draft, rejected, trashed, expired or closed, the card is withdrawn, so a closed vacancy never keeps a live card in the feed. Publish it again and the same card returns, with its original date and any comments still attached, rather than surfacing as a fresh post.
Resumes work the other way round, because the member decides. A card saying “is open to work” appears only when the member makes their resume public, and it disappears when they switch that off. The badge is different from a job’s on purpose, so a candidate announcing availability is never mistaken for a vacancy.
Listings
A published listing posts “added a new listing” with its title and an excerpt, plus a cover image when there is one. Edits to the listing refresh the card. Anything other than published (draft, pending, expired, trashed) withdraws it, and republishing restores the same card with its comments. A listing that is deleted outright has its card removed.
Courses: cards about the learner
The Learnomy cards are about people, not the catalogue. A learner finishing a course posts “completed a course”, and a learner earning a certificate posts “earned a certificate” with a link to the certificate’s public verification page.
Each learner gets their own card. That sounds obvious, but a card keyed only on the course would show just the first person to finish it, so the link carries the learner’s identity to keep them apart.
The cards stay honest as things change:
- If a course is unpublished, every card for it is withdrawn, and they come back when the course is published again.
- If a course is deleted, its cards are removed.
- If a certificate is revoked, its card is removed. An expired certificate has its card withdrawn.
Events: the richest card
Eventonomy’s card is the only one that is more than a label and a link. It shows the event cover (or a placeholder) and a month-and-day date chip, with a live count of people going. While the event is upcoming, members who are allowed to RSVP get Going and Maybe toggles right on the card; everyone else sees a plain link to view the event.
Two cards can exist for one event. The organizer’s reads “scheduled an event”. Each person who RSVPs “going” adds an “is attending” card, and changing their answer away from going retracts it. Only public, published events get cards. If an event is cancelled, unpublished or edited so that it is no longer public, its organizer and attendee cards are withdrawn, and they come back with the same comments if the event goes live again. Deleting an event removes them for good.
Where each card sends people
A card is a doorway, not a copy. Each one links back to the plugin that owns the thing it describes, so the details stay in one place.
- A job card goes to the job, and a resume card to the resume.
- A listing card goes to the listing’s own page.
- A course completion card goes to the course, with a link specific to that learner, and a certificate card goes to the certificate’s public verification page.
- An event card goes to the event, and an “is attending” card is tied to the person who registered.
That is why the cards stay short. A visitor who wants the full story follows the link, and the feed does not become a second copy of every page.
It also means you never update anything in two places. When a job, listing or event is edited and saved, its card is refreshed from the item, so the title, the excerpt and the cover image in the feed follow the source. A member who corrects a typo in a job title does not leave an old headline behind in the feed.
Cards keep their history
A card is not recreated every time something changes. When a job, listing, course or event stops being live, its card is withdrawn, which hides it but keeps its original date and any comments members left. Publish the item again and the same card returns, in its original place, with the comments still attached.
This matters more than it sounds. Without it, a job that closes and reopens would surface as a brand new post, and anyone who commented on it would lose the thread. The cards that are removed outright are the ones whose subject is permanently gone: a deleted event, a deleted course or a revoked certificate.
You control each one
Each bridge has its own switches in BuddyNext’s integration settings, covering the parts it uses, such as navigation, feed and search. The feed switch decides whether that plugin writes cards at all. Turn it off for Learnomy and new completions stop appearing, while the plugin itself carries on as before.
That matters more than it first appears. A busy job board can post cards faster than a discussion community wants to read them. The right answer is often to leave the feed switch off for the noisy source and keep it for the quiet ones.
A simple way to decide is to keep the feed on for the cards members enjoy seeing about each other, such as a finished course or an RSVP, and think harder about sources where a few accounts post often. Try it with a test account and one real item from each plugin before you open the doors, so you see exactly what members will see.
If you find the whole feed getting crowded, that is a structure question as much as a switch question, and why communities need Spaces covers it.
What the cards are not
A few limits are worth knowing before you plan around this.
- The cards are summaries. Applying for a job or finishing a lesson happens in the plugin that owns it. The one exception is the event card, where the RSVP toggles live on the card itself.
- A card exists only while the thing it describes is live. That is deliberate, but it means the feed is not a permanent history of everything that ever happened.
- Turning a feed switch off stops new cards. Set it up before you launch, not after the feed has filled.
Check it before you launch
Cards are easy to test, and the test shows you exactly what members will see.
- Create or publish one real item in each plugin you run: a job, a listing, a course and an event.
- Open the community feed as an ordinary member and look for one card per item, with the right badge and wording.
- Follow each card’s link and confirm it lands on the right page.
- Unpublish one item and check that its card disappears, then publish it again and check that the same card returns.
- Switch one plugin’s feed switch off and confirm it stops adding new cards.
Putting it together
On a site that runs all four plugins, a member’s feed can show a colleague’s new job post, a business added to the directory, a classmate finishing a course and a friend going to next month’s meetup, in one scroll, alongside ordinary conversation. That is the point of the bridges: the members who do things on your site are visible to each other without anyone copying links into posts by hand.
If you want to read the detail for one of them, the integration pages cover Career Board, Listora, Learnomy and Eventonomy. Each plugin also has its own site: WP Career Board, Listora, Learnomy and Eventonomy. The bridges ship in BuddyNext Pro, and the pricing page shows what that includes.