What this skin object does
Upendo OpenContent Helper is a website skin object and API helper for OpenContent templates and other front-end integrations. Add it to a skin when a page needs OpenContent SEO tags in the HTML head. The installed package also exposes small, reusable API endpoints for events, galleries, business directories, client dashboards, membership dashboards, and template usage reports.
This is not a content-management screen. It does not replace the module that stores events, gallery images, business records, memberships, or templates.
What the skin object does on each page
When the skin object is present, it reads the current page and portal context and adds OpenContent metadata and link tags to the page head. It also applies the shared SEO rules used by runsonUpendo.
If the page has no usable header, portal settings, or trusted site authority, the helper skips the part it cannot safely apply. Errors are written to the website exception log instead of being shown as page content.
The API base is:
/DesktopModules/OpenContentHelper/API/{Controller}/{Action}
Examples:
/DesktopModules/OpenContentHelper/API/Gallery/Images
/DesktopModules/OpenContentHelper/API/Events/Sitemap
/DesktopModules/OpenContentHelper/API/BusinessDirectoryLookup/LookupCategories
The API uses the current website portal. Public endpoints are portal-scoped and do not let a caller select another portal by changing a query value.
Permission levels
- Anonymous visitors: Can use public gallery, event, business-directory lookup, and business-directory sitemap endpoints.
- Authenticated users: Can use the membership dashboard endpoints. The billing portal action also requires a valid anti-forgery token.
- Users with module View permission: Can use the client dashboard summary and the Template Usage API gate.
- Elevated users or users with module Edit permission: Can use the Template Usage reports, inventory, cleanup candidates, and CSV export.
- Superusers: Can use Template Usage with the instance-wide scope and select another website. Superuser status does not make public APIs private or grant management actions in this skin object.
Public integrations
Events
GET /Events/Calendar?slug=event-slug returns an .ics calendar download for one event.
GET /Events/Sitemap?detailPagePath=/events returns an XML sitemap for upcoming events.
Gallery
GET /Gallery/Images lists published images with search, category, tag, location, sorting, and paging filters.
GET /Gallery/Image?slug=image-slug returns one published image.
GET /Gallery/ImageById?id=123 is a defensive ID lookup; slug lookup is preferred.
GET /Gallery/Categories and GET /Gallery/Tags return only categories and tags used by published images.
Business directory
GET or POST /BusinessDirectoryLookup/LookupCategories returns active categories for a Select2-style picker.
POST /BusinessDirectoryLookup/GetBusinessesByCategories returns businesses for selected category IDs.
GET /BusinessDirectorySitemap/Sitemap returns the public company sitemap as XML.
Authenticated integrations
GET /ClientDashboard/GetSummary returns the current portal's client dashboard summary.
GET /MembershipDashboard/GetMyDashboard returns the signed-in member's dashboard.
POST /MembershipDashboard/CreateBillingPortalSession creates a Stripe billing portal session for the signed-in member.
The membership controller uses the current signed-in user and portal. A portalId query value must not be treated as a way to read another portal.
Template Usage
Template Usage helps staff inspect OpenContent template inventory, usage, and cleanup candidates. It supports the current website, all websites for superusers, or a selected website for superusers. Reports can be exported as CSV.
The cleanup report is a report only. Review the candidates and confirm the source files are not needed before removing anything through the normal website or deployment process.
Safe use
- Keep the skin object installed on pages that need its SEO head injection or APIs.
- Do not put secrets, Stripe keys, or private data in OpenContent templates or client-side code.
- Do not expose authenticated dashboard responses to anonymous JavaScript.
- Use published data endpoints for public pages; do not add management actions to this helper.
- Test API URLs on the correct portal and with the intended permission level.