#MINIMALIST DRAWING HOW TO#

‘I had stacks of comics because I had sort of taught myself how to read, because I couldn’t speak English. As a young girl she moved with her parents from Latvia to Indianapolis in the USA and began collecting pictures from comic books and picture playing cards. In simpler examples, it’s usually easier to go top-down, and on larger projects, it’s easier to go bottom-up.įunction ProductCategoryRow ( if ( product.Vija Celmins was fascinated by images from an early age. You can either build “top down” by starting with building the components higher up in the hierarchy (like FilterableProductTable) or “bottom up” by working from components lower down (like ProductRow). Since this is a static version of the app, you don’t need it.) State is reserved only for interactivity, that is, data that changes over time. (If you’re familiar with the concept of state, don’t use state at all to build this static version. Props are a way of passing data from parent to child. To build a static version of your app that renders your data model, you’ll want to build components that reuse other components and pass data using props. Building a static version requires a lot of typing and no thinking, but adding interactivity requires a lot of thinking and not a lot of typing. The most straightforward approach is to build a version that renders the UI from your data model without adding any interactivity… yet! It’s often easier to build the static version first and add interactivity later. Now that you have your component hierarchy, it’s time to implement your app.

Components that appear within another component in the mockup should appear as a child in the hierarchy: Now that you’ve identified the components in the mockup, arrange them into a hierarchy. However, if this header grows to be complex (e.g., if you add sorting), you can move it into its own ProductTableHeader component. For this example, it is a part of ProductTable because it appears inside the ProductTable’s list. This is a matter of preference, and you could go either way. If you look at ProductTable (lavender), you’ll see that the table header (containing the “Name” and “Price” labels) isn’t its own component. There are five components on this screen: Separate your UI into components, where each component matches one piece of your data model. That’s because UI and data models often have the same information architecture-that is, the same shape.

If your JSON is well-structured, you’ll often find that it naturally maps to the component structure of your UI.

Design-consider how you would organize the design’s layers.

(However, components are a bit less granular.)

CSS-consider what you would make class selectors for.

If it ends up growing, it should be decomposed into smaller subcomponents. One such technique is the single responsibility principle, that is, a component should ideally only do one thing.

Programming-use the same techniques for deciding if you should create a new function or object.

Ask them!ĭepending on your background, you can think about splitting up a design into components in different ways: If you work with a designer, they may have already named these components in their design tool. Start by drawing boxes around every component and subcomponent in the mockup and naming them. Step 1: Break the UI into a component hierarchy To implement a UI in React, you will usually follow the same five steps.

Minimalist drawing