related_content is heavy in JSON about yari HOT 5 CLOSED

By the way, because of repetition, related_content compresses better. Gzipped:

related_content                  1108    34%
prose                             892    28%
contributors                      416    13%
browser_compatibility             283     8%
examples                          250     7%
interactive_example_url            83     2%
mdn_url                            78     2%
title                              51     1%
attributes                         22     0%

from yari.

One interesting solution is to not hydrate with content from a serialized string. Then you get the best of both worlds. You get no re-render on the client-side and you don't have to include all the heavy state in a serialized JSON string.

from yari.

A horribly rough draft is: https://github.com/peterbe/stumptown-renderer/tree/hydrate-based-on-dom
It removes the need to include the state serialized. But it breaks hydration.

from yari.

A flaw that can't be escaped is that if you follow that idea it means you simply don't get the event handlers. I.e. all onClicks within the Document will not work. And it can't because we never give the React-in-the-browser a chance to build up its own virtual DOM.

from yari.

Perhaps, it's a better idea to break apart index.json into index.json and related_content.json and then lazy-load the sidebar with XHR after initial load. Not great either.

from yari.