@kecan0406/ttheme 1.2.10 → 1.2.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +4 -4
  2. package/bin/ttheme.js +206 -221
  3. package/bin/ttheme.js.map +1 -1
  4. package/dist/manifest.json +2 -9
  5. package/package.json +1 -1
package/README.md CHANGED
@@ -86,7 +86,7 @@ waiting for a release.
86
86
  ### Markets
87
87
 
88
88
  Anyone can publish palettes from a GitHub repository. A market is named
89
- `<owner>@<name>` — its repository's owner and the name its index gives — and
89
+ `<owner>@<name>` — its repository's owner and the name its `ttheme-market.toml` gives — and
90
90
  sits below the series in `ttheme preview` and `ttheme browse`, past a line, with
91
91
  the folders under its `palettes/` as catalogs:
92
92
 
@@ -131,9 +131,9 @@ rei's colors instead. `ttheme edit rei` opens the same editor, and `ttheme check
131
131
  --fix` suggests colors that pass the gate.
132
132
 
133
133
  A local market is already a repository layout: `palettes/*.toml` (a folder
134
- under it, such as `palettes/night/`, is a catalog), the
135
- `ttheme-market.json` index and a workflow that rebuilds the index on every
136
- push. `ttheme market init <name>` makes one and prints the commands that
134
+ under it, such as `palettes/night/`, is a catalog) and the
135
+ `ttheme-market.toml` that names it — nothing to build, since ttheme reads the
136
+ files as pushed. `ttheme market init <name>` makes one and prints the commands that
137
137
  publish it:
138
138
 
139
139
  ```sh