Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Style Documentation for the Resource-Limited by Betsy Haibel Application view layers are always hard to manage. Usually we handwave this as the natural consequence of views being where fuzzy user experience and designer brains meet the cleaner, neater logic of computers and developers. But that handwave can be misleading. View layers are hard to manage because they’re the part of a system where gaps in a team’s interdisciplinary collaboration become glaring. A comprehensive, well-documented styleguide and component library is a utopian ideal. Is it possible to actually get there? It is, and we can do it incrementally with minimal refactor hell.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "Style Documentation for the Resource-Limited" features Betsy Haibel from ActBlue discussing practical strategies for creating effective style guides under resource constraints. The talk emphasizes the importance of clear goals and achievable steps when documenting UI components, while recognizing the challenges of interdisciplinary collaboration in web development. Key points discussed in the video include: - **Defining Goals**: Establishing a clear vision is essential to avoid aimless progress. - **Breaking Down the Process**: Any project, especially under limited resources, requires breaking it down into manageable tasks, while being realistic about time allocations. - **Flexibility and Adaptation**: Recognizing that plans may evolve over time and being open to changes in the vision is crucial. - **Use of Examples**: The 18F style guide is highlighted as a successful model due to its alignment with specific needs instead of an oversized template like Google's Material Design. - **Accidental Style Guides**: Existing codebases often serve as unintentional style guides due to consistent copy-pasting practices, which may falter as teams grow. - **Documenting UI Components**: Betsy outlines a three-step process for developing a style guide that includes identifying UI components, codifying them in code, and then documenting them to enhance team collaboration. - **Iteration over Perfection**: The speaker stresses that documentation should not be treated as a one-time project but rather evolve incrementally, drawing parallels with Agile principles in software development. - **Tools for Documentation**: Utilizing tools like Hologram and KSS for creating visual documentation that can link functionality to design is advised to ensure clarity and enhance communication between developers and designers. In conclusion, Betsy asserts that effective collaboration through proper UI documentation is achievable, advocating for incremental improvements, clear communication, and maintaining a flexible approach in the development journey. She invites the audience to explore additional resources for code samples and documentation techniques shared in her talk.
Suggest modifications
Cancel
