Welcome to closureplease.com! Now what?

[thanpolas]

Hi all!

I created the closureplease organization as a common place to word towards making Closure Library more awesome and reachable by a wider audience.

I have moved all my closure related projects to the organization and launched http://closureplease.com

In the future i plan on starting a campaign of blog posts and screencasts to [re?]introduce the Closure Library to the community, in the new context that modern tools and workflows provide.

Ping me on #closure-tools freenode or twitter for access to the org.

/cc @steida @rhysbrettbowen @izb @scottlangendyk @donaldpipowitch @nicolacity @jbenet @callumlocke @teppeis @hallettj @jarib @gmarty @urmuzov @fbzhong @dcodeIO @darsain @mpneuried ... and anyone else you think would be interested

[teppeis]

nice!

[izb]

Cool :)

[rhysbrettbowen]

Nice one Thanasis,

Is there going to be a blog section of the site? It would be great to get
people to post articles straight to the site, such as tutorials, overviews
of certain classes, 3rd party tools etc. I'd be more than happy to post
some, I've got a few on my site (http://rhysbrettbowen.com) that I can
clean up and use (got some posts about my libraries but also got one about
the difference between square bracket and dot notation that would be good
once I go back and edit it).

It would be good to get the site in sections - so putting the frameworks
and libraries in their own section.

Also some links to
http://closure-library.googlecode.com/svn/docs/closure_goog_base.js.htmlwould
be great.

I've got my hands full at the moment at the new job and I'm going to be
releasing a port of goog.ui.component for backbone as soon as I can get my
company to get their github account organized. Also I'll be talking in
April about Closure Tools in Philly (so I'll be mentioning this website)
and started writing a getting started with closure book (that is designed
more to get people up and running with the various build tools but also
will go in to the latest developments like closure stylesheets, results,
coffeescript, 3rd party tools, libraries, frameworks ide plugins, etc.) but
I'll try and get some content together to go on the site (I think I've got
a blog post on rhysbrettbowen.com about square vs dot notation and I'll see
what materials from my talks are can be turned in to blog posts).

expect some pull requests from me in the near future,
Rhys

On Tue, Mar 19, 2013 at 7:32 PM, Thanasis Polychronakis <
notifications@github.com> wrote:

Hi all!

I created the closureplease organization as a common place to word
towards making Closure Library more awesome and reachable by a wider
audience.

I have moved all my closure related projects to the organization and
launched http://closureplease.com

In the future i plan on starting a campaign of blog posts and screencasts
to [re?]introduce the Closure Library to the community, in the new context
that modern tools and workflows provide.

Ping me on #closure-tools freenode or twitterhttp://twitter.com/thanpolasfor access to the org.

/cc @steida https://github.com/steida @rhysbrettbowenhttps://github.com/rhysbrettbowen
@izb https://github.com/izb @scottlangendykhttps://github.com/scottlangendyk
@donaldpipowitch https://github.com/donaldpipowitch @nicolacityhttps://github.com/nicolacity
@jbenet https://github.com/jbenet @callumlockehttps://github.com/callumlocke
@teppeis https://github.com/teppeis @hallettjhttps://github.com/hallettj@jarib @gmarty @urmuzov @fbzhong @dcodeIO @darsain @mpneuried ... and
anyone else you think would be interested

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1
.

[thanpolas]

Rhys awesome,

that's the general idea of this project, lower the learning curve of Closure and evangelize about it.

Yes, sections are in order, I wanted to put out what we have and sit on it for a while so we can better understand what sections need to be created and how to organize the information. Please add what you have on the index.md file and we'll figure out how to organize it.

My current idea is to make the frontpage a product selling one, closure being the product. So that means that the goal is to have CTAs and flows that will help you get up to speed as fast as possible and with the less frustration possible. More experienced developers can find their way through the section links or deep-linking (e.g. closureplease.com/externs).

I'll open a new issue to discuss what these sections should be and how to properly organize the resources.

Rhys, Added you to the org.

[steida]

Great work!
btw: add please also this useful link .) https://code.google.com/p/closure-templates/source/browse/trunk/examples/

[wzr1337]

Nice!
You might want to add Google Closure Linter Grunt task from here:

https://github.com/wzr1337/grunt-closure-linter

[thanpolas]

@wzr1337 @steida, bit busy atm, please send pull requests