api-guidelines - Microsoft REST API Guidelines

The Microsoft REST API Guidelines, as a design principle, encourages application developers to have resources accessible to them via a RESTful HTTP interface. To provide the smoothest possible experience for developers on platforms following the Microsoft REST API Guidelines, REST APIs SHOULD follow consistent design guidelines to make using them easy and intuitive.This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

guides - Design and development guides

Guides for programmers who want to be awesome. The intent of this repository is to collect and distribute links to useful coding style guides and development practices across the web. Any improvements or suggestions are welcome! See Contribution Guides.

awesome-guidelines - A curated list of high quality coding style conventions and standards.

•    Javascript

A curated list of high quality coding style conventions and standards. A set of guidelines for a specific programming language that recommend programming style, practices, and methods for each aspect of a program written in that language.

react-redux-typescript-guide - The complete guide to static typing in "React & Redux" apps using TypeScript

•    TypeScript

You should check out Playground Project located in the /playground folder. It is a source of all the code examples found in the guide. They are all tested with the most recent version of TypeScript and 3rd party type definitions (like @types/react or @types/react-redux) to ensure the examples are up-to-date and not broken with updated definitions. Playground was created in such a way that you can simply clone the repository locally and immediately play around on your own. It will help you to learn all the examples from this guide in a real project environment without the need to create some complicated environment setup by yourself.

Front-End-Checklist - 🗂 The perfect Front-End Checklist for modern websites and meticulous developers

•    Javascript

It is based on Front-End developers' years of experience, with the additions coming from some other open-source checklists. You can contribute to the Front-End Checklist App reading the README_APP file which explain everything about the project.

Front-End-Design-Checklist - 💎 The Design Checklist for Creative Web Designers and Patient Front-End Developers

The Design Checklist for Front-End Developers is an exhaustive list of elements which can help developers to analyse and understand web designs and ensure the quality of their Front-End development. The Design Checklist for Front-End Developers is an exhaustive list of elements which Web Designers and Front-End Developers need to take into consideration to facilitate their collaboration. The following elements are a mix between known practices and new elements based on a long experience analysing web designs.

Front-End-Performance-Checklist - 🎮 The only Front-End Performance Checklist that runs faster than the others

Performance is a huge subject, but it's not always a "back-end" or an "admin" subject: it's a Front-End responsibility too. The Front-End Performance Checklist is an exhaustive list of elements you should check or at least be aware of, as a Front-End developer and apply to your project (personal and professional). For each rule, you will have a paragraph explaining why this rule is important and how you can fix it. For more deep information, you should find links that will point to 🛠 tools, 📖 articles or 📹 medias that can complete the checklist.

zalando-howto-open-source - Open Source guidance from Zalando, Europe's largest online fashion platform

A guide to releasing an open-source project at Zalando, Europe's largest online fashion platform. Please feel free to use this as a template for your own organization's open source planning, policymaking, and development efforts. If there's a topic we've missed, or if you have any suggestions for making this better, let us know via our Issues tracker.We're really grateful to Software Lead Weekly, cron.weekly, Chris Aniszczyk (TODO Group), the folks at Datio Engineering, Thomas Lockney of Nike, Jamie Allen at Starbucks, Richard Seroter at Pivotal, Peter Zaitsev at Percona, Jonathan Lipps at Sauce Labs, and others for spreading the word about this doc.

Restful API Guidelines - A model set of guidelines for RESTful APIs, created by Zalando

•    Javascript

Great RESTful APIs look like they were designed by a single team. This promotes API adoption, reduces friction, and enables clients to use them properly. To build APIs that meet this standard, and to answer many common questions encountered along the way of RESTful API development, the Zalando Tech team has created this comprehensive set of guidelines. We have shared it with you to inspire additional discussion and refinement within and among your teams, and contribute our learnings and suggestions to the tech community at large.

erlang_guidelines - Inaka's Erlang Coding Guidelines

•    Erlang

If you find any bugs or have a problem while using this library, please open an issue in this repo (or a pull request :)). Spaces over tabs, 2 space indentation.

dotCommand

•    CSharp

dotCommand project explores various .NET implementations of Command design pattern, by providing and measuring those implementations.

patterns & practices: Application Architecture Guide 2.0

patterns & practices Application Architecture Guide 2.0 Community Site

Coding Guidelines for C# 3.0, C# 4.0 and C# 5.0

A set of coding guidelines for C# 3.0, 4.0 and 5.0, design principles, layout rules, ReSharper settings and Static Code Analysis rulesets

Templex - The TFS Process Template Library

Set your templates free! Share and discover Team Foundation Server process templates and other goodies here.

patterns & practices Improving Web Services Security Guide

Guidance for building secure Web services. Includes design and implementation guidance for WCF security scenarios. Prescriptive guidance includes guidelines, checklists, key security practices, end-to-end application scenarios, and step-by-step How Tos.

zappr - An agent that enforces guidelines for your GitHub repositories

•    Javascript

Approvals for Github pull requests.

iOS-handbook - Guidelines and best practices for excellent iOS apps

Don't forget to check out our favorite suite of components and helper methods and the other B&B iOS repos to see if we've already built something to help with what you're trying to do.

guidelines - Sophilabs' Guidelines

These are the guidelines that lead us to create beautiful software. Please contribute to it following this contribution guidelines.The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

docs - Documentation of ZEIT now and other services

•    Javascript

This is the public documentation for ZEIT now all other related services. You can access this documentation online at https://zeit.co/docs .Download the copy of this repostory.

guidelines - General Inaka Guidelines

This document describes the general guidelines we expect all our members (a.k.a. inakos) to comply with in all of our projects. For code guidelines and best practices regarding specific languages, please refer to the corresponding inaka/[language]_guidelines github repo. In this same repo we also have several other guideline files, specifically tailored to some languages or platforms (e.g. iOS, Android, Erlang, Elixir, etc.). Check them out to find out how we work in those particular cases.