Just like our JavaScript libraries, we maintain the design and content of all our websites in the open, with everything available on GitHub. We do this for several reasons: It works for code. Open source development is collaborative, auditable, and decentralized — all qualities that should be part of working on design and documentation as … Continue reading →

Contributing to the jQuery project, and to any FOSS project for that matter, can be a rewarding experience both in terms of the way you can help yourself and projects you are working on, as well as the countless number of others you may help with your contribution. Taking that first step though, can be … Continue reading →

This page is a collection of tips and tricks for dealing with pull requests and managing the jQuery git repositories on GitHub. link Fetch the Pull RequestGithub stores the refs for each pull request on the main repo. Assuming you have the jquery repo set as your upstream remote, you can use the following git … Continue reading →

All of the sites that are part of the jQuery WordPress network use the following markup conventions to apply styling to elements. Please adhere to these conventions if you are working on any of our web sites. This page is a live example of these conventions in action. Tools & Libraries The jQuery sites are … Continue reading →

Linting Spacing Bad Examples Good Examples Object and Array Expressions Multi-line Statements Chained Method Calls Full File Closures Constructors Equality Type Checks Comments Quotes Semicolons Naming Conventions Global Variables DOM Node Rules Switch Statements link LintingUse JSHint to detect errors and potential problems. Every jQuery project has a Grunt task for linting all JavaScript files: … Continue reading →

Working With a Fork Never Commit On Master Branching Preparing To Commit Commit Guidelines Subject Long description References Your Pull Request We use git and GitHub's Pull Request system to review and accept all contributions of code, content and design to all of our projects. Your experience can be as pleasant as possible (for everyone) … Continue reading →

Triage, the process of reviewing incoming bug tickets, gathering more information about the situation, and verifying whether or not the report is valid, is a critical part of the day-to-day operation of all of our projects. Some new tickets are valuable reports of broken behavior, others are suggestions for enhancements both large and small, and … Continue reading →

For almost as long as jQuery has been around, its documentation has been an integral part of the project, from helping new users get up to speed to offering detailed explanations of features for seasoned developers. Currently, the jQuery Foundation manages API documentation and demos for its projects and provides a growing set of tutorials … Continue reading →

For good and valuable consideration, receipt of which I acknowledge, I hereby transfer to jQuery Foundation, Inc. (the "Foundation") my entire right, title, and interest (including all rights under copyright) in my changes and enhancements to any code or other work contributed by me to the open source project commonly known as the jQuery Project … Continue reading →

Like many Open Source projects, the majority of jQuery contributors are volunteers; their ability to contribute ebbs and flows with the demands of their professional and personal lives. As a result, jQuery projects are always looking for talented people who are motivated to contribute. New contributors sometimes make the mistake of starting with a pull … Continue reading →

link Before You Reportlink Make Sure It's a jQuery BugMany bugs reported to our bug trackers are actually bugs in user code, not in jQuery code. Keep in mind that just because your code throws an error and the console points to a line number inside of a jQuery project, this does not mean the … Continue reading →

Thank you for Your interest in the jQuery Foundation. This document clarifies the terms under which You, the person listed below, may make Contributions — which may include without limitation, software, bug fixes, configuration changes, documentation, or any other materials — to any of the projects owned or managed by the jQuery Foundation. Please complete … Continue reading →

link Formatting ConventionsOn many sites, prose (sites, README, docs, etc) is authored with GitHub Flavored Markdown. Some sites (e.g. api.jquery.com) use an XML-based markup system but the advice offered here for good writing still applies. link Writing StyleContent should be educational and accessible to a broad audience of developers. The primary target audience is beginning … Continue reading →

Unfortunately, there was an error checking the CLA signatures. The following authors don't have appropriate CLA signatures: Either the authors have not signed the CLA or the CLA signature does not match the name and email address in their git config. link Signing the CLAIf you haven't signed the CLA yet, simply visit the CLA … Continue reading →

With millions of jQuery users all over the world, there's always someone out there who needs a helping hand. Like many open source projects, the jQuery Foundation relies on community support channels like forums, IRC, and StackOverflow. Helping out with support is one of the best first steps you can take to get involved in … Continue reading →

In a sense, each of the different ways of getting involved that we detail on this site are all ways of contributing to the jQuery community, which we define quite liberally: helping to make any aspect of using jQuery Foundation projects better for other people. This, of course, includes things like filing and fixing bugs, … Continue reading →

This page outlines the style guide for CSS across all jQuery projects. link LintingUse CSSLint to detect errors and potential problems. Most jQuery projects have a Grunt task for linting all CSS files: grunt csslint. The options for CSSLint are stored in a .csslintrc file. Each .csslintrc file follows a specific format. All options must … Continue reading →

Linting Spacing Formatting HTML Semantics Reducing Markup Separation of Concerns Forms Comments This page outlines the style guide for HTML pages in all jQuery projects. These rules apply to web sites, demo pages, inline examples, test pages, etc. Exceptions are allowed for pages that must violate the rules by their very nature, e.g., a page … Continue reading →

Style guides aim to make a code base appear as if it were written by one meticulous programmer. As with many aspects of coding and writing, there can be differences of opinion about the best style. Contentious issues like "spaces versus tabs" or "semicolons or not" distract from the goal of writing code that works. … Continue reading →

link jQuery CorejQuery Core Won't-Fix issues are tracked and explained on a jQuery Wiki page. link jQuery UIlink change EventWidgets that enhance form elements manipulate their element's value programmatically, therefore we cannot guarantee that a native change event will fire when the element's value changes. These widgets do all provide a custom change event. For … Continue reading →