Good point. But maybe it is still useful for a single page with a lot of information that they do not want to have in a database, for some reason? Just my 2cents.
I would agree, if the data was stored in JSON and only visible if the user had enabled JavaScript. But the TableKit system uses a vanilla HTML table for its data source, and then makes that look/behave fancier as a special favor to those who have enabled JS. It doesn’t hide the content at all. Any system that doesn’t start with content in HTML is ignoring search engines, too.
Walter
On Dec 19, 2013, at 10:25 PM, Todd wrote:
Yep, it’s cool, but I have to wonder: why base this kind of functionality on js when it’s so easy to disable? Maybe I’m missing the bigger picture.
Thanks for clearing that up. Then I would say TableKit is even cooler than I initially thought.
Todd
I would agree, if the data was stored in JSON and only visible if the user had enabled JavaScript. But the TableKit system uses a vanilla HTML table for its data source, and then makes that look/behave fancier as a special favor to those who have enabled JS. It doesn’t hide the content at all. Any system that doesn’t start with content in HTML is ignoring search engines, too.