@@ -13,29 +13,30 @@ Quick guide on using our metadata management system for the OP Stack documentati
1313## Using the Scripts
1414
15151 . Run a dry run to preview changes:
16- * Process all .mdx files in a directory
17- ``` bash
18- pnpm metadata-batch-cli:dry " pages/app-developers/**/*.mdx"
19- ```
20- * Process a specific file with verbose output
21- ``` bash
22- pnpm metadata-batch-cli:verbose " pages/app-developers/example.mdx"
23- ```
24- * Process multiple directories
25- ``` bash
26- pnpm metadata-batch-cli:dry " pages/app-developers/**/*.mdx" " pages/node-operators/**/*.mdx"
27- ```
16+ ``` bash
17+ # Process all .mdx files in a directory
18+ pnpm metadata-batch-cli:dry " pages/superchain/*.mdx"
19+
20+ # Process a specific file with verbose output
21+ pnpm metadata-batch-cli:verbose " pages/app-developers/example.mdx"
22+
23+ # Process multiple directories
24+ pnpm metadata-batch-cli:dry " pages/app-developers/*.mdx" " pages/node-operators/*.mdx"
25+ ```
2826
29272 . Apply the changes (remove : dry ):
30- ``` bash
31- pnpm metadata-batch-cli " pages/app-developers/** /*.mdx"
32- ```
28+ ``` bash
29+ pnpm metadata-batch-cli " pages/app-developers/*.mdx"
30+ ```
3331
3432### Important Note About File Patterns
3533
36- * Use ` **/*.mdx ` to match all .mdx files in a directory and its subdirectories
37- * The double asterisk ` ** ` is required for recursive directory matching
38- * Single ` / ` patterns will not work correctly
34+ Use these patterns to match files:
35+
36+ * ` directory/*.mdx ` - matches all .mdx files in a specific directory
37+ * ` directory/subdirectory/*.mdx ` - matches all .mdx files in a specific subdirectory
38+ * ` directory/*/*.mdx ` - matches all .mdx files in all immediate subdirectories
39+ * the quotes around the pattern are important to prevent shell expansion
3940
4041### Configuration Files
4142
@@ -100,13 +101,13 @@ metadata_rules:
100101 * Commit your current changes
101102 * Ensure you're in the docs root directory
102103 * Check that keywords.config.yaml exists and is properly configured
103- * **Important**: All valid metadata values must be defined in keywords.config.yaml
104+ * **Important**: All metadata values must be defined in keywords.config.yaml
104105
1051062. **After Running**
106- * Review the manifest file
107- * Check validation messages in console output
108- * Verify metadata changes in files
109- * Review any files flagged for category review
107+ * Review the categories assigned to each file
108+ * Check that topics and personas are correct
109+ * Verify any files marked for review
110+ * Make sure network types (mainnet/testnet) are correct for registry files
110111
111112## Content Analysis
112113
0 commit comments