Tag Code Blocks for Prism.js Highlighting

Python block becomes language-python

Tagged python from the def start, which your SSG renders as language-python for prism-python.

Input:
```
def handler(request):
    return {'ok': True}
```

Output:
```python
def handler(request):
    return {'ok': True}
```

JSON config tagged for Prism

Leading { matches the JSON rule, giving Prism a language-json class to highlight the config.

Input:
```
{
  "presets": ["@docusaurus/preset-classic"]
}
```

Output:
```json
{
  "presets": ["@docusaurus/preset-classic"]
}
```

Bash command stays bare — tag it yourself

Shell is not detected. The block is left untagged; add ``` bash ``` so Prism's bash component can style it.

Input:
```
npm run docusaurus build
```

Output:
```
npm run docusaurus build
```

(Manually change to ```bash for Prism.)

TypeScript snippet tagged javascript

A .ts block opening with const matches the JavaScript pattern. If your theme loads prism-typescript, rename the hint to typescript.

Input:
```
const config: Config = { title: 'Docs' };
```

Output:
```javascript
const config: Config = { title: 'Docs' };
```

Your manual Prism tag is preserved

A block you already tagged ``` jsx ``` for Prism is left untouched, so the tagger never clobbers component-specific tags.

Input:
```jsx
export default () => <Hero />;
```

Output:
```jsx
export default () => <Hero />;
```

Shell is not in the detection set, so command blocks stay bare and Prism shows them plain. Tag them ``` bash ``` and ensure prism-bash is loaded in your theme.

There is no typescript target. TS gets javascript, which prism-javascript highlights adequately. For true TS highlighting, rename to typescript and load prism-typescript.

JSX rarely matches the patterns unless it opens with a recognised keyword. Tag ``` jsx / tsx ``` by hand and load the matching Prism component.

The html hint produces a language-html class that Prism's markup component highlights. No extra component is needed for HTML.

Any hint you set for a specific Prism component (e.g. ``` graphql ```) is kept. The tagger only fills bare fences, so your component-specific tags survive.

Only backtick fences are processed. Tilde (~~~) fences common in some MDX content are skipped — convert them to backticks first.

JavaScript is tested before Go and shares const /var . A Go block opening with const ( becomes javascript. Lead with package or func for go.

A block starting with { or [ is tagged json. Watch for non-JSON config (e.g. JS object literals) being given a language-json class — review and correct.

Free tier accepts up to 500,000 characters / 1 MB per file. Large generated docs beyond that are rejected; tag them on a higher tier (Pro: 5,000,000 / 10 MB) or split first with md-splitter.

This tool processes a single file per run. For a site-wide pass, tag each content file individually, combine them with md-merger first, or script the deterministic transform into your pipeline.