mikeal commented 9 years ago

This is the list of blockers for getting the new site live. There's plenty of additional things to do to improve the website, this list is only things that MUST be done in order to go live.

Content

[x] Docs.md (main docs page content)
[x] versions.json w/ all io.js and node.js releases
[x] https://iojs.org/api/ -> https://new.nodejs.org/api/
[x] Google Analytics

What else?

fhemberger commented 9 years ago

Move/link API docs from iojs.org to (new.)nodejs.org

rvagg commented 9 years ago

https://new.nodejs.org/download/release/index.json https://new.nodejs.org/download/release/index.tab or https://new.nodejs.org/dist/index.json https://new.nodejs.org/dist/index.tab

Note that this server is now populated with all of the old node dist directory

I wasn't planning on merging the two but I'm getting the impression that that's being suggested.

fhemberger commented 9 years ago

@rvagg Can you sort the list by date? If merging both lists is a problem at the moment, we could do this at build time as well.

rvagg commented 9 years ago

"date" is kind of hard to determine, which file do you test and what is that date indicating anyway?

Instead, I've pulled in node-semver and used it to compare for a sort, hope that helps

rvagg commented 9 years ago

I've turned on CloudFlare for new.nodejs.org and am going to bed, let me know if anything odd turns up but we're getting very close to this being ready. I did want to switch iojs.org over to this new server but it's too late and I don't want to be switching it just before I head off to sleep so I'll do it tomorrow.

fhemberger commented 9 years ago

@rvagg Wrote a little script load-versions.js which merges the two files for our release list.

fhemberger commented 9 years ago

Okay, I'm calling it a day as well. ;)

rvagg commented 9 years ago

You can do https://iojs.org/api/ -> https://new.nodejs.org/api/ now, it's active

Also, I don't know if it helps at all but I'm putting latest-v0.10.x, latest-v0.12.x, latest-v4.x etc. in all of the download directories (/dist/ a.k.a. /downoads/release/, /download/nightly/, /download/rc/, etc.), these'll get updated on each release. But you have the index.json data you can do that from anyway.

fhemberger commented 9 years ago

@rvagg I still end up on the Node.js v0.12.7 docs instead of the iojs docs.

rvagg commented 9 years ago

well, that's appropriate for nodejs.org where 0.12 is the "latest", as soon as v4 drops it'll switch to 4.0.0 docs

fhemberger commented 9 years ago

Okay, felt a bit odd at first when you're redirected to the old site. ;)

I'll go through the site and change all links later.

fhemberger commented 9 years ago

Link is updated.

rvagg commented 9 years ago

I spent the entirety of my day being intimate with the new server and am not as close as I hoped. Most of the pieces are in place now, there's a little bit of testing to do but remaining items are:

[x] Re-enable proper http support for the resources that need it, as per #42, this is not as easy as it sounds
[x] Put in the redirects that @fhemberger listed for me somewhere in this repo
[ ] Do a final catalogue of the non-4xx hits in the existing logs on the old nodejs.org to see what resources are actually being used. There's a lot of cruft in there and I'm hesitant to just cut the cord on it all without having an idea of what's being used. If anyone wants to help look over the list to see if there are any goodies, here it is: https://gist.github.com/rvagg/b2e76ef6c8217530d313
[x] Upgrade the server to something with a little more grunt
[ ] Get a proper log rotation archive scheme in place so the server doesn't fill but but we don't lose valuable analytics data (this can wait till after launch, but I shouldn't leave it too long!)

fhemberger commented 9 years ago

@rvagg Found them! https://github.com/nodejs/new.nodejs.org/issues/20#issuecomment-130218243

ghost commented 9 years ago

To be honest, looking at the staging (I assume that's what it is) site, the index looks kind of meager, as in, the page does not really scroll at all. Shouldn't we add a little more information than that? (Apologies if that's already being worked on)

rvagg commented 9 years ago

"latest" on the front page is v3.2.0, are we OK with that? I'd say in the interests of transition we go with 0.12.7 until v4 is out later this week. Or is this a remnant of the fact that you've only had io.js' index.json to go with till now?

rvagg commented 9 years ago

@fhemberger & @mikeal I'm going to look to you two for sign-off on the switch to the new site, I'll get my pieces done today but need you to let me know when you're comfortable with the move.

rvagg commented 9 years ago

Can we add:

[x] Google Analytics

To the checklist please? I see it in the prefetch list but not inline at all. Since we are relying on CF to serve most of the website content we're not going to be able to do anything useful with the server logs except for /dist & /download files. Make sure that any Analytics setup is shared with enough of the website team to make it useful.

rvagg commented 9 years ago

OK, redirects are mostly done, but very painful. I've put in @fhemberger's list mostly as is for nodejs.org:

    rewrite ^/about/advisory-board/(.*)$                          https://$server_name/en/about/organization/ permanent;
    rewrite ^/advisory-board/(.*)$                                https://$server_name/en/about/organization/ permanent;
    rewrite ^/about/organization/tsc-meetings/$                   https://$server_name/en/foundation/tsc/minutes/ permanent;
    rewrite ^/about/organization/tsc-meetings/(.*?)/minutes.html$ https://$server_name/en/foundation/tsc/minutes/$1/ permanent;
    rewrite ^/about/security/$                                    https://$server_name/en/security/ permanent;
    rewrite ^/contribute/$                                        https://$server_name/en/get-involved/ permanent;
    rewrite ^/contribute/accepting_contributions.html$            https://github.com/nodejs/dev-policy permanent;
    rewrite ^/contribute/becoming_collaborator.html$              https://$server_name/en/get-involved/ permanent;
    rewrite ^/contribute/code_contributions/$                     https://$server_name/en/get-involved/ permanent;
    rewrite ^/contribute/code_contributions/workflow.html$        https://$server_name/en/get-involved/ permanent;
    rewrite ^/documentation/(.*)$                                 https://$server_name/en/docs/ permanent;
    rewrite ^/foundation/blog.html$                               https://$server_name/en/blog/ permanent;
    rewrite ^/foundation/members.html$                            https://$server_name/en/foundation/members/ permanent;

    rewrite ^/images/foundation-visual-guidelines.pdf$            https://$server_name/static/documents/foundation-visual-guidelines.pdf permanent;
    rewrite ^/images/logos/js-black(.*)$                          https://$server_name/static/images/logos/js-black$1 permanent;
    rewrite ^/images/logos/nodejs-(.*)$                           https://$server_name/static/images/logos/nodejs-$1 permanent;
    rewrite ^/images/node-foundation-by-laws.pdf$                 https://$server_name/static/documents/node-foundation-by-laws.pdf permanent;
    rewrite ^/images/.*trademark-policy.pdf$                      https://$server_name/static/documents/trademark-policy.pdf permanent;
    rewrite ^/video/(.*)$                                         https://$server_name/static/video/$1 permanent;

and put in the blog ones to blog.nodejs.org but because you're now listing by category a bulk redirect no longer works! So I had to do some hackery with a program to work it all out, see https://gist.github.com/rvagg/c9ef9dfc9dbe23ac0f7e for my program and data files to get this mapping. I've ended up with:

    rewrite ^/\d+/\d+/\d+/(?:node-v(?:ersion-)?|version-)(\d+)[-\.](\d+)[-\.](\d+).*$ https://nodejs.org/en/blog/release/v$1.$2.$3/ permanent;

    rewrite ^/2015/05/16/node-leaders-are-building-an-open-foundation/$ https://nodejs.org/en/blog/community/node-leaders-building-open-neutral-foundation/ permanent;
    rewrite ^/2015/05/16/the-nodejs-foundation-benefits-all/$ https://nodejs.org/en/blog/community/foundation-benefits-all/ permanent;
    rewrite ^/2014/01/17/nodejs-road-ahead/$ https://nodejs.org/en/blog/nodejs-road-ahead/ permanent;
    rewrite ^/2013/12/03/bnoordhuis-departure/$ https://nodejs.org/en/blog/uncategorized/bnoordhuis-departure/ permanent;
    rewrite ^/2013/11/26/npm-post-mortem/$ https://nodejs.org/en/blog/npm/2013-outage-postmortem/ permanent;
    rewrite ^/2013/10/22/cve-2013-4450-http-server-pipeline-flood-dos/$ https://nodejs.org/en/blog/vulnerability/http-server-pipeline-flood-dos/ permanent;
    rewrite ^/2015/05/08/transitions/$ https://nodejs.org/en/blog/community/transitions/ permanent;
    rewrite ^/2015/05/08/next-chapter/$ https://nodejs.org/en/blog/community/next-chapter/ permanent;
    rewrite ^/2013/02/08/peer-dependencies/$ https://nodejs.org/en/blog/npm/peer-dependencies/ permanent;
    rewrite ^/2012/12/21/streams2/$ https://nodejs.org/en/blog/feature/streams2/ permanent;
    rewrite ^/2012/09/30/bert-belder-libuv-lxjs-2012/$ https://nodejs.org/en/blog/video/bert-belder-libuv-lxjs-2012/ permanent;
    rewrite ^/2012/05/08/bryan-cantrill-instrumenting-the-real-time-web/$ https://nodejs.org/en/blog/video/bryan-cantrill-instrumenting-the-real-time-web/ permanent;
    rewrite ^/2012/05/07/http-server-security-vulnerability-please-upgrade-to-0-6-17/$ https://nodejs.org/en/blog/vulnerability/http-server-security-vulnerability-please-upgrade-to-0-6-17/ permanent;
    rewrite ^/2012/05/02/multi-server-continuous-deployment-with-fleet/$ https://nodejs.org/en/blog/module/multi-server-continuous-deployment-with-fleet/ permanent;
    rewrite ^/2012/04/25/profiling-node-js/$ https://nodejs.org/en/blog/uncategorized/profiling-node-js/ permanent;
    rewrite ^/2012/03/28/service-logging-in-json-with-bunyan/$ https://nodejs.org/en/blog/module/service-logging-in-json-with-bunyan/ permanent;
    rewrite ^/2012/02/27/managing-node-js-dependencies-with-shrinkwrap/$ https://nodejs.org/en/blog/npm/managing-node-js-dependencies-with-shrinkwrap/ permanent;
    rewrite ^/2011/12/15/growing-up/$ https://nodejs.org/en/blog/uncategorized/growing-up/ permanent;
    rewrite ^/2011/10/26/version-0-6/$ https://nodejs.org/en/blog/uncategorized/version-0-6/ permanent;
    rewrite ^/2011/10/05/an-easy-way-to-build-scalable-network-programs/$ https://nodejs.org/en/blog/uncategorized/an-easy-way-to-build-scalable-network-programs/ permanent;
    rewrite ^/2011/09/23/libuv-status-report/$ https://nodejs.org/en/blog/uncategorized/libuv-status-report/ permanent;
    rewrite ^/2011/09/08/ldapjs-a-reprise-of-ldap/$ https://nodejs.org/en/blog/uncategorized/ldapjs-a-reprise-of-ldap/ permanent;
    rewrite ^/2011/08/29/some-new-node-projects/$ https://nodejs.org/en/blog/uncategorized/some-new-node-projects/ permanent;
    rewrite ^/2011/08/12/the-videos-from-node-meetup/$ https://nodejs.org/en/blog/uncategorized/the-videos-from-node-meetup/ permanent;
    rewrite ^/2011/08/03/node-meetup-this-thursday/$ https://nodejs.org/en/blog/uncategorized/node-meetup-this-thursday/ permanent;
    rewrite ^/2011/07/11/evolving-the-node-js-brand/$ https://nodejs.org/en/blog/uncategorized/evolving-the-node-js-brand/ permanent;
    rewrite ^/2011/06/24/porting-node-to-windows-with-microsoft.+s-help/$ https://nodejs.org/en/blog/uncategorized/porting-node-to-windows-with-microsofts-help/ permanent;
    rewrite ^/2011/05/01/npm-1-0-released/$ https://nodejs.org/en/blog/npm/npm-1-0-released/ permanent;
    rewrite ^/2011/04/29/trademark/$ https://nodejs.org/en/blog/uncategorized/trademark/ permanent;
    rewrite ^/2011/04/28/node-office-hours-cut-short/$ https://nodejs.org/en/blog/uncategorized/node-office-hours-cut-short/ permanent;
    rewrite ^/2011/04/07/npm-1-0-link/$ https://nodejs.org/en/blog/npm/npm-1-0-link/ permanent;
    rewrite ^/2011/04/05/development-environment/$ https://nodejs.org/en/blog/uncategorized/development-environment/ permanent;
    rewrite ^/2014/12/05/listening-to-the-community/$ https://nodejs.org/en/blog/advisory-board/listening-to-the-community/ permanent;
    rewrite ^/2014/12/03/advisory-board-update/$ https://nodejs.org/en/blog/advisory-board/advisory-board-update/ permanent;
    rewrite ^/2011/03/25/jobs-nodejs-org/$ https://nodejs.org/en/blog/uncategorized/jobs-nodejs-org/ permanent;
    rewrite ^/2011/03/24/npm-1-0-global-vs-local-installation/$ https://nodejs.org/en/blog/npm/npm-1-0-global-vs-local-installation/ permanent;
    rewrite ^/2011/03/24/office-hours/$ https://nodejs.org/en/blog/uncategorized/office-hours/ permanent;
    rewrite ^/2011/03/18/npm-1-0-the-new-ls/$ https://nodejs.org/en/blog/npm/npm-1-0-the-new-ls/ permanent;
    rewrite ^/2011/03/18/welcome-to-the-node-blog/$ https://nodejs.org/en/blog/video/welcome-to-the-node-blog/ permanent;
    rewrite ^/2014/07/31/v8-memory-corruption-stack-overflow/$ https://nodejs.org/en/blog/vulnerability/v8-memory-corruption-stack-overflow/ permanent;
    rewrite ^/2014/07/29/building-nodejs-together/$ https://nodejs.org/en/blog/community/building-nodejs-together/ permanent;
    rewrite ^/2014/06/16/openssl-and-breaking-utf-8-change/$ https://nodejs.org/en/blog/vulnerability/openssl-and-utf8/ permanent;
    rewrite ^/2014/06/11/notes-from-the-road/$ https://nodejs.org/en/blog/uncategorized/notes-from-the-road/ permanent;

    rewrite ^/(.*)$ https://nodejs.org/en/blog/ permanent;

with the following mapping not working yet:

(200) /2014/01/15/the-next-phase-of-node-js/ -> https://nodejs.org/en/blog/
(404) /2013/02/07/node-v0-9-9-unstable/ -> https://nodejs.org/en/blog/release/v0.9.9/
(200) /2013/07/16/download-statistics/ -> https://nodejs.org/en/blog/

They'll have to be manually done because you've gone and changed their names.

rvagg commented 9 years ago

(edited previous comment to remove unnecessary nginx fluff)

rvagg commented 9 years ago

Edited post and program after adding manual mappings and now I'm down to three not-working redirects and I'm moving on. If you want me to add any new redirects for the blog then let me know.

fhemberger commented 9 years ago

@schisma Let's rather have less, precise content than just filling the page just to make it scroll. ;)

fhemberger commented 9 years ago

"latest" on the front page is v3.2.0, are we OK with that?

We're pulling the first element (= highest semver release) from the index.json. Fortunately @phillipj put that into a separate variable, so this can be changed easily: https://github.com/nodejs/new.nodejs.org/blob/master/build.js#L55

fhemberger commented 9 years ago

What also comes to my mind for the list: Are we okay with the content? We mostly just moved everything from nodejs.org over, but does it reflect the current situation? E.g. getting involved, code contributions, etc.

At least before we start translating everything, we should try to weed out and shorten some of the texts. Otherwise they will be had to maintain and become outdated quickly in the future.

rvagg commented 9 years ago

re content, I'm not fussed if we start with existing and update over time, the important part is to migrate to the new server so we can iterate quicker.

re redirects, it turns out we're still pretty far off but I'd really like to get this into a state where we can switch over today if at all possible.

What I've done is taken a scrape through the 1 month of logs on the old server and found all of the URLs that get hit that don't 404, then sorted by number of hits. Then I've run those URLs against the current server to see what happens and weeded out all of the 200's and remove everything with "nightlies" in it (a lot of them). I've fixed up a bunch of them (the whole /docs/ directory was missing from my config) but I'm left with quite a lot.

See full gist for gory details: https://gist.github.com/rvagg/f4a24312053af1195824#file-statuses_non200-txt

Or jump to the pruned list of non-200's that we should look at and resolve where possible, particularly at the higher end of the list: https://gist.githubusercontent.com/rvagg/f4a24312053af1195824/raw/54b5cc6d37c1b92ce6791bf26dbe7dc0494a386a/statuses_non200.txt

fhemberger commented 9 years ago

@rvagg Working on it!

Update: After removing all the drive-by scans for vulnerabilities, the list doesn't look that bad. ;)

rvagg commented 9 years ago

Lots of docs, prior to the late v0.10.x docs restyle, are missing https://nodejs.org/images/logo-light.png when viewed on the new site, e.g. https://nodejs.org/docs/v0.10.30/api/, can we put that one into this repo or should I make a special alias just for this and store it somewhere else?

fhemberger commented 9 years ago

@rvagg Just added the logo as well.

Now, moar redirects (might contain some duplicates):

# Website

rewrite ^/about/$                           https://nodejs.org/en/about/ permanent;
rewrite ^/about/advisory-board/$            https://nodejs.org/en/about/organization/ permanent;
rewrite ^/about/advisory-board/members/$    https://nodejs.org/en/about/organization/ permanent;
rewrite ^/about/organization/$              https://nodejs.org/en/about/organization/ permanent;
rewrite ^/about/organization/tsc-meetings/(\d{4}-\d{2}-\d{2})/$                https://nodejs.org/en/foundation/tsc/minutes/$1/ permanent;
rewrite ^/about/organization/tsc-meetings/(\d{4}-\d{2}-\d{2})/minutes.html$    https://nodejs.org/en/foundation/tsc/minutes/$1/ permanent;
rewrite ^/about/releases/$                  https://nodejs.org/en/about/releases/ permanent;
rewrite ^/about/resources/$                 https://nodejs.org/en/about/resources/ permanent;
rewrite ^/about/security/$                  https://nodejs.org/en/security/ permanent;
rewrite ^/about/trademark/$                 https://nodejs.org/en/about/trademark/ permanent;
rewrite ^/blog/$                            https://nodejs.org/en/blog/ permanent;
rewrite ^/community/$                       https://nodejs.org/en/get-involved/ permanent;
rewrite ^/foundation/$                      https://nodejs.org/en/foundation/ permanent;

# All the release blog posts should be covered by this one
rewrite ^/\d{4}/\d{2}/\d{2}/(?:node-v(?:ersion-)?|version-)(\d+)[-\.](\d+)[-\.](\d+).*$ https://nodejs.org/en/blog/release/v$1.$2.$3/ permanent;

# Other blog posts
rewrite ^/\d{4}/\d{2}/\d{2}/(.*)$      https://nodejs.org/en/blog/$1 permanent;
rewrite ^/\d{4}/(\d{2}/)?(\d{2}/)?$    https://nodejs.org/en/blog/ permanent;

# Not sure about this one (Staging releases v0.10.40 and v0.12.6)
rewrite ^/dist/staging/(.*)$         https://nodejs.org/dist/$1 permanent;

# FIXME: Wrong redirects in existing list!
rewrite ^/documentation/api/(.*)$    https://nodejs.org/api/$1 permanent;

# What should happen with links to node.js < v0.8.x?
rewrite ^/docs/v\d+\.\d+\.\d+/$            https://nodejs.org/api/ permanent;
rewrite ^/docs/v\d+\.\d+\.\d+/api/(.*)$    https://nodejs.org/api/$1 permanent;

# API docs redirects
rewrite ^/docs/api$               https://nodejs.org/api/ permanent;
rewrite ^/docs/api/(.*)$          https://nodejs.org/api/$1 permanent;
rewrite ^/addons.html$            https://nodejs.org/api/addons.html permanent;
rewrite ^/assert.html$            https://nodejs.org/api/assert.html permanent;
rewrite ^/buffer.html$            https://nodejs.org/api/buffer.html permanent;
rewrite ^/child_process.html$     https://nodejs.org/api/child_process.html permanent;
rewrite ^/cluster.html$           https://nodejs.org/api/cluster.html permanent;
rewrite ^/console.html$           https://nodejs.org/api/console.html permanent;
rewrite ^/crypto.html$            https://nodejs.org/api/crypto.html permanent;
rewrite ^/debugger.html$          https://nodejs.org/api/debugger.html permanent;
rewrite ^/dgram.html$             https://nodejs.org/api/dgram.html permanent;
rewrite ^/dns.html$               https://nodejs.org/api/dns.html permanent;
rewrite ^/documentation.html$     https://nodejs.org/api/documentation.html permanent;
rewrite ^/domain.html$            https://nodejs.org/api/domain.html permanent;
rewrite ^/errors.html$            https://nodejs.org/api/errors.html permanent;
rewrite ^/events.html$            https://nodejs.org/api/events.html permanent;
rewrite ^/fs.html$                https://nodejs.org/api/fs.html permanent;
rewrite ^/globals.html$           https://nodejs.org/api/globals.html permanent;
rewrite ^/http.html$              https://nodejs.org/api/http.html permanent;
rewrite ^/https.html$             https://nodejs.org/api/https.html permanent;
rewrite ^/modules.html$           https://nodejs.org/api/modules.html permanent;
rewrite ^/net.html$               https://nodejs.org/api/net.html permanent;
rewrite ^/os.html$                https://nodejs.org/api/os.html permanent;
rewrite ^/path.html$              https://nodejs.org/api/path.html permanent;
rewrite ^/process.html$           https://nodejs.org/api/process.html permanent;
rewrite ^/punycode.html$          https://nodejs.org/api/punycode.html permanent;
rewrite ^/querystring.html$       https://nodejs.org/api/querystring.html permanent;
rewrite ^/readline.html$          https://nodejs.org/api/readline.html permanent;
rewrite ^/repl.html$              https://nodejs.org/api/repl.html permanent;
rewrite ^/stream.html$            https://nodejs.org/api/stream.html permanent;
rewrite ^/string_decoder.html$    https://nodejs.org/api/string_decoder.html permanent;
rewrite ^/synopsis.html$          https://nodejs.org/api/synopsis.html permanent;
rewrite ^/timers.html$            https://nodejs.org/api/timers.html permanent;
rewrite ^/tls.html$               https://nodejs.org/api/tls.html permanent;
rewrite ^/tty.html$               https://nodejs.org/api/tty.html permanent;
rewrite ^/url.html$               https://nodejs.org/api/url.html permanent;
rewrite ^/util.html$              https://nodejs.org/api/util.html permanent;
rewrite ^/v8.html$                https://nodejs.org/api/v8.html permanent;
rewrite ^/vm.html$                https://nodejs.org/api/vm.html permanent;
rewrite ^/zlib.html$              https://nodejs.org/api/zlib.html permanent;

# Somebody seems to link npm packages (340 of them) to nodejs.org
rewrite ^/nodejs/dist/?$        https://www.npmjs.com/ permanent;
rewrite ^/nodejs/dist/(.*)$     https://www.npmjs.com/package/$1 permanent;

# RSS Feeds
rewrite ^/(atom|feed|rss)(/|\.xml)$       https://nodejs.org/en/feed/blog.xml permanent;
rewrite ^/feed/release/$                  https://nodejs.org/en/feed/releases.xml permanent;
rewrite ^/feed/vulnerability/$            https://nodejs.org/en/feed/vulnerability.xml permanent;

# Asset rewrites
rewrite ^/robots.txt$                 https://nodejs.org/static/robots.txt permanent;
rewrite ^/.*favicon\.ico$             https://nodejs.org/static/favicon.ico permanent;
rewrite ^/apple-touch-icon.*\.png$    https://nodejs.org/static/apple-touch-icon.png permanent;
rewrite ^/trademark-policy.pdf$       https://nodejs.org/static/documents/trademark-policy.pdf permanent;

rewrite ^/logos/                      https://nodejs.org/static/images/logos/ permanent;
rewrite ^/logos/monitor.png           https://nodejs.org/static/images/logos/monitor.png permanent;
rewrite ^/logos/nodejs(.*)$           https://nodejs.org/static/images/logos/nodejs$1 permanent;

# Foundation member logos
rewrite ^/images/logos/apigee_logo_md.png$     https://nodejs.org/static/images/foundation/apigee_logo_md.png permanent;
rewrite ^/images/logos/codefreshLogo.png$      https://nodejs.org/static/images/foundation/codefreshLogo.png permanent;
rewrite ^/images/logos/codefreshLogo2.png$     https://nodejs.org/static/images/foundation/codefreshLogo2.png permanent;
rewrite ^/images/logos/digitaloceanLogo.png$   https://nodejs.org/static/images/foundation/digitaloceanLogo.png permanent;
rewrite ^/images/logos/famousLogo.jpg$         https://nodejs.org/static/images/foundation/famousLogo.jpg permanent;
rewrite ^/images/logos/famousLogo.png$         https://nodejs.org/static/images/foundation/famousLogo.png permanent;
rewrite ^/images/logos/fidelityLogo.png$       https://nodejs.org/static/images/foundation/fidelityLogo.png permanent;
rewrite ^/images/logos/godaddyLogo.png$        https://nodejs.org/static/images/foundation/godaddyLogo.png permanent;
rewrite ^/images/logos/grouponLogo.png$        https://nodejs.org/static/images/foundation/grouponLogo.png permanent;
rewrite ^/images/logos/ibmLogo.png$            https://nodejs.org/static/images/foundation/ibmLogo.png permanent;
rewrite ^/images/logos/intelLogo.png$          https://nodejs.org/static/images/foundation/intelLogo.png permanent;
rewrite ^/images/logos/joyentLogo.svg$         https://nodejs.org/static/images/foundation/joyentLogo.svg permanent;
rewrite ^/images/logos/microsoftLogo.png$      https://nodejs.org/static/images/foundation/microsoftLogo.png permanent;
rewrite ^/images/logos/microsoftLogo2.png$     https://nodejs.org/static/images/foundation/microsoftLogo2.png permanent;
rewrite ^/images/logos/modulusLogo.png$        https://nodejs.org/static/images/foundation/modulusLogo.png permanent;
rewrite ^/images/logos/nearformLogo.png$       https://nodejs.org/static/images/foundation/nearformLogo.png permanent;
rewrite ^/images/logos/nearformLogo2.png$      https://nodejs.org/static/images/foundation/nearformLogo2.png permanent;
rewrite ^/images/logos/nodesourceLogo.png$     https://nodejs.org/static/images/foundation/nodesourceLogo.png permanent;
rewrite ^/images/logos/npmLogo.png$            https://nodejs.org/static/images/foundation/npmLogo.png permanent;
rewrite ^/images/logos/paypalLogo.png$         https://nodejs.org/static/images/foundation/paypalLogo.png permanent;
rewrite ^/images/logos/sapLogo.png$            https://nodejs.org/static/images/foundation/sapLogo.png permanent;
rewrite ^/images/logos/saucelabsLogo.png$      https://nodejs.org/static/images/foundation/saucelabsLogo.png permanent;
rewrite ^/images/logos/saucelabsLogo2.png$     https://nodejs.org/static/images/foundation/saucelabsLogo2.png permanent;
rewrite ^/images/logos/strongloopLogo.png$     https://nodejs.org/static/images/foundation/strongloopLogo.png permanent;
rewrite ^/images/logos/yldLogo.png$            https://nodejs.org/static/images/foundation/yldLogo.png permanent;
rewrite ^/images/logos/yldLogo2.png$           https://nodejs.org/static/images/foundation/yldLogo2.png permanent;

rewrite ^/images/(.*)               https://nodejs.org/static/images/$1 permanent;

Those should cover most cases of the statuses_non200.txt list.

fhemberger commented 9 years ago

Some people have subscribed to release and vulnerability feeds. We should continue those.
Is everybody okay that blog post URLs won't be prefixed with /YYYY/MM/DD any longer? At least we should show the date on the blog overview page.

rvagg commented 9 years ago

I'm +1 on releasing now in the current state, the only thing I'd like to see added is Google Analytics but since we don't seem to even have that on the old site then I guess we're not missing anything by making the switch as is.

@mikeal, @fhemberger, what's your call?

mikeal commented 9 years ago

I'm +1 but will defer to @fhemberger since he's been more involved than I have.

rvagg commented 9 years ago

@fhemberger fwiw I think moving away from /YYYY/MM/DD is a good call, although I would have ditched the categories too but it's not as big a deal. Re the vulnerability feed, I didn't know about it but I'll try and make sure it gets used properly. Might be worth documenting in our security docs though.

rvagg commented 9 years ago

oh, remaining nit - latest needs to be v0.12.7 not v3.2.0

fhemberger commented 9 years ago

There actually is a Google Analytics snippet on the old website: https://github.com/nodejs/nodejs.org/blob/master/doc/tracking.js

a) Do we want to continue using this exact same tracking ID in the future? b) I don't know who has access to the anlalytics backend.

fhemberger commented 9 years ago

Removed the io.js releases for now, latest is now v0.12.7.

As soon as Google Analytics is added and working for the site, I'm fine with switching.

rvagg commented 9 years ago

Mikeal is sorting an analytics account right now

fhemberger commented 9 years ago

Great, will be AFK now for a while … I'll check this thread again later.

fhemberger commented 9 years ago

Oh, one thing to consider: When we go live, we need to have the new navigation on the Docs pages as well.

rvagg commented 9 years ago

Yeah, we can't edit what's already there unfortunately, we have to maintain it (note to @nodejs/documentation: please make all docs/ self-contained, JS, CSS etc. included, preferably not with too much integration with the rest of the site).

Check out https://nodejs.org/docs/latest/ which is v0.12.7, this will remain along with previous versions of the same styling, e.g. https://nodejs.org/docs/v0.12.7/ so we have to maintain it. I'm seeing

So we should probably put these in somewhere permanent, either in /static/whatever, or I can put them in /docs/ somewhere, and we can put a redirect for them.

Too late for me to do anything now, gotta :zzz: and will make the switch if we're ready in ~9h or so. @fhemberger if you want to tackle these docs issues then by all means, you could check previous versions too if you can be bothered. Otherwise I can take that one. The Analytics code is the most important thing on your list I think.

mikeal commented 9 years ago

I've added analytics, let me know what your google accounts are so I can add you to it.

fhemberger commented 9 years ago

@rvagg I think we should put those files in /static/legacy for now and redirect to that.

I don't really get why the "docs" so far have been a complete copy of the entire website, instead of just the API docs. It would be great if we could update them to use the same look and feel as https://iojs.org/api/

therebelrobot commented 9 years ago

I'm gonna be signing on to look at this in a couple hours. Is there anything critical I can hop in and help for Thursday? (It is still Thursday, right?)

I'm planning on checking build, styling across browsers, and checking all links, going from there. I'll also be online for most of the night, so when @mikeal gets the analytics account sorted I can help with that too. I'll also take a look at the docs while I'm at it. If it's easy enough, I'll try to get the new navigation onto it.

rvagg commented 9 years ago

let's write off old docs and make sure @nodejs/documentation changes the way we ship /docs/ in the future. I'll get those legacy files in and the redirects up, I want to launch this thing in the next couple of hours

rvagg commented 9 years ago

@nodejs/collaborators I've just flipped the DNS switch to the new site, please tune in to any potential issues that you may experience out there in userland given all the dependencies on the site working in very particular ways. I'll be around to fight fires if anything comes up but please make sure they are surfaced either on this repo or the main nodejs/node repo.

Also, if you don't like the new site, then don't complain, contribute here.

fhemberger commented 9 years ago

@snostorm Do we still need the following files/dirs?

public/index.html
scripts/tasks/*
gulpfile.js

I'm thinking about moving a few things:

plugins -> scripts/plugins
build.js -> scripts/build.js
load-versions.js -> scripts/load-versions.js (and add npm task for it)

fhemberger commented 9 years ago

@mikeal Can you add me to Google Analytics please? My email address is on the readme: https://github.com/nodejs/new.nodejs.org/blob/master/README.md

(And as we're online now, I'm closing this issue)

mikeal commented 9 years ago

@fhemberger added, sorry that it took so long :(

fhemberger commented 9 years ago

@mikeal No worries! Wasn't sure you got my mail.

nodejs / nodejs.org

First release checklist #58

Content