3 ms·

That's interesting you mention. I think it's already happening in a little different form with Structured Data [1] and schema.org and it's using for example JS

That's interesting you mention. I think it's already happening in a little different form with Structured Data [1] and schema.org and it's using for example JSON-LD [2]. But a separate endpoint might also be an evolution. Right now this could be the sitemaps and robots.txt as an entrypoint for spiders. Although the one drawback that comes to my mind with a separate endpoint is that it'd have to be kept in sync with the normal page and that might vastly enlarge the costs for maintaining it. So keeping it close to the DOM seems to be reasonable [1]: https://developers.google.com/search/docs/guides/intro-structured-data https://developers.google.com/search/docs/guides/intro-struc... [2]: https://json-ld.org https://json-ld.org

thomasfromcdnjs 6y ago
Sounds like we come from the same experience. I think for anyone who wants to pioneer this idea, the costs will be noticeable, but that's what bandwagons and the youth are for =D Ultimately I think there will be a reduction in costs (bits, process, maintenance) To steal from React lingo, UI represented as state, that is more or less what any web page is. Wrapping it in a meta layer like the DOM just adds overhead which I think can be optimized. I'm undecided but still entertaining the idea.