refactor: split the repo into self-contained validator, directory, quickstart, spec and site folders
validator/ holds mewslint (lint, css, fetch, DTD/CSS data); directory/ holds the mews.page service (app, db, check, pages, cli) and depends on validator/; quickstart/ holds mews-quickstart and md2mews.py for third parties who want to create Mews content without cloning the repo; spec/ consolidates doc/ and dtd/ with the canonical mews-0.1.css; site/ becomes a Pelican project with the forward-facing pages as Markdown, the check form kept as a raw HTML snippet. Root pyproject.toml is now a virtual uv workspace over validator, directory and quickstart, with cross-cutting tests that span more than one of them staying at the repo root. Makefile and flake.nix updated to match.
This commit is contained in:
parent
5fa8708bd1
commit
060d4e00fd
90 changed files with 1290 additions and 287 deletions
37
site/content/pages/check.md
Normal file
37
site/content/pages/check.md
Normal file
|
|
@ -0,0 +1,37 @@
|
|||
Title: Check a page
|
||||
Slug: check
|
||||
Description: Check a page against Mews Profile 0.1, and add your site to the directory.
|
||||
|
||||
# Check a page
|
||||
|
||||
Paste an address. The checker validates the page against the [Mews DTD](/dtd/mews-0.1.dtd), reads your stylesheet and up to twenty images, and lists every rule it breaks with the section of the spec that explains it.
|
||||
|
||||
<form action="/result" method="post">
|
||||
<fieldset>
|
||||
<p><label for="url">Page address</label><br />
|
||||
<input type="text" name="url" id="url" size="30" maxlength="200" accesskey="1" /></p>
|
||||
<p><input type="submit" name="check" value="Check page" accesskey="2" />
|
||||
<input type="submit" name="list" value="Check and list" accesskey="3" /></p>
|
||||
</fieldset>
|
||||
</form>
|
||||
|
||||
**Check page** reports and keeps nothing. **Check and list** also puts your site in the <a href="/directory" accesskey="4">directory</a> if the page passes. Either way it takes up to a minute, with no progress bar, because that would want JavaScript. Leave this page open and put the kettle on.
|
||||
|
||||
## Doing it yourself
|
||||
|
||||
The same checks run on the command line, which is quicker while you are still fixing things:
|
||||
|
||||
<pre>uvx --from git+https://code.randogoth.com/randogoth/mews.page.git#subdirectory=validator \
|
||||
mewslint https://example.com/</pre>
|
||||
|
||||
It reads local files too, so you can check a page before publishing it. This site's own build refuses to produce mews.page if any of its pages stops conforming. That seemed only fair.
|
||||
|
||||
## What gets listed
|
||||
|
||||
One page per site, the one you submit, and nobody reviews it: it passes or it doesn't. Listed sites are rechecked every week, and there is no address to warn you at. No account, no password to forget, and no warning either.
|
||||
|
||||
<hr />
|
||||
|
||||
A page turned down over something the spec doesn't say is a bug in the validator, not a fault in your page. Report it to the address on the <a href="/" accesskey="0">home page</a>.
|
||||
|
||||
<p><a href="/spec/0.1" accesskey="5">The spec</a></p>
|
||||
Loading…
Add table
Add a link
Reference in a new issue