4 ms·
The problem with only using markup to render websites is the lack of navigation. We need something to show next/previous page (we have rel headers and tags for
by bradgessler 4y ago
The problem with only using markup to render websites is the lack of navigation.
We need something to show next/previous page (we have rel headers and tags for that) and something that shows a tree navigation structure for populating menus (not sure what exists for that)
The tree structure would need to be “crawlable” because for very large sites, the entire tree can’t be loaded. That could be solved by representing nodes on the tree as URLs that can be loaded by the client as needed.
I’d love to see this happen. I don’t think we need markdown per-se… maybe it’s a subset of HTML that leaves out css, JavaScript, and a lot of the other nonsense.
Is anybody interested in building this out? I have ideas for the server and formats, but would want help implementing the clients.