Starting with all

This part of the site follows my own Sewfile: what I put in it, why each piece belongs there, and how it changes as my projects need more from it.

It follows the approach of makefile.fyi, where a personal Make setup grows through a series of explained changes. Here, the setup will grow alongside Sew itself.

Start with one task

The proposed starting point is:

all: []

There are no build steps to collect yet, so the dependency list is empty. The name all gives those steps a place to come together later.

This is a planned example, not a working configuration for the current command. The parser design note explains what needs to exist in Sew before this file can be used.

Let the project supply the next step

I want each addition to answer a concrete need in a project. That could mean building a program, generating a file, or running a check. The explanation should start with that need, then show the change and its result.

This is a personal setup, not a template every project has to follow. The reasoning should make it easier to decide which parts are useful in your own Sewfile.

Keep the two stories connected

Building Sew explains how the tool is made. This section explains how I use it. When a change to my Sewfile depends on a new capability in Sew, the two explanations can link to each other.

That keeps the practical example close to the implementation that supports it.