Release

[jzaefferer]

What is blocking the site from going live right now? There's obviously a lot of work left, but I'm sure most of it can be worked on even after lunching a first version of the site. The opportunity to release all new sites at once has passed, so that surely isn't a blocker anymore.

[addyosmani]

At the moment we're waiting on some fixes that need to be made to the existing build and compilation process. @ajpiano is going to start taking a look at this soon. Other than that it's mostly polish of site structure and of course content. We could do a launch once the build (and partially the structure) have been addressed.

[ajpiano]

1. Designs from 47media need to be implemented
2. Remove Ruby/nanoc dependency #120, removing the ruby dependency - I'm working on that this week, and am about halfway through with creating a grunt task that wraps Wintersmith for general use converting markdown content into jQuery Sites
3. It is a new site, and it doesn't have a "legacy" design so it can't really go live until the new master theme is launched.

[addyosmani]

@jzaefferer if we're not planning on launching all the sites at once, is there anything holding us back on 3? Haven't spoken to the design team in a while so unsure of what the status on the master theme is. Looked fairly close to complete last I saw it.

[jzaefferer]

1. can you provide specifics what's missing?
2. does it really make sense to integrate another site generator? Can't we just add markdown support to grunt-jquery-content? Seems like that would keep things as simple as we actually want them. Is nanoc doing anything beyond rendering markdown to html?
3. That was the idea originally, but it just doesn't make sense anymore. Just merge whatever you need into the legacy branch by cherry-picking. Works here http://qunitjs.com/

[ajpiano]

1. I saw the new mockup for the first time the night of the hackathon in SF, the interior is brand new and needs to be applied instead of the existing theme.
2. Nanoc is parsing yaml metadata and translating it into the metadata that goes into our leading JSON, and also preprocessing the data to honor an "order" that is specified in order.yaml, and also going to the Github API to find out information about the article author. Currently my grunt-wintersmith plugin is working to handle the basic churning through markdown, and creating html with script tags part, and thus all that's left for me to do here now is handle the custom logic that we had implemented in nanoc to begin with in grunt. I felt (and still feel like) wrapping around an existing node based generator in grunt is cleaner than reinventing that wheel inside of grunt-jquery-content. Furthermore, Wintersimth is similar to nanoc in that it provides a content tree that we can parse programmatically to generate additional views of the content, as we want. Essentially, I felt like the goal of 'keep things simple" means not writing our own markdown ssg when we can just leverage one that exists.
   In addition, nanoc is currently doing some custom pre-processing of our markdown to translate our code examples into <pre><code></code></pre>. For an example, see this Unfortunately, these amount to some custom markdown extensions that again, we shouldn't be inventing, so the plan is to switch over all the code blocks to use the github-flavoured-markdown convention of 3 backticks and the language.
3. I did not know that. Once the design changes in 1 and build changes in 2 are completed, I am glad to know we can backport it without waiting for the one magic day when "everything is ready"

[addyosmani]

I saw the new mockup for the first time the night of the hackathon in SF, the interior is brand new and needs to be applied instead of the existing theme.

Is this currently up anywhere accessible?

[ajpiano]

Sorry, yes, I meant to make that a link, here you go

[addyosmani]

@ajpiano Niiice. Thanks for the linkup!

[jzaefferer]

1. is this a blocker though? Last I saw from the existing design didn't look that bad.
2. well, this obviously is
3. yep, that day won't ever come. Now we just need to release whatever is ready, and we can still make a big fuzz about it once most sites are live

[ajpiano]

1. I wouldn't call it a blocker, but if it can happen contemporaneously with 2, we may as well have it ready for launch.

[buritica]

@ajpiano can you tell me which are priority issues and I'll help you tackle some? Where could I find the new designs if I wanted to help implementing them?

[addyosmani]

@ajpiano +1 to @buritica's question. If there's anything else that can be done to help move this along happy to try pitching in.

[sindresorhus]

I would be happy to pitch in too 💪, to get this vaporware released

[RedWolves]

Closing as this is a discussion and not an issue. Shooting to release in mid-November.