-
Notifications
You must be signed in to change notification settings - Fork 74
Wrong link to the github repository for the http://sizzlejs.com/ website #113
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
Comments
Not sure where the sizzlejs.com web site is located, but there doesn't seem to be a repo for it in /jquery. @timmywil? |
It should be pretty obvious that sizzlejs.com has never been part of jquery-wp-content. It's a one-off that never got any attention. |
@scottgonzalez Does that mean we should delete line 261? |
Yeah. Note that it's already in the list of sites that don't use jquery-wp-content. |
Okay... I'll submit a PR then |
@scottgonzalez @dmethvin #114 resolves this issue |
We should probably first discuss the long-term plans with that site before just deciding to remove it everywhere. I'm fine with removing it from that list but we can't just let the site of one of our projects die. First of all, what was the reason the repo was removed and where does it live now? |
There was never a repository for the existing site. There was a repository for the new site, which contained a single page of content that was copy/pasted from the live site, but was never worked on and never deployed. You can see what state it was in on http://stage.sizzlejs.com/. Since nobody ever expressed any desire to work on it, and having the repo exist but not be the actual site was confusing, that repo was deleted a long time ago. |
Okay, thanks for the info. I'm +1 for removing it. |
This page provides the link to the github repository for the sizzleJS website. The link appears to be broken however. I tried searching for the repository for that website but I couldn't find one. Does it even exist?
The text was updated successfully, but these errors were encountered: