I wonder is it possible to do this without running any javascript, only HTML5/CSS?
You can use XML+XSLT
Show HN: This website is valid JSON
61–70 of 240 posts
Re: Show HN: This website is valid JSON
#62Isn't Reddit like this, in a way? You can append ".json" at the end and get the data for a page. Others can build their own UI on top of this, if they don't prefer the first party representation. https://www.reddit.com/r/pics/.json
Yeah, it is kind the same, but with the same page.
Re: Show HN: This website is valid JSON
#63For those like me who needed a little help... I do not fully understand the browser rendering process (someone who does please chime in), but what I gather about how this is works is: - the content-type of the page is "text/html", so the browser is trying to render html - there is no special meaning of the #render key to the browser (again the browser doesn't know this is json) - browsers are very fault tolerant so t…
You are correct. It's a silly hack. Just because it happens to work doesn't make it a good idea. Turn off JavaScript and you just get JSON text.
Re: Show HN: This website is valid JSON
#64This is a really cool hack. > The JSON must contain only pure information without any concern about design or markup. Wellll.. I mean the json has markdown syntax in it. That's a lot nicer than html tags for markup, but it's still markup. In case anyone reading hasn't seen it before, browsers have a thing called XSLT built into them that does something similar for XML documents. You serve up your data as XML, add a t…
XSLT is the only way to do HTML templating on the client without using JS. I think that is valuable.
HTML templating with XSLT may be used to save data, too.
For example, if you build a social network profile page using XSLT, alice.xml and bob.xml can reference the same profile.xsl stylesheet which converts the XML profile data to the rendered HTML page. Since the profile.xsl stylesheet can be cached, whenever a new profile is visited, only the profile data in XML needs to be transferred.
Note that the templating can also be used to save data when rendering a single page. Imagine a Twitter clone that displays a list of tweets. If, hypothetically, 80 characters of Tweet data plus 500 characters of XSL template, produce 250 characters of HTML markup, you only need 3 tweets to start saving data (250x3=750 > 500+3x80=740).
Re: Show HN: This website is valid JSON
#65This is an amazing idea, but this is very complicated to write ,I think, because you need to write html lines.
Re: Show HN: This website is valid JSON
#66This is a really cool hack. > The JSON must contain only pure information without any concern about design or markup. Wellll.. I mean the json has markdown syntax in it. That's a lot nicer than html tags for markup, but it's still markup. In case anyone reading hasn't seen it before, browsers have a thing called XSLT built into them that does something similar for XML documents. You serve up your data as XML, add a t…
I still have nightmares from learning XSLT. It's very cool, but also, very strange, if you come from a procedural language background. Also, XSLT is really given power by being mixed with XPath (which is procedural). I suspect that if I had known more about FP back when I learned it, I would have had an easier time. I wrote up a really long, painful post about XSLT, way back in the early 'oughts.
> XPath (which is procedural)
XPath is not procedural. It is entirely composed of expressions that compose and return results. The closest common language might be SQL.
Re: Show HN: This website is valid JSON
#67At this point, browsers should allow non-markup files - specifically JS or WASM - to be the base of a web page. Browsers will already automatically add in and into the DOM if they're missing on a page, so literally, you could have a website that's just a //do DOM stuff and it'd be parsed and run without issues.
The index page at this point is mostly just a DOM skeleton on which to hang references to CSS, media, scripts and metadata. We might as well cut out the last step already.
If there was an official HTML-to-JSON format, we could even use that as well. It would probably already exist, but the question is always what to do with node attributes, text nodes and child-nodes. There's a dozen ways to organize them in JSON.
Re: Show HN: This website is valid JSON
#68Wow. Hacker News is really the place to be I was just thinking of a project like this.
Only that my goal was to create a browser for that an alternative to the web.
It would work on the same principle of separating data from information
Re: Show HN: This website is valid JSON
#69Wow, now we can write pages like { "content": [ ["html", {}, [["head", {}, []], ["body", {}, [["h1", { id: "main-header" }, [ "Welcome to my", ["span", { class: "red-text" }, ["PAGE"]]]], ["h2", { id: "sub-header" }, [ "It's so cool.", ["br", {}, nil], "Don't you think?"]]]]]]]};
We do basically this. [0][1]
[0] escherize.com/w/hiccup.space
[1] escherize.com/w/cljsfiddle
Re: Show HN: This website is valid JSON
#70The json.org description of an "object" is:
> An object is an unordered set of name/value pairs.
But this site seems to be assuming that the key/value pairs are parsed in their original ordering for everything to display properly. Is it safe to assume JavaScript will always parse the keys in order?