10 replies

1. Marco Rogers 2 min later

   @zachleat @eleventy is that bad?

   1. Zach Leatherman 6 min later

      @polotek @eleventy the only bad part is how long it’s taking 😅

2. Private reply 33 min later
   1. Private reply 14 hr later
      1. Private reply 16 hr later
         1. Private reply 16 hr later
3. Zach Leatherman 1 day later

   this v3 docs PR is growing in both breadth and power

   1. westbrook 1 day later

      @zachleat Only 100 additions, seems smoll... 🙃

   2. Jared White (ResistanceNet ✊) 1 day later

      @zachleat ah, a docs PR!

      I'm not sure how you like to tackle that stuff, but I've come to discover it's so-o-o much easier to document new features in its own docs PR than co-located with code (Bridgetown’s a monorepo). I used to think I should try to write docs as if it's part of a checklist along with tests and other code-level concerns, and that really gunked up the works.

      Anyways…just curious!

      1. Zach Leatherman 1 day later

         @jaredwhite I try really hard to maintain only one live/latest branch of docs—but some of this ESM stuff was too intrusive to live on `www` before `v3` shipped stable—thus the PR. Lots of v3 features are already documented on `www` right now!

         I used to go nuts with versioned docs for every minor release but now I’m planning on just doing major release subdomains moving forward: https://www.11ty.dev/docs/versions/