MCP control plane for unaltraweb website workspaces
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"unaltraweb-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# unaltraweb `unaltraweb` is a reusable Jekyll core for academic, research project, software and documentation websites maintained by `dosquartsdedocs`. ## Content Editors: Start Here If you have been invited to edit a generated site, start with that repository's `README.md`. It identifies the selected profile, lists the content paths you may edit, and puts the browser-only workflow before local technical setup. For every GitHub Web edit: 1. Work from an assigned issue or an explicit file reservation accepted by the maintainer. Only one active editor may work on a file. 2. Create one branch per task and never edit `main` directly. 3. Open a small Draft pull request early. If a conflict appears, stop and ask the maintainer instead of overwriting work. 4. The maintainer runs local checks and required renders, reviews the result, merges the pull request, and only then starts deployment manually. See [Edit Safely In GitHub Web](docs/_documentation/en/06-github-web-editing.md) for the full coordination, image-upload, file-safety, and publication protocol. ## Four Site Profiles | Profile | Use it for | Main editor-owned paths | |---|---|---| | `unaltreselfie` | A personal academic or professional site | `_pages/`, `_posts/`, `_news/`, `_projects/`, `_books/`, `_bibliography/`, approved profile assets | | `unaltreprojecte` | A research project, group, infrastructure, or output site | `_pages/`, `_news/`, `_projects/`, `_outputs/`, `_books/`, `_data/team.yml`, `_data/repositories.yml`, approved project assets | | `unaltremanual` | A manual, course, handbook, or book-like publication | `_pages/`, `_chapters/`, `_bibliography/`, `context/writing-profile.md`, approved source images | | `unaltredocs` | Technical or operational documentation | `_pages/`, `_documentation/`, public `_data/` files, approved screenshots | ## Technical Overview The core packages shared layouts, includes, Sass, assets, Jekyll plugins, bibliometric tooling, multilingual behaviour, theme mode…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.