Lots of broken links in README

[guneysus]

There are only a few links are working in README. Unchecked links are broken or down.

• [ ] Full documentation is at pug-lang.com
• [ ] cssdeck interactive Pug syntax tutorial
• [ ] cssdeck interactive Pug logic tutorial

Implementations in other languages:

• [ ] php
• [ ] scala
• [x] ruby
• [ ] python
• [ ] java

Implementations in other languages:

• [ ] Emacs Mode
• [x] Vim Syntax
• [ ] TextMate Bundle
• [ ] Coda/SubEtha syntax Mode
• [ ] html2pug converter
• [ ] pug2php converter
• [ ] Pug Server Ideal for building local prototypes apart from any application

[KarbonKitty]

Pug-themed pages are generally unavailable; neither pug-lang.com nor pug-lang.org leads anywhere. Also pugjs.org, which was mentioned in renaming issue - it doesn't lead anywhere, too.

[pakastin]

How about pug.js.org? It's free! https://dns.js.org/

[TimothyGu]

@ForbesLindesay could you take a look at the domain issue?

[retrone]

@TimothyGu @ForbesLindesay

Why not make all the pug changes in a special renaming branch off master, and then only merge when it looks rock solid? You're going to get a lot of comments from people who don't know better, complaining about broken links, broken functionality, etc.

I love Jade/Pug, and I'm fine spending a few hours debugging or reviewing breakages due to the renaming (everything from file extensions, to breaking Jade plugins I use, to the website), but you're going to get a bunch of issues/user support asking what's wrong with various components, if you roll out the renaming onto master in dribs and drabs.

There also needs to be some sort of migration guide or FAQ for users (should you switch your NPM repo, should you rename extensions, etc). Ideally, most people don't have to do anything, but even just info about what to keep in mind with the name change would be helpful.

[ABM-Dan]

php's new library will be at https://github.com/pug-php/pug

[Ekranos]

I want to add the link for the browser support standalone version which doesn't work as well.