Regarding the prototype, could you do that look inline with what is already there with the site header? While that looks cool, we were also going for continuity on all of the websites.

You can also see all of the design work and contribute at https://github.com/jquery/web-base-template

WTF? A font face just for that!?

To start, let's be professional here. WTF comments aren't helpful. I happen to dislike the font used for the subheader, but this is not a decision that will be made on a site-by-site basis. As we've already mentioned multiple times, this is part of a larger design. We can certainly make changes, but this is not a productive way to move forward with that. I've also expressed concerns about the perf of loading external fonts.

Do we really need the same element twice?

Your biggest complaint was that all you wanted was a search field. I think that alone should explain why the search field appears twice on the page.

Are them so important to stay alone on the sidebar?

I don't understand your question. Is your question "Do people find popular tags useful?" or is it "Shouldn't there be more information in the sidebar?" If the former, the answer is yes. If the latter, please actually make suggestions.

On a short page your footer does not work

Feel free to file an issue against web-base-template.

Then one of the jQuery developers suggested to create new lint section on the new site, something like plugins.jquery.com/lint , having just the plugin ajax search on it.

I think you mean /lite. I'm not a fan on this idea, it seems way to minimal and duplicative to me.

what about an entire ajax navigation?

What about it? That question alone provides nothing helpful. Are you asking for just autocomplete? Autocomplete + partial page loads as you type?

you could create a JSON (JSONP) API allowing the other pluigins websites to fetch from your official data (the same API could be used to make your website entirely an ajax app)

Yes, that's what I told you yesterday. I specifically asked for a proposal of an actual API. Reiterating this isn't going to get us anywhere. If you would like to use the API, please tell us what you want.

jQuery is going to drop the support for the old browsers right?! so where are the CSS3 transitions?

No, we're going to continue to support the same browsers we support today. I have no idea what this has to do with CSS3 transitions anyway.

To start, let's be professional here. WTF comments aren't helpful. I happen to dislike the font used for the subheader, but this is not a decision that will be made on a site-by-site basis. As we've already mentioned multiple times, this is part of a larger design. We can certainly make changes, but this is not a productive way to move forward with that. I've also expressed concerns about the perf of loading external fonts.

You are right, I am sorry, but watching a font so similar to "Comic sans" make me nervous because I thought it was banned since 2000.

Your biggest complaint was that all you wanted was a search field. I think that alone should explain why the search field appears twice on the page.

Maybe we could hide the smaller one just on the home page and then make it visible on the other pages. The one bigger is enough IMHO

I don't understand your question. Is your question "Do people find popular tags useful?" or is it "Shouldn't there be more information in the sidebar?" If the former, the answer is yes. If the latter, please actually make suggestions.

I meant the first, nevermind

Feel free to file an issue against web-base-template.

ok I will

I think you mean /lite. I'm not a fan on this idea, it seems way to minimal and duplicative to me.

sorry for the typo mistake, ok your position is clear: if you want help us then work on what is already done. I can't blame you for that

What about it? That question alone provides nothing helpful. Are you asking for just autocomplete? Autocomplete + partial page loads as you type?

jQuery pushed ajax techniques to the next level, $.ajax() is one of the methods that made jQuery so popular. I was just asking why is it not possible to realize the entire website like an ajax application? ( partial page loads, autocomplete, push notification etc.. )

Yes, that's what I told you yesterday. I specifically asked for a proposal of an actual API. Reiterating this isn't going to get us anywhere. If you would like to use the API, please tell us what you want.

I will do it in a different topic

No, we're going to continue to support the same browsers we support today. I have no idea what this has to do with CSS3 transitions anyway.

I am referring to this post http://blog.jquery.com/2012/06/28/jquery-core-version-1-9-and-beyond/

jQuery 2.0 (early 2013, not long after 1.9): This version will support the same APIs as jQuery 1.9 does, but removes support for IE 6/7/8 oddities such as borked event model, IE7 “attroperties”, HTML5 shims, etc.

this means that it is time to pimp jQuery plugins website with features (like CSS3 transitions) even if they are not completely supported by the old browsers.

anyway I will help you pushing some changes to the layout repo in the next days, keeping my prototype as a side project because it does not fit with all your big layout corporate redesign

You need to keep reading that post:

Our goal is for 1.9 and 2.0 to be interchangeable as far as the API set they support. When 2.0 comes out, your decision on which version to choose should be as simple as this: If you need IE 6/7/8 support, choose 1.9; otherwise you can use either 1.9 or 2.0.

jQuery is not dropping support for any browsers. We are simply providing two different versions with the same API but different browser support per version. The idea is to provide speed and size benefits when on newer browsers, but continue to support older browsers.

Anyway, that's completely unrelated to using CSS transitions on a web site. Do you have something in mind that should be transitioning?

As for leveraging ajax calls to make the website an app, some of those things could be added later but the biggest focus is exposure and ease of development. We have a lot of properties that need to be worked on. We are also using wordpress as our deployment platform.

This creates a few needs:

• provide pages that nginx can cache and serve without any processing
• provide pages that can be indexed well by google for discovery
• be easy to maintain moving forward

As for the side navigation regarding tags, I assume you resized the browser to see that the extra space for tags gets joined with the right side nav (there's some css3 media queries for ya? :p)

I like your desire to make the site more interactive and fun, which I assume is what your target is for pushing a single page app and using transitions between content. nav items, etc - but it's taken us this long to get here, and we want to make sure jQuery is accessible for all kinds of audiences. So if we can look pretty good and serve all of these needs, awesome. It sounds like you have some design sense and desire to help, so I look forward to seeing you get involved with web-base-template.

I could start with these simple tasks:

• Autofocus on the search field on the homepage
• box shadow transition on the search field when it receives the focus
• mega accordion for the contents under the big black search field
• animated dropdown menu (maybe a fade in)
• accordion for the plugin versions table

Autofocus on the search field on the homepage

ok

box shadow transition on the search field when it receives the focus

ok

mega accordion for the contents under the big black search field

What is a mega accordion? What content are you trying to hide and why?

animated dropdown menu (maybe a fade in)

ok

accordion for the plugin versions table

What information would you be showing?

Closing due to inactivity. If you'd like to contribute to the site, please file a separate issue for each task, but please do not file large changes if you don't plan on implementing them. Thanks.