progressive enhancement for SEO

ChromeDevTools / debugger-protocol-viewer

DevTools Protocol API docs—its domains, methods, and events

https://chromedevtools.github.io/devtools-protocol/

Other

862 stars 172 forks source link

progressive enhancement for SEO #1

Closed paulirish closed 9 years ago

paulirish commented 9 years ago

Would be ideal to have the HTML of the entire thing in place for SEO purposes.

Filters at the top would then filter things.

A cheap build process would be fine for this.

paulirish commented 9 years ago

The app is crazy simple and dying for a refactor. requirements:

data-binding
templating
serverside rendering

ericguzman commented 9 years ago

Any specific technologies in mind for these requirements, Paul?

paulirish commented 9 years ago

@ericguzman not really.

I am comfortable with something using one or more of the following: web components / polymer 0.8 / ember (w fastboot) / react

paulirish commented 9 years ago

the refactor with polymer 1.0 has now been merged in #10

we still don't ship the HTML, so going to leave the item open for now.

kdzwinel commented 9 years ago

I'm not sure how to approach that. Maybe we should have used jekyll* instead of polymer? Maybe there is a way to mix these two solutions?

(*) jekyll works nicely with github pages, and we could probably make it generate static pages based on protocol.json only

Update - there is no way (supported by github pages) to generate domain pages directly from protocol.json. Jekyll expects a document for each page it generates (so, in our case: dom.md, console.md, css.md, etc.)