Skip to content

Editor profile

About patterncrochet.

Founder, designer, and editor behind patterncrochet. Every pattern on the site goes through the same process: design, work the prototype with the recommended yarn and hook, photograph each step, write the instructions, then test-read the pattern from scratch before publishing.

The process

How a pattern becomes a post.

  1. 1

    Design. Start from the photographed inspiration or a request. Sketch the silhouette, choose the yarn weight and hook, work out the construction.

  2. 2

    Prototype. Make the piece with the chosen yarn and hook. Track changes as the make evolves. If the design needs a different construction, restart from step one.

  3. 3

    Photograph. In daylight, on a neutral surface. Cover photo plus key in-progress shots.

  4. 4

    Write. Materials list with the weight + hook size that worked, abbreviations, step-by-step instructions with stitch counts at the end of each round or row, finishing notes.

  5. 5

    Test-read. Read the finished pattern from scratch as if seeing it for the first time. Anywhere the written instructions don't match what was actually done, fix the writing before publishing.

  6. 6

    Publish. Open, in full, with no email gate. If a reader spots an error after publishing, the pattern gets updated and a dated note is added.

What I believe about patterns

The house rules.

  • The page is the pattern. Materials, abbreviations, photos, and step-by-step instructions all live on the same scroll. No paywalls, no inbox trades, no hidden steps.
  • Beginner-friendly framing. Patterns are written so the language doesn't assume previous experience. Where a pattern needs a stitch or technique you might not know, it links to the tutorial.
  • Honest skill labels. A beginner pattern only uses beginner stitches. An intermediate pattern is honestly intermediate, not labeled "easy" to draw clicks.
  • Open and shareable. Every pattern stays readable on the page. The finished piece is yours to wear, gift, or sell.
  • Updated when something breaks. If a reader catches an error, the pattern gets fixed and the update is dated. The site keeps a public correction history rather than quietly editing the past.

Read every pattern in the library.