Pay slips
Compensation data should not stay readable in inboxes after the delivery step is complete.
For HR teams
This sample page demonstrates how the new single-page runtime can support HR-focused landing pages in English.
Why it matters
A secure link replaces one step in the workflow and removes the highest-risk part: readable files sitting in inboxes and third-party platforms.
This is one of six sample single pages added to prove the first runtime slice. The content is deliberately simple and exists to exercise the new content directory, wrapper, and route resolution.
A production version could focus on secure pay slip delivery, compensation updates, contract amendments, and other employee documents that should not remain indefinitely in email inboxes.
Use cases
This section is still placeholder content, but it already maps well to a real HR-focused landing page structure.
Compensation data should not stay readable in inboxes after the delivery step is complete.
Changes to employment terms can be shared through a more controlled workflow than open attachments.
Sensitive salary-related messages benefit from one consistent and auditable delivery pattern.
FAQ
Because it proves the runtime model first: content loading, slug resolution, SEO metadata, and page rendering all work before editorial refinement.
Yes. It includes title, meta description, keywords, canonical URL behaviour, and an OG image.
Yes. Blog posts still use the blog wrapper, while these documents use the dedicated page wrapper.
Yes. This first step keeps the system stable by reusing existing sections, then expands from there.
Next step