Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: This website is valid JSON

webdatarender.com

Post reply on HN
Print view View original

81–90 of 240 posts

Re: Show HN: This website is valid JSON

#81

Post by [deleted] »

Felk wrote: post #56
quineoa wrote: post #45

Isn'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

The same could be achieved by having the server return different views of the data for different HTTP Accept headers, although not as convenient as appending a file extension. I once did this to interpolate REST API responses into dedicated HTML templates if requested with Accept: text/html, which made exploring the API in the browser more enjoyable.

[deleted]

Re: Show HN: This website is valid JSON

#82

Post by gpnt »

jerf wrote: post #75
gpnt wrote: post #26

Earlier quoted context omitted.

Yes, this is a good catch. The reason for this is the basic render that I created is generic, and it is not what you should do to render your JSON. The render should fit perfectly with the JSON. The basic render is just for a quick start. For example, the basic render "# Title" creates an h1 header, but if you created the render, you know the internal schema of the JSON, so you can use the correct HTML element for th…

"try not to use markup on the JSON, because this would make it difficult for others to consume your website with JSON." Since there is no standard for representing rich text in JSON, if you want rich text, this is simply an unavoidable problem. At least Markdown is semi-standard and people can get libraries for it. Embedded HTML would also work. Defining an ad-hoc rich text embedded would be worse.

You are correct. Sometimes, some markup is inevitable. You can try to break down the information to render separately, but it is not always possible. So I think a little bit of markdown would be an acceptable compromise.

Re: Show HN: This website is valid JSON

#84

Post by gpnt »

trevor-e wrote: post #70

The 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?

The website uses the basic render, that is just a start to make it easy to create a page quickly. But ideally, you create a custom render, that will not depend on the order.

Re: Show HN: This website is valid JSON

#86

Post by gpnt »

zelly wrote: post #83

RIP SEO

Not really, Google and Bing will read the page correctly with Javascript. Check the page insight: https://developers.google.com/speed/pagespeed/insights/?url=...

But it would be even better if they could get the information directly on JSON. So much carbon saved ;)

Re: Show HN: This website is valid JSON

#87

Post by [deleted] »

mark_and_sweep wrote: post #33
habitue wrote: post #10

This 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.

[deleted]

Re: Show HN: This website is valid JSON

#88

Post by Kalium »

greggman3 wrote: post #63
bogidon wrote: post #44

For 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.

> Just because it happens to work doesn't make it a good idea.

An oft-unheard voice of wisdom and sane engineering practices speaks. Hark, ye mortals.

Re: Show HN: This website is valid JSON

#89

Post by minikomi »

gpnt wrote: post #57
minikomi wrote: post #53

Wow, 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?"]]]]]]]};

This is actually the exact opposite of why I have created WDR. The JSON is supposed to be only pure data. All the markup should be inside the render.

Don't worry mate, just mucking about.

https://en.wikipedia.org/wiki/SXML

Re: Show HN: This website is valid JSON

#90

Post by [deleted] »

greggman3 wrote: post #63
bogidon wrote: post #44

For 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.

[deleted]
Post reply on HN