Why it exists
A site written in plain semantic HTML needs no CMS, database, or framework, and it will still open in twenty years. The cost is that every change means editing HTML by hand. The usual fix moves the content into Markdown or data files behind a site generator and a CMS, which brings back the moving parts the plain site avoided.
TagDraft keeps the HTML as the only source and makes the HTML editable. Tag family pages have no classes to decode, so the editor can tell what something is from its tag: a table is rows to add and remove, a <time> is a date to pick, a section of articles is a row of columns.
What you can try
The prototype opens TagKit's church starter site. On any page:
- Change words: click a heading, paragraph, list item, or table cell and type.
- Rows, cards, and questions: copy, move, or remove a table row, a card, a list item, or an FAQ entry.
- Dates, links, and photos: pick a date and the visible text and the machine-readable date are both written; a photo needs a description before it's accepted.
- Add a section: choose from TagKit's ready-made sections (FAQ, card grid, stat tiles, testimonials, a contact form, and more).
- Add columns: a section of one to six columns, then add a column to the left or right of any other.
- Add an element: a paragraph, heading, list, callout, photo, or table below the one you clicked.
- Edit HTML: open the markup of one row, card, or section, change it, and go back to the page.
- Checked as you go: TagCheck reads the page after every change, and an HTML edit that adds a problem isn't applied.
What it doesn't do yet
- Save to a folder or to GitHub. You can view or download the edited page.
- Edit the shared header and footer, or your own site: it opens the demo site only.
- Keep the file exactly as it was outside your edit. The real editor must; the prototype re-writes the page from the browser's copy.
- Columns of different widths. That is proposed for TagBrush.css.
- Upload photos, or run the page's interactive parts while you edit.
How it fits the family
TagBrush.css makes the page look finished, TagAction makes it behave, TagCheck finds mistakes, and TagKit gives you pages and sections to start from. TagDraft is for the person who keeps the site up to date afterwards: it uses TagKit's sections as its building blocks and TagCheck as its safety net, and it writes only HTML the other tools already understand.
The draft spec lists what is decided and what is still open. The biggest open question is where "save" goes.