-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
craftycomponents.com website down #12
Comments
Is it still linked to from anywhere in the docs? It's been down for quite a while; I thought references to it had been removed. There's a quasi-replacement here. |
I think i may have clicked a link in some 3rd party tutorial or guide or forum post. I was wondering around the internet looking for info on the update a couple a days ago. |
@starwed I didn't see a reference to the /components/ page anywhere in the docs. But some places in forums still reference it from when community members had posted about their creations. Also, the readme.md and the Website URL field on this CraftyComponents repo make a lot of references to craftycomponents.com specifically. |
Other than spread the word in such forum threads, and try to get tutorials updated, there's not much we can do. The folk who owned the URL didn't get back to us before it lapsed, and it now looks like someone else owns it.
I'll grep through the repo and try to remove such links. |
There's a reference here: http://craftyjs.com/api/Crafty-modules.html |
The description of the Google Group https://groups.google.com/forum/#!forum/craftyjs has a Modules link that refers to the old domain. |
Heh, this is still true for the readme.md of this repo... Worse yet is that the domain is now active again but obviously not crafty.js related. |
It appears this repository site craftycomponents.com is no longer active and the domain is showing as for sale.
Has the site been moved somewhere else? A subdomain of craftyjs.com would make sense / save the cost of an extra domain.
The text was updated successfully, but these errors were encountered: