Skip to content
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

create website #169

Closed
junosuarez opened this issue Jun 23, 2015 · 14 comments

Comments

@junosuarez
Copy link

commented Jun 23, 2015

Whether or not we like it, a lot of javascript adoption happens in cargo-cult fashion based on how popular a thing is perceived to be and how much it looks like a "real thing." We use standard because we want our code to be consistent and have good defaults, and so we don't have to waste time with these little decisions. The less time we have to spend convincing other people we work with to do this, the better. Having a nice, memorable URL to send people to will help with standard adoption and help us put all this other stuff behind us.

@feross

This comment has been minimized.

Copy link
Member

commented Jun 24, 2015

Yes! Let's do it!

@pbrinkmeier

This comment has been minimized.

Copy link

commented Jun 24, 2015

What about standard.js.org?
We could register that here: http://dns.js.org/
Also, do we want a second repo or just a gh-pages branch?

I'd contribute 👍

@louh

This comment has been minimized.

Copy link

commented Jun 25, 2015

👍

@feross

This comment has been minimized.

Copy link
Member

commented Jun 28, 2015

@maxogden do you have any thoughts about how to get a site up and running? I know you've done this a bunch before for other projects 👍

@maxogden

This comment has been minimized.

Copy link
Contributor

commented Jul 24, 2015

@feross sorry missed your comment. I usually just fork a static site of another project that I like and modify it. In this case I think the site should have a 'paste your code here to check it with standard' thing, installation instructions and philosophy

could fork this http://moose-team.github.io/friends/

@bcoe

This comment has been minimized.

Copy link

commented Jul 25, 2015

I love the idea of having a website. Perhaps it could have a section that features projects that adhere to the standard format? Good way to show off the adoption happening.

@Flet

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

Had some fun today
http://flet.github.io/standard-www

This is just a site generated from the README.md (and RULES.md) using a theme I like :)

Agree with @bcoe that it would be cool to have a "Who's using it?" page. If the list of sites in clone.js were its own json file, it could be done with this generated site.

@feross

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

@Flet Nice!

@feross

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

@Flet

I just registered standardjs.com. Waiting for Linode support (apparently someone else has set up DNS for standardjs.com before - just need them to delete that old entry) and then I can point it at your repo.

Then we just need to add a CNAME file that contains standardjs.com to the repo and we're good :)

https://help.github.com/articles/setting-up-a-custom-domain-with-github-pages/

@Flet

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

Cool! Happy to transfer it to you as well for consistency and add contributors.

@feross

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

Okay, that's a good idea. Can you transfer it? Thanks!

@Flet

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

@feross

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

And now DNS is set up! http://standardjs.com should work!

If it doesn't work, give it a few hours... DNS is slow.

@feross

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

Now that we have a site, post site related issues here: https://github.com/feross/standard-www/issues

I'll close this now. Thanks so much @Flet!! 🐈 👍 🐈

@feross feross closed this Jul 28, 2015

@lock lock bot locked as resolved and limited conversation to collaborators May 11, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
8 participants
You can’t perform that action at this time.