-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d58b711
commit 82b157d
Showing
4 changed files
with
78 additions
and
0 deletions.
There are no files selected for viewing
25 changes: 25 additions & 0 deletions
25
packages/proposals/proposals/a-universal-design-system-substrate.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Title | ||
|
||
A Universal Design System Substrate | ||
|
||
# Description | ||
|
||
Design systems are tough to build and maintain across multiple UI | ||
surfaces and differing technologies. JavaScript gives us a gateway | ||
into reducing platform sprawl in our design systems. In this talk | ||
we'll cover API design that works everywhere, simplifying support to a | ||
single technology, and how to work with systems like WordPress once | ||
you've simplified your technical approach. The audience will walk away | ||
with the ability to simplify their design system efforts across | ||
typically disjointed mediums. The talk will use React for concrete | ||
examples, but the principles apply to other approaches as well. | ||
|
||
# Notes | ||
|
||
This talk builds on my experience building design systems at Docker, | ||
Dropbox, and working with clients. The goal of the talk is to paint a | ||
picture of a unified approach to design systems enabled by recent | ||
developments in the JavaScript ecosystem. By leaning on JS, we can | ||
vastly reduce the effort required to maintain sophisticated and high | ||
growth systems granting smaller teams higher leverage to achieve | ||
better results. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Title | ||
|
||
Let's Go, Generate! | ||
|
||
# Elevator Pitch | ||
|
||
> Please use go generate creatively. It's there to encourage experimentation. | ||
> | ||
> - Rob Pike | ||
Codegen is often thought of as mystical dark art but it's a powerful | ||
tool in the go toolbox. In this talk we'll demystify go:generate, and | ||
talk through interesting use cases in open source projects. | ||
|
||
# Description | ||
|
||
The audience will walk away from this talk equipped with the tools and | ||
conceptual framework they need to start using go:generate (and codegen | ||
in general) in their own libraries and applications. We'll cover the | ||
basics (what `go:generate` is, how it works, why using `go run` makes | ||
more sense than depending on other binaries) before advancing to | ||
investigating implementations in real-world open source projects like | ||
gqlgen, which uses codegen to maintain type safety in GraphQL | ||
APIs. Finally we'll touch on more advanced and creative codegen in | ||
projects like Kubernetes, which can generate clients and other API | ||
machinery using a universal DeepCopy method and has its own go package | ||
and comment syntax. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Title | ||
|
||
Styles and Naming | ||
|
||
# Description | ||
|
||
Building on Nicole's Object Oriented CSS in 2008, BEM | ||
in 2005-2010, and later Snook's SMACSS, CSS has a long and storied | ||
history of naming conventions that heavily affect code organization, | ||
design thinking, and maintenance. This talk will cover the evolution | ||
of naming conventions in CSS, the benefits they brought, and how the | ||
tools we use affect the way we think. The audience will come away with | ||
an understanding of how we got to where we are and how to evaluate the | ||
emerging crop of tools such as CSS Blocks, CSS Modules, and even | ||
CSS-in-JS. | ||
|
||
# Notes | ||
|
||
This talk takes a design systems viewpoint on styles and naming | ||
conventions using my experience building such systems at various | ||
startups over the last few years. As such, the overarching storyline | ||
will be related to how these tools and conventions impact our ability | ||
to deliver great user experiences through our languages and systems. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters