rendering-accessibility
Implement and maintain post rendering, syntax highlighting, and accessible semantic output behavior for this blog.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Rendering Accessibility
Scope
Own presentation behavior for post and archive rendering.
Required Rules
- Use the central renderer (
App\\Markdown\\MarkdownRenderer) for post body rendering. - Keep Tempest Highlight CommonMark extension integrated for fenced and inline code.
- Preserve semantic, accessible output structure.
- Keep highlighted token contrast and code block readability intact.
- For sample content fixtures, use realistic fictional topics, distribute markdown feature coverage, include representative code fences/inline code, and avoid benchmark labels unless requested.
- Avoid unsolicited visual redesign.
Workflow
- Change renderer/highlight integration in minimal slices.
- Verify rendered output remains predictable and accessible.
- Validate highlight readability after style changes.
- Follow
delivery-standardsquality gates and reporting.
References
-
laravel-bladefor Blade template/component conventions.
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!