62 lines
3 KiB
HTML
62 lines
3 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN"
|
||
|
|
"http://www.openmobilealliance.org/tech/DTD/xhtml-mobile12.dtd">
|
||
|
|
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||
|
|
<head>
|
||
|
|
<title>Check a page</title>
|
||
|
|
<meta name="mews-profile" content="0.1" />
|
||
|
|
<meta name="viewport" content="width=device-width" />
|
||
|
|
<meta name="description" content="Check a page against Mews Profile 0.1, and add your site to the directory." />
|
||
|
|
<link rel="stylesheet" type="text/css" href="mews-0.1.css" />
|
||
|
|
</head>
|
||
|
|
<body class="mews-cool">
|
||
|
|
<h1>Check a page</h1>
|
||
|
|
<p>Paste an address below. The checker fetches that page, validates it
|
||
|
|
against the <a href="/dtd/mews-0.1.dtd">Mews DTD</a>, reads your copy of
|
||
|
|
the stylesheet and up to twenty of your images, and then lists every rule
|
||
|
|
the page breaks together with the section of the spec that explains it.</p>
|
||
|
|
|
||
|
|
<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>
|
||
|
|
|
||
|
|
<p><strong>Check page</strong> tells you what it found and keeps nothing.
|
||
|
|
<strong>Check and list</strong> does the same and then, if the page passes,
|
||
|
|
puts your site in the <a href="/directory" accesskey="4">directory</a>.
|
||
|
|
Either way it can take up to a minute, and there is no progress bar,
|
||
|
|
because a progress bar wants JavaScript and that is the one thing a Mews
|
||
|
|
page can't have. Leave this page open and go and put the kettle on.</p>
|
||
|
|
|
||
|
|
<h2>Doing it yourself</h2>
|
||
|
|
<p>The same checks run on the command line, which is far less tedious
|
||
|
|
while you are still fixing things:</p>
|
||
|
|
<pre>uv run mewslint.py https://example.com/</pre>
|
||
|
|
<p>It reads local files too, so you can check a page before anyone else
|
||
|
|
sees it, and I run it on this site as well: the build refuses to produce
|
||
|
|
mews.page at all if one of its own pages stops conforming. That seemed
|
||
|
|
only fair.</p>
|
||
|
|
|
||
|
|
<h2>What gets listed</h2>
|
||
|
|
<p>One page per site, the one you hand me, and nobody reviews it: if the
|
||
|
|
page passes it goes in, and that is the whole of the trust model. A listed
|
||
|
|
site is checked again every week, and one whose page stops conforming
|
||
|
|
comes out of the directory without being asked twice.</p>
|
||
|
|
|
||
|
|
<p>Fix it, submit it again, and it is back in straight away. I keep no
|
||
|
|
address to warn you at, which is the trade (no account, no password to
|
||
|
|
forget, and no warning either).</p>
|
||
|
|
|
||
|
|
<hr />
|
||
|
|
<p>If the checker turns your page down over something the spec doesn't
|
||
|
|
actually say, that is a bug in my validator rather than a fault in your
|
||
|
|
page, and I would like to hear about it.</p>
|
||
|
|
<p><a href="/spec/0.1" accesskey="5">The spec</a>
|
||
|
|
· <a href="/about" accesskey="0">About this site</a></p>
|
||
|
|
</body>
|
||
|
|
</html>
|