at main
20 folders
1 file
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.
Lead the API pages with the module, and type the conformance report as data (#369)
Two things the pages were saying about themselves rather than about their
subject.
All 120 generated API pages opened with the "auto-generated from the source
docstrings, do not edit by hand" note. That is a message to whoever might edit
the file, and it was standing where the module's own summary belongs: it was
the paragraph a search result quoted and the one the `speakable` selector
points assistants at. The summary leads now and the note follows it.
The conformance report page was typed as an article. It is a machine-generated
table with a fixed schema, regenerated by CI, downloadable at a stable URL, so
it is a Dataset, and it is the most citable object the project owns. Both
language versions now declare one, with the column schema, the download URL
and the DOI. The counts in the description are read from the report itself
rather than written out.
451 pages build, html-validate clean, i18n parity holds, the site-reports and
conformance-claims gates pass, and the three JSON-LD blocks on each
conformance page parse.