These are my unstructured notes from the workshop. Read with caution (they're biased to my own interpretation).

1,000,000 Julian.com visitorsPart 1: What's your objective for your article?Part 2: pair it with an objectiveobjective + motivationgood nonfiction = 70% novelty + 25% story + 5% style

This document is a guide to writing agile contracts. Unlike traditional contracts, an agile contract does not specify individual tasks to be completed by the Contractor. Rather, an agile contract specifies how the Client and Contractor interact, and how the Contractor is paid. The Deliverable Work performed for the contract is determined through an ongoing collaboration between the Client and the Contractor.

Agile contracts require a great deal of trust from both the Client and the Contractor. This trust is fostered through tight feedback cycles and well-defined responsibilities that both parties can expect from each other. More so than traditional contracts, an agile contract requires active participation from the Client.

With the addition of ES modules, there's now no fewer than 24 ways to load your JS code: (inline|not inline) x (defer|no defer) x (async|no async) x (type=text/javascript | type=module | nomodule) -- and each of them is subtly different.

This document is a comparison of various ways the<script> tags in HTML are processed depending on the attributes set.

If you ever wondered when to use inline<script async type="module"> and when<script nomodule defer src="...">, you're in the good place!

Note that this article is about<script>s inserted in the HTML; the behavior of<script>s inserted at runtime is slightly different - seeDeep dive into the murky waters of script loading by Jake Archibald (2013)

Testing double-fetching ofmodule/nomodule JS code (includingthe Safari hack)

<script type="module" src="module.js"></script><script nomodule src="nomodule.js"></script>

Test page:https://jg-testpage.github.io/es-modules/module-nomodule/

|IE/Edge|Firefox|Chrome|Safari |fetches module|fetches nomodule|executes| |

2015.10.07t

Reach UI is an accessible foundation for React applications and design systems.

The three equally important goals are to be:

• Accessible
• Composable
• Stylable

1. Location
   1. pathname
   2. state
   3. search/query
   4. hash
2. Path

This is the base of all projects and it will include the foundation for all potential react-based projects in Reason.

This base package should include a ReasonReact api to promote collaboration and familiarity with people using a ReasonReact, and for the modern world of React this should also include a Hooks api that currently revery uses.

All blocks in Jsx are of typeReact.reactElement. This reactElement should represent:

Building reusable UI components is a non trivial task, as we need to anticipate a number of things when planing for reuseability. On the one end of the spectrum we want to enable customization and on the other side we want to avoid developers doing the wrong thing, like breaking the component or displaying invalid states.

To get a better understanding of what we need to think about and consider upfront, we will build a non-trivial UI component, that displays tags. OurTags component will take care of managing and displaying tags.

The following examples are all built withTachyons andReact, but these ideas apply to any UI component and any general styling approach.