Typedoc: Domain typedoc.io not reachable, has status pendingDelete

[mrbigbunbury]

All links to typedoc.io are leading nowhere, because the domain is on status pendingDelete.

See whois typedoc.io:

Domain : typedoc.io
Status : pendingDelete
Expiry : 2016-08-04
Delete : 2016-11-03 00:30

[Edward-Lombe]

Where is the API documented elsewhere I wonder...

[aciccarello]

@Edward-Lombe you can build the documentation from the project source if you need. But I do think the website should be brought back.

[BurtHarris]

I too discovered the DNS entry for typedoc.io is expired. Similarly, the domain typestrong.org looks unattended.

Custom domains cost money, is there some reason these aren't hosted on https://pages.github.com/ ?

[johan-gorter]

Another free option is http://typedoc.js.org

[BurtHarris]

@sebastian-lenz and @blakeembrey seem to be the key contributors to this project, perhaps we can attract their attention by mentioning their names.

[blakeembrey]

Thanks. Someone had reached out on Twitter. I never had control over the websites, so if people are interested we can re-create the site under @TypeStrong.

[BurtHarris]

I think it would be a good idea to host it under TypeStrong. I don’t know what was there before, so I’m curious.

From: Blake Embrey [mailto:[email protected]]
Sent: Wednesday, August 17, 2016 4:16 PM
To: TypeStrong/typedoc [email protected]
Cc: Burt Harris [email protected]; Comment [email protected]
Subject: Re: [TypeStrong/typedoc] Domain typedoc.io not reachable, has status pendingDelete (#270)

Thanks. Someone had reached out on Twitter. I never had control over the websites, so if people are interested we can re-create the site under @TypeStrong https://github.com/TypeStrong .

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/TypeStrong/typedoc/issues/270#issuecomment-240578023 , or mute the thread https://github.com/notifications/unsubscribe-auth/AClv_wJNhB-J6BghKEmjGSEoQqAne9ufks5qg5ZGgaJpZM4Jd_ou . https://github.com/notifications/beacon/AClv_4ZvIZYx1LUJXuJfDOlKmyLpGPK3ks5qg5ZGgaJpZM4Jd_ou.gif

[blakeembrey]

I believe this is the existing content: https://github.com/TypeDoc.

[aciccarello]

Yeah, I think you are right. Should those get pulled into one repo and updated?

[blakeembrey]

Sure @aciccarello! Would you be interested in helping out with that?

[blakeembrey]

If someone is interested in setting that up (I can create an repo and add you to it), then I can purchase the domain and we can put things back how it was before.

[aciccarello]

@blakeembrey, I would like to but am in the process of moving and won't have any time soon 😢.

[ShadowManu]

Hi. I''ve just recently came across the typedoc project but my team may be interested in integrating typedoc in our projects. I could contribute a piece of my daily time next week to fix this and also see how it works for us. I'll confirm tomorrow.

[ShadowManu]

Btw, typestrong.org site looks having domain issues too.

[d-asensio]

I can help also, all we need to re-create the website is generate the docs with grunt, check the content of https://github.com/TypeDoc/typedoc.github.io and tie them toghether?

[blakeembrey]

@ShadowManu To be honest, I'm not even sure what the typestrong.org site held. Do you know?

@d-asensio Sounds good. If you want to replicate the content with gh-pages support, I can point a new domain there.

[ShadowManu]

@blakeembrey no idea

[d-asensio]

Okay @blakeembrey I will try to do it tomorrow ;)

[felixfbecker]

I like to use http://surge.sh/ in my projects. It is extremely simple, you just npm i -g surge and run the surge command inside a folder with a static site. You pick a custom subdomain and have your site online. Even better, Travis has native support for deploying to surge so you can update the site with every push (it can be built from the source inside CI).

[ShadowManu]

Sounds promising that surge thingy. @d-asensio you can contact me if yo want a dev partna' ;)

[WasabiFan]

@ShadowManu For the sake of maintainability, _please_ don't use 3rd-party tools like that. I would highly recommend sticking to known-good tools that are supported by GitHub.

Optimally, you should just move the existing code into the new repo which @blakeembrey has said he can give you -- which would be named appropriately for GitHub pages -- and then clean up the code and update the docs. Using GitHub Pages means that publish permissions are simple, and because it uses Jekyll, you can separate out common headers and structure into layouts to keep it clean and understandable. No CI build or other custom infrastructure is required, and there's a high likelihood that prospective contributors would already know how to work with Pages and Jekyll.

I'm not trying to be needlessly contrary, but I have watched many projects rise and fall because someone decided they wanted to use some brand new project in core infrastructure and then only later discovered that no one could maintain it.

[blakeembrey]

Thanks @WasabiFan. Although I believe it's easy enough to go either way with the correct setup ( there's a different set of benefits), in most cases it's unnecessary overhead when GitHub pages exists. I won't be committing to anything extra here either since we don't need any other features. @d-asensio has already been very helpful moving the existing site into http://github.com/TypeStrong/typedoc-site. The domain is set up, but I believe there's some extra work to be done yet.

For an application server that isn't directly related to an open source project that wants contributor ownership, you probably shouldn't be using GitHub pages and should look into tools like Surge (personally been using Stout + S3 + Cloudfront). But that discussion isn't relevant here, let's stick with ease of accessibility (for current and future maintainers). There will always be a number of issues where something out of the maintainers control will go offline when they don't have access - like this domain, for instance!

Edit: If anyone does solve resource sharing for teams, that would be a great step 😄 Unfortunately, most services aren't set up for "teams". That includes hosting services, domain registries, etc.

[d-asensio]

I'm agree with you @WasabiFan and because of that I have migrated the templates from http://docpad.org/ (which is used by https://github.com/TypeDoc/typedoc.github.io) to Jekyll.

@ShadowManu as @blakeembrey said there's some extra work to be done, so you can help me to generate the API documentation if you want 😄 .

[stocksr]

package.json also has the .io domain

[aciccarello]

I believe all related issues have been address.

[ca98am79]

Hi, we (at park.io) got typedoc.io if you guys want to use it.