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

Release 1.7.0 #3332

Closed
jashkenas opened this issue Jan 27, 2014 · 13 comments
Closed

Release 1.7.0 #3332

jashkenas opened this issue Jan 27, 2014 · 13 comments

Comments

@jashkenas
Copy link
Owner

One last thing that we need before releasing 1.7.0, is to port the current Ruby-based index.html.erb homepage into Node. It would allow any maintainer to be able to release point releases ... and I am no longer able to install Ultraviolet in such a way as to make the current implementation work as well.

@xixixao
Copy link
Contributor

xixixao commented Jan 27, 2014

Are you going for it? If not, I assume you don't want to use Jade, any preferred way of doing it?

@xixixao
Copy link
Contributor

xixixao commented Jan 27, 2014

I guess we could just do a regex on the code_for tags, put everything in the Cakefile.

@jashkenas
Copy link
Owner Author

I can't at the moment, so if you want to take a crack, feel free.

Let's leave it with basically the same structure, with some little things in the file, and the rest of the setup in the Cakefile. Just using a simple Underscore template for the index page would be fine. Or whatever you like, really. And then HighlightJS for the highlighting...

@epidemian
Copy link
Contributor

Isn't this exactly what #3198 did?

It seems to have been merged into gh-pages though, whereas @xixixao's doc updates where done on master.

What should we do? Do you we want to

  1. have gh-pages be a mirror of master that updates on each release, or
  2. make gh-pages have only the static pages files (index.html, extras/coffee-script.js, CSS styles, etc) plus documentation/* files, while master has src/* and lib/* but none of the coffeescript.org-specific stuff?

Both seem like good approaches to me. The first one might be the simplest, but the second one may have the best "separation of concerns" between branches. I'd vote for the first one.

@jashkenas
Copy link
Owner Author

#1, please. If we can just move it over, then great.

jashkenas added a commit that referenced this issue Jan 28, 2014
@jashkenas
Copy link
Owner Author

Boom.

A million thanks to @xixixao for putting in all of the final stretchwork to make this release happen. Cheers, buddy.

@aseemk
Copy link
Contributor

aseemk commented Jan 28, 2014

Woot! Thanks @xixixao.

@vendethiel
Copy link
Collaborator

Yay for @xixixao ;).

@davidchambers
Copy link
Contributor

xoxo @xixixao!

@vendethiel
Copy link
Collaborator

@davidchambers

EDIT : whoah, new design unfolding before me

@michaelficarra
Copy link
Collaborator

No! What have they done with the gradients?

@dashed
Copy link

dashed commented Jan 28, 2014

Wow. It actually happened. Awesome job @xixixao

And interesting GitHub design o.O

@xixixao
Copy link
Contributor

xixixao commented Jan 28, 2014

Someone at Github did casual npm install on unspecified coffee-script version and the new layout was hidden with coffee-script/register. Damn.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants