The great redirect about debugger-protocol-viewer HOT 5 CLOSED

1. can't do 301's with jekyll. :( rel=canonical along with a meta refresh
2. about to.
3. one more line for the bot. ;)
4. ah word. not a bad idea. :)

from debugger-protocol-viewer.

@kdzwinel this sound good to you?

from debugger-protocol-viewer.

SGTM, 'debugger-protocol-viewer' wasn't a great name - the docs had a hard time surfacing on the first page of google results.

Some questions/notes:

1. Are these 301 redirects? That'd be good for SEO.

2. Have you fixed your bot so that it doesn't touch debugger-protocol-viewer anymore and updates two branches (master&gh-pages) of devtools-protocol instead?

3. It'll be a bit of a PITA to push new version of debugger-protocol-viewer to devtools-protocol everytime we want to deploy :/ Can automate it somehow?

4. we don't have to use gh-pages for branch names anymore, you can pick any branch from repo settings.

from debugger-protocol-viewer.

okay!

1. https://chromedevtools.github.io/devtools-protocol/ now has all the old data from https://developer.chrome.com/devtools/docs/debugger-protocol FLESHED OUT. my my.
2. i set up a redirect for https://developer.chrome.com/devtools/docs/debugger-protocol so it should autoforward to the new url any hour now..
3. i call these two scripts to update everything: https://github.com/ChromeDevTools/devtools-protocol/tree/master/scripts
4. they're called every hour. so at most we have 1 hour delay between a non-protocol bump change here and a publish. (we could improve this more)

from debugger-protocol-viewer.

Awesome 👏

from debugger-protocol-viewer.