Displaying 1 to 20 from 39 results

Codelyzer - Static analysis for Angular projects.

A set of tslint rules for static code analysis of Angular TypeScript projects.You can run the static code analyzer over web apps, NativeScript, Ionic, etc.

css - :art: CSS: The Good Parts

The so-called "nico-style" brought to markdown. Because Style Guide.This style guide is a jab at solving collisions between CSS class names, and issues that ultimately lead to confusion, having to use !important rules, copying and pasting style declarations, and similarly awful aspects of CSS development.

js - :art: A JavaScript Quality Guide

This style guide aims to provide the ground rules for an application's JavaScript code, such that it's highly readable and consistent across different developers on a team. The focus is put on quality and coherence across the different pieces of your application.These suggestions aren't set in stone, they aim to provide a baseline you can use in order to write more consistent codebases. To maximize effectiveness, share the styleguide among your co-workers and attempt to enforce it. Don't become obsessed about code style, as it'd be fruitless and counterproductive. Try and find the sweet spot that makes everyone in the team comfortable developing for your codebase, while not feeling frustrated that their code always fails automated style checking because they added a single space where they weren't supposed to. It's a thin line, but since it's a very personal line I'll leave it to you to do the drawing.

javascript - JavaScript Style Guide

Note: this guide assumes you are using Babel, and requires that you use babel-preset-airbnb or the equivalent. It also assumes you are installing shims/polyfills in your app, with airbnb-browser-shims or the equivalent.1.1 Primitives: When you access a primitive type you work directly on its value.

styleguide-generators - An overview of automatic living styleguide generators

Pattern Libraries (or Style Guides) are a helpful tool in developing websites. Read more about Creating Style Guides at this A List Apart article. Maintaining a static Pattern Library (in HTML/CSS) is hard work and errorprone. There are, however, various tools that help us generate a dynamic Pattern Library or 'Living Style Guide'.

swift-style-guide - LinkedIn's Official Swift Style Guide

Make sure to read Apple's API Design Guidelines.Specifics from these guidelines + additional remarks are mentioned below.

catalog - Create living style guides using Markdown or React

Catalog lets you create beautiful living and fully interactive style guides using Markdown and React components. Please read the Catalog documentation (built with Catalog!) for detailed installation and usage instructions.

ruby-style-guide - :blue_book: Russian Version: A community-driven Ruby coding style guide.

Это руководство по оформлению кода на Руби дает передовые рекомендации. С его помощью обычный программист на Руби будет создавать код, который с легкостью смогут поддерживать и развивать другие обычные разработчики. В дополнение к настоящему сборнику вас может заинтересовать 📗 Rails: руководство по стилю оформления.

jekyll-style-guide - An opinionated guide to common Jekyll design patterns and anti-patterns.

An opinionated guide to common Jekyll design patterns and anti-patterns. Jekyll's incredibly flexible, but in some instances, the lack of common conventions make things harder for users.

relaxed.ruby.style - A Relaxed Style Guide for Ruby & Configuration for RuboCop

A more liberal style guide for RuboCop. It comes with a config file that deactivates some of RuboCop's features. It is meant as a less restrictive foundation that you can use directly or base your style discussions on. RuboCop is an amazing tool, still some of its default rules feel overly strict. This might distract you from the helpful messages.

fashion-show - Build consistent and versioned styleguides by including and running consistent lint files across projects

Build consistent and versioned styleguides by including and running consistent lint files across projects.Your styleguide should be verisoned and consistent across all of your projects. This means that you should only have ONE .jshintrc and/or .jscsrc file anywhere. But how can this be accomplished easily? By making your own styleguide using fashion-show.

populist-style - A (one day) auto-updating style at the mercy of the people, and only the people.

A (one day) auto-updating style at the mercy of the people, and only the people.Today it is still a bespoke set of rules. One has to have goals, no? The copy below is unfortunately a bit out of date compared to the latest eslint rules in index.js. They remain because reusing the English copy is very likely even with new and/or slightly different rules.

javascript - The official GoDaddy JavaScript styleguide.

Official GoDaddy JavaScript styleguide. It includes eslint packages for three use-cases and can be used as a standard in any new project.There are two ways to use this styleguide depending on your own tooling preference: directly using pre-included binaries or running eslint yourself with a custom .eslintrc config.

eslint-config-standard-jsx - ESLint Shareable Config for JSX support in JavaScript Standard Style

Shareable configs are designed to work with the extends feature of .eslintrc files. You can learn more about Shareable Configs on the official ESLint website.This Shareable Config adds extra JSX style rules to the baseline JavaScript Standard Style rules provided in eslint-config-standard. It doesn't assume that you're using React, so other virtual DOM libraries like virtual-dom and deku are supported.

We have large collection of open source products. Follow the tags from Tag Cloud >>

Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.