We added many improvements to our Design System (DS), along with progress on the Community Solution.
Design System updates
Updated, organized, and extended the complete DS, with a strong focus on the DS core.
Refined the core component structure and split it into clear categories: core, customizable graphics, navigation, section elements, sections, grids and layouts.
Organized solution-specific components (Community, Marketplace, Course, Documentation, Admin)
Reviewed and moved all the general-purpose components into the core set.
Added customizable vector graphics and vector backgrounds that adapt automatically to the given color scheme or branding using Figma variables.
Extended section elements with several new components and their variants, such as: content types, card types, and dashboard components.
Extended the section library with new section types, all built from the section elements above.
Planned
Extend the DS color modes with a high-contrast, accessible mode. Switching to this mode will ensure compliance with accessibility standards.
Community Solution
Ideated and iterated concepts with Figma Make.
Ideated dashboard interfaces for practice-sharing and knowledge-base community types. Designed the UI for both regular users and newcomers.
Created the necessary dashboard and navigation components and integrated them into the core.
University Course Lesson
We held a lesson at the University of Szeged, as part of the Exploring PaaS for Dynamic Online Ventures course by pOS.
The session covered topics such as:
general UI design principles
automation and the technical depth of UI design with Design Systems
accessibility
how we integrate AI into everyday design work at platformOS
The presentation, in Hungarian, is available here.
UX: From Strategy to Experience: The Next Phase of the Community Solution
Following the completion of the foundational UX framework, the core landing page re-design of the community solution is finalized, and the dashboard concept has been refined into a clean, scalable structure that supports both first-time and returning user journeys.
Our focus has now shifted to building a universal core flow. This next phase brings the Community Solution from a conceptual framework into a tangible, high-fidelity prototype that highlights its modular, business-ready design.
We’re prioritizing a general, reusable flow that most communities share, so clients and partners can instantly see the core value: why to join, how to contribute, what’s happening now, and what outcomes they can drive on platformOS community solution. This aligns with best-practice community patterns around clear purpose, structured onboarding, engagement rituals, and measurable results. Our UX team is now working on an interactive prototype, which will demonstrate key flows and engagement mechanics. In parallel, we’re integrating AI-enhanced features that elevate user experience through intelligent summaries, contextual recommendations, and content insights, showcasing how AI can drive both efficiency and engagement within community interactions.
By combining human-centered UX with adaptive AI capabilities, we’re setting the stage for a solution that’s not only flexible and fast to launch, but also smart, scalable, and ready to evolve with our clients’ or partners’ community goals.
The Writing Docs for AI series explores how artificial intelligence is reshaping the way we create, structure, and maintain technical documentation. The series highlights how documentation now serves both human readers and AI systems, and how technical writers can adapt their workflows, tools, and style to meet the needs of both audiences.
Through four interconnected articles, the series builds a complete picture: from understanding AI as a new reader of documentation to integrating it as an active collaborator in writing and review processes. It concludes with a practical checklist of actionable best practices.
1. Writing for Humans and Machines: Why Docs Now Serve Two Audiences
Explores how documentation today must meet the needs of both human readers and AI systems such as chatbots, search, and large language models. Discusses the dual audience problem and how writers can create content that is both readable and parsable.
2. Structuring Documentation for AI Comprehension
A practical guide to organizing documentation for AI. Explains how structure helps both users and machines understand, navigate, and reuse content effectively.
3. From Consumer to Collaborator: How AI Supports Documentation Teams
Examines how AI tools are becoming active participants in the documentation process. Covers practical ways AI assists with research, editing, migration, and feedback analysis, while emphasizing the importance of human judgment, tone, and context.
4. 10 Ways to Make Your Docs AI-Friendly
A final, actionable checklist summarizing the series’ insights. Provides concrete steps documentation teams can take to ensure their content is accessible, structured, and optimized for both human readers and AI-powered tools.
Docs as Code Fundamentals course
We’ve published all three lessons of Module 3 of our Docs as Code Fundamentals course! This module focuses on enhancing the quality and effectiveness of your documentation through structured review processes. You’ll learn how to apply Docs as Code review practices, use automation and linters to ensure consistency, and build strong collaboration workflows that invite contributions while maintaining quality control.
Lessons in this module:
Lesson 1: Docs as Code Review Process: Understand the review workflows unique to Docs as Code and how peer reviews, pull requests, and version control practices help maintain accuracy, consistency, and continuous improvement.
Lesson 2: Automation and Linters: Discover tools and techniques that help automate documentation review. Explore how linters, automated style checks, and CI/CD integrations can streamline the quality assurance process and enforce documentation standards.
Lesson 3: Editing, Collaboration, and Contribution: Explore best practices in editing and collaborative writing. Learn how to manage feedback, maintain tone and clarity across contributors, and foster a healthy contribution model that balances openness with editorial control.
Module 4 coming soon!
A new chapter has been added to the Contact Us Form tutorial, explaining how to use Common Styling: https://documentation.platformos.com/get-started/contact-us-tutorial/using-common-styling
The Contact Us Form tutorial now includes checkpoints, allowing users to check out the exact code state matching each chapter: https://github.com/Platform-OS/tutorials-contact-us
The Common Styling module README has been updated: https://github.com/Platform-OS/pos-module-common-styling
To learn more about the most recent updates, enhancements and fixes in platformOS, check out our latest release note: platformOS Release Note 27 August, 2025 — Added transaction and rollback liquid tags, activity_streams part of pos-cli clone
NEW
add new transaction and rollback liquid tags to support explicit database transactions
pos-cli clone will also affect Activity Streams
IMPROVED
admin_asset_delete_all will also affect soft deleted assets
context.globals will not be explicitly serialized for each BackgroundJob (but will still be available) - it is just a low level implementation optimization to reduce job size, unnecessary noise and performance
include Liquid tag can be used within render tag
FIXED
Fixed issue preventing certain instance copies processes from completing successfully.
NEW
Explicitly set case sensitivity for starts_with and ends_with queries
add new transaction and rollback liquid tags to support explicit database transactions
FIXED
Fixed issue preventing certain instance copies processes from completing successfully.
Subscribe: get status reports in email
Ensure your project’s success with the power of platformOS.