# SolidOS Team Meeting * Date: 12.05.2026 10:00 UTC * Call: [https://meet.jit.si/solid-operating-system](https://meet.jit.si/solid-operating-system) * Chat: [https://gitter.im/solidos/solidos](https://gitter.im/solidos/solidos) * Repository: [https://github.com/solidos/solidos](https://github.com/solidos/solidos) * Meetings home: [https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/](https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/) ---- ## Present attendees - Alain Bourgeois - Sharon - Timea - Noel De Martin - Michael Peters ### Scribes * Notion AI meeting notes ## Some links - current work: Milestone 3m -> new profile design https://github.com/SolidOS/solidos/issues/275 - our project board: https://github.com/orgs/SolidOS/projects/2/views/7 - SolidOS designs: https://www.figma.com/proto/88xQawSSXzfQprEZPaKplZ/Solid-OS?node-id=1101-12533&starting-point-node-id=1101%3A12533&show-proto-sidebar=1 ## Topics ### Intro This meeting is a follow up technical discussion meeting to yesterday's meeting. We focuses on Web Components but not only. ### Action Items - [ ] Sharon to finalize mobile layout fixes in profile pane - [ ] Sharon to go through all copilot review comments in solid panes PR - [ ] Sharon to review and perfect projects section - [ ] Sharon to test and verify all mobile improvements - [ ] Sharon to move button components back into profile pane temporarily - [ ] Timea to review all tickets in ProfilePane and provide feedback - [ ] Timea to work with Sharon on photo capture dialogue and add to contacts button - [ ] Noel and Michael to work together on SolidUI web components, focusing on both behavioral (solid-specific) and design system components - [ ] Noel to take lead on web components implementation - [ ] Noel and Michael to create one component (button or select) using new approach with storybook as proof of concept - [ ] Noel and Michael to review and address issues in PR comments - [ ] Noel and Michael to update SolidUI code structure as they see fit, with freedom to decide approach - [ ] Michael to support with accessibility improvements - [ ] Michael to complete accessibility ticket on ProfilePane - [ ] Michael to optionally explore browser HTML improvements in Meshlib - [ ] Michael to consider working on [friends page (social pane)](https://github.com/SolidOS/solid-panes/tree/main/src/social) design implementation later - [ ] Alain to look into updating dependencies for SolidUI, profile pane, and solid panes - [ ] Team to discuss with Jeff about migration path if significant changes are made to [his web components](https://github.com/SolidOS/solid-web-components) library - [ ] Team to ask designer about icon set preference (Lucide vs alternatives) - [ ] Team to decide on [open source font](https://matrix.to/#/!wAfwwonbRnRLYejFOR:gitter.im/$wjQHKNd2JbSEVJ5bER0Q-pNtmrjvDiHTCQxE7TngRFM?via=gitter.im&via=matrix.org&via=chat.semantic.works) from three suggestions and have designer update Figma designs - [ ] Team to add conventions and guidelines document to Git repository, possibly in SolidUI ### Web Components: Key Decisions - **Web components should be behavioral and solid-specific** - The threshold for what becomes a web component is whether it has solid-specific behavior (e.g., login button with OIDC authentication) versus generic UI elements (e.g., simple button) - **LIT Elements approved for continued use** - Despite experimental server-side rendering status, team agreed to continue using LIT because: no solid apps currently use SSR, team lacks extensive web components experience, and all SSR solutions for web components are experimental - **Two types of components identified** : - Reusable, headless web components for the solid ecosystem (behavioral) - SolidOS-specific styled components for internal use (not necessarily headless) - **Styling approach** - Components should include styles and not expose extensive CSS variables for customization; overriding should be possible but not easy, following "some things should be possible but not easy" principle - **Future repository structure** - May split into separate packages: SolidUI for design system with styles, and new package for headless behavioral components ### Design System and Styling - **Design system discipline needed** - Team must stick to defined variants and sizes; custom designs outside the system require strong justification - **Button variants approach** - Similar to other frameworks, buttons should have variants (primary, secondary, outline, ghost) and sizes (small, medium, large) - **CSS variables location** - Currently in Meshlib as interim solution; should be moved to solid-assets repository long-term and imported accordingly - **Ghost button standardization needed** - Edit buttons showing underline on hover should be standardized with other ghost buttons showing background on hover - **Excessive CSS variables to be reduced** - Current approach with variables for every property adds complexity; components should have fewer customization points - **Dark theme is unofficial** - Only light theme is officially designed; dark theme is rudimentary and needs designer input - **Opacity-based theming suggested** - Using opacity values for colors might enable easier dark theme implementation without switching every color ### Technical Implementation Decisions - **Side effects issue in SolidUI** - Current implementation has side effects that prevent tree shaking; should be fixed but can be addressed later - **Component naming and exports** - Directory naming with star exports could simplify component registration, but may impact tree shaking for external users - **Storybook for development** - Team agreed storybook would improve developer experience by allowing quick iteration and viewing all component states without repeated login/logout - **Icon implementation** - Need to implement dynamic icon loading; currently using Lucide as default but should confirm with designer - **Font selection pending** - Three open source alternatives identified for proprietary font; decision needed before designer updates Figma - **SVG icons in solid-assets** - Icons copied as SVGs without color, customizable based on theme (work in progress) - **Base64 icons problem** - Some icons added via base64 prevent current-color from working; should inline SVGs instead ### Profile Pane Release Planning - **Release target: Next week** - Aiming to complete profile pane by next week, with Sharon targeting Tuesday for full testing readiness - **Not blocking on web components work** - SolidUI/web components improvements can happen after profile pane release - **Testing approach** - Sharon created comprehensive testing checklist covering three views: logged in as owner, logged in viewing others, not logged in - **Deployment timing** - Not deploying to test server yet; waiting for mobile fixes first - **Gradual web components integration** - Big changes to web components should be kept for after release; only gradual changes during this phase - **Version 2 structure** - New web components in v2 folder of SolidUI to avoid breaking existing code; location may change later but easy since only used by profile pane - **No major version release yet** - Cannot make breaking changes to SolidUI due to Jeff's extensive usage; must take careful approach ### Process Improvements Discussed - **Testing makes development faster** - Working within tests rather than always running server enables faster iteration - **Developer experience priority** - Need overview of all component states for quick iteration and regression detection - **Pair programming suggested** - Noel and Michael to coordinate on initial component, possibly pairing in afternoon - **Code organization** - Need to document conventions and re-evaluate code structure as team is at "somewhat new beginning" - **Prettier postponed** - Code formatting changes should wait until after profile pane release to avoid too many file changes ### Context and Background - **SolidUI vision** - Library for entire solid ecosystem to help developers create apps; should be framework-agnostic and interoperable with PodOS and community components - **Jeff's web components** - Jeff developed own web components library that should be merged/converged with SolidUI; need migration path - **Solid-assets repository** - Contains light/dark themes and SVG icons for solid-wide community usage - **Conference feedback positive** - Profile pane received excellent feedback at conference; current implementation is best SolidOS has ever looked - **Browser HTML** - Meshlib code that renders similar UI, deployed on GitHub pages; often forgotten but needs to work with changes - **Friends page upcoming** - Designer released friends page design; not officially under grant but Sharon has done work; could be task for Michael later ### Additional Notes - **Working philosophy** - Team prefers keeping close to JavaScript and HTML for longevity; frameworks come and go - **Design flexibility** - Design systems are flexible; can create new variants when needed while maintaining discipline - **Open source nature** - Team emphasized this is open source and experimentation is encouraged - **Michael's motivation** - Michael motivated by improving prominent reused items first for maximum impact on convincing people to use solid - **Resource constraints** - Main bottleneck is reviewing PRs, not preventing them; contributions always welcome across solid community ---- This template is based on the [W3C meeting template](https://github.com/solid/specification/blob/main/meetings/template.md) [Code of conduct](https://github.com/solid/process/blob/main/code-of-conduct.md)