Add a live in-browser playground; retire the markdown docs/ folder

The landing page now runs the real, published @sahinur/forgedata package
client-side (via esm.sh, no bundler) in a new "Try it live" section:
module/generator pickers populated from forge.listGenerators(), plus
seed/locale controls, all calling forge.invoke() for genuinely live output.

docs/*.md is removed — site/docs.html already covers the same ground in a
nicer, browsable format, so keeping both was redundant. Updated every
reference (README, CHANGELOG, RELEASE_NOTES, release.yml, site/docs.html)
to point at the hosted docs site instead of the deleted files.

Author: SahinurDEV

.eslintrc.cjs

@@ -18,7 +18,7 @@ module.exports = {
     browser: true,
     es2020: true,
   },
-  ignorePatterns: ["dist", "node_modules", "coverage", "docs/.vitepress/cache"],
+  ignorePatterns: ["dist", "node_modules", "coverage", "site"],
   rules: {
     "@typescript-eslint/no-unused-vars": ["warn", { argsIgnorePattern: "^_" }],
     "@typescript-eslint/no-explicit-any": "off",

.github/workflows/release.yml

@@ -6,7 +6,7 @@ name: Release
 # last release, AND the NPM_TOKEN secret below is configured. Until you add
 # that secret, this workflow safely fails at the publish step and nothing is
 # published — publishing manually via `npm login && npm publish --access
-# public` (see RELEASE_NOTES.md / docs/contributing.md) is unaffected either way.
+# public` (see RELEASE_NOTES.md) is unaffected either way.
 on:
   push:
     branches: [main]

CHANGELOG.md

@@ -8,8 +8,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 From this point forward, entries in this file are generated automatically by
 [semantic-release](https://semantic-release.gitbook.io/) from
 [Conventional Commits](https://www.conventionalcommits.org/) on `main` — see
-`.releaserc.json` and `docs/contributing.md`. New entries are prepended above
-this line by CI; do not hand-edit past releases.
+`.releaserc.json` and the docs site's [Contributing](https://devsahinur.github.io/ForgeData/docs.html#contributing)
+section. New entries are prepended above this line by CI; do not hand-edit past releases.
 
 ## [0.1.0] - Unreleased
 

README.md

@@ -175,7 +175,7 @@ npx --package=@sahinur/forgedata forgedata generate internet.email --count 5 --s
 npx --package=@sahinur/forgedata forgedata generate location.country --locale ja --json
 ```
 
-Install it globally (`npm install -g @sahinur/forgedata`) to just run `forgedata ...` directly; see [docs/cli.md](./docs/cli.md) for the full flag reference.
+Install it globally (`npm install -g @sahinur/forgedata`) to just run `forgedata ...` directly; see the [docs site](https://devsahinur.github.io/ForgeData/docs.html#cli) for the full flag reference.
 
 ## Modules
 
@@ -220,7 +220,7 @@ npm run bench            # micro-benchmark, compares against faker if installed
 npm run cli -- list      # run the CLI from source during development
 ```
 
-See [docs/](./docs) for the getting-started guide, full API reference, React guide, CLI reference, migration guide from Faker.js, and contributing guide. See [examples/](./examples) for runnable Node, browser, React, and CLI samples.
+See the [documentation site](https://devsahinur.github.io/ForgeData/docs.html) (built from `site/docs.html`) for the getting-started guide, full API reference, React guide, CLI reference, migration guide from Faker.js, and contributing guide. See [examples/](./examples) for runnable Node, browser, React, and CLI samples.
 
 ## Website
 
@@ -247,7 +247,7 @@ npm publish --access public
 
 `scripts/publish.sh` wraps that sequence with a confirmation prompt, and `RELEASE_NOTES.md` has a ready-to-paste description for the GitHub Release / npm announcement.
 
-For every release after the first, `.github/workflows/release.yml` runs [semantic-release](https://semantic-release.gitbook.io/) on pushes to `main` — it derives the next version from [Conventional Commits](https://www.conventionalcommits.org/), updates `CHANGELOG.md`, tags, and publishes, but only once you add an `NPM_TOKEN` repository secret. Until then it's a no-op (see `docs/contributing.md#releasing`); it never requires a token to just sit there ready.
+For every release after the first, `.github/workflows/release.yml` runs [semantic-release](https://semantic-release.gitbook.io/) on pushes to `main` — it derives the next version from [Conventional Commits](https://www.conventionalcommits.org/), updates `CHANGELOG.md`, tags, and publishes, but only once you add an `NPM_TOKEN` repository secret. Until then it's a no-op (see the docs site's [Contributing](https://devsahinur.github.io/ForgeData/docs.html#contributing) section); it never requires a token to just sit there ready.
 
 ## License
 

RELEASE_NOTES.md

@@ -53,11 +53,11 @@ forge.person.fullName();
 forge.internet.email();
 ```
 
-See [README.md](./README.md) and [docs/](./docs) for the full guide, API
-reference, React guide, CLI reference, and migration notes from Faker.js.
+See [README.md](./README.md) and the [documentation site](https://devsahinur.github.io/ForgeData/docs.html)
+for the full guide, API reference, React guide, CLI reference, and migration notes from Faker.js.
 
 ## Links
 
 - npm: https://www.npmjs.com/package/@sahinur/forgedata
-- Docs: [docs/getting-started.md](./docs/getting-started.md)
+- Docs: https://devsahinur.github.io/ForgeData/docs.html
 - Changelog: [CHANGELOG.md](./CHANGELOG.md)