Displaying 1 to 20 from 40 results

project-layout - Standard Go Project Layout

  •    Makefile

This is a basic layout for Go application projects. It's not an official standard defined by the core Go dev team; however, it is a set of common project layout patterns emerging in the Go ecosystem. Some of these patterns are more popular than others. It also has a number of small enhancements along with several supporting directories common to any large enough real world application. If you are trying to learn Go or if you are building a PoC or a toy project for yourself this project layout is an overkill. Start with something really simple (a single main.go file is more than enough). As your project grows keep in mind that it'll be important to make sure your code is well structured otherwise you'll end up with a messy code with lots of hidden dependencies and global state. When you have more people working on the project you'll need even more structure. That's when it's important to introduce a common way to manage packages/libraries. When you have an open source project or when you know other projects import the code from your project repository that's when it's important to have private (aka internal) packages and code. Clone the repository, keep what you need and delete everything else! Just because it's there it doesn't mean you have to use it all. None of these patterns are used in every single project. Even the vendor pattern is not unversal.

polyfill - JavaScript Polyfills, Shims and More

  •    Javascript

This is a collection of polyfills covering web platform features, from those defined as part of the ECMAScript standard to new web browser functionality. Most are for features shipping in major browsers. A few are experimental and called out as such, subject to change at any time. My philosophy is that it's better to write future-looking code that takes advantage of new Web platform APIs where possible, and fill in the gaps with polyfills. There is no effort to produce 100% compliant behavior, or to completely hide differences in browser behavior.

wpt - Test suites for Web platform specs — including WHATWG, W3C, and others

  •    HTML

The web-platform-tests Project is a W3C-coordinated attempt to build a cross-browser testsuite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors. Clone or otherwise get https://github.com/web-platform-tests/wpt.

HTTPolice - Lint for HTTP requests and responses

  •    Python

HTTPolice is a lint for HTTP requests and responses. It checks them for conformance to standards and best practices. As a command-line tool, it can read HAR files or raw HTTP/1.x TCP streams. HTTPolice just analyzes anything you feed into it. Thus, it can be used on requests and responses captured from a real process or test suite.


  •    CSharp

HL7.net groups all the neccessary code for managing HL7 standard. It makes it easy to add HL7 interoperability to your application. It is developed in C#.NET

geoint-standards - co-create and grow GEOINT standards transparenlty

  •    HTML

The GEOINT Standards Working Group (GWG) is a National System for Geospatial-Intelligence (NSG) forum that serves the Director, National Geospatial-Intelligence Agency (NGA) and the NGA Chief Information Officer who is the delegated functional manager for GEOINT architecture and standards, in executing the functional management responsibilities authorized in NSG Directive FM 1100, August 2, 2014. The GWG provides the forum for the coordination of GEOINT standard activities. The GWG is led and chaired by the NGA's Geospatial Intelligence Standards Center of Excellence (GSCOE). In addition to its designation as an NSG Functional Management forum, the GWG is a Joint Technical Working Group that participates in both the DoD and IC standards governance processes. In the DoD, the GWG votes and manages GEOINT standards lifecycle recommendations reported to the Information Technology Standards Committee (ITSC), the governing group responsible for developing and promoting standards interoperability in support of net-centricity within the Department of Defense (DoD). GWG recommendations for mandating standards for the DoD are approved by the DoD Architecture and Standards Review Group (ASRG). Approved GEOINT standards are then cited in the DoD Information Technology (IT) Standards Registry (DISR) [Account and PKI/CAC required].

commons - CommonJS Shim Library

  •    Javascript

This is a simple library for bootstrapping compatibility into the many nearly compatible implementations that exist. It provides shims to make it possible to interoperate with code not designed for compatibility and some modules to make getting started as quick and painless as possible. We should all be able to take advantage of the great work poured into the various javascript runtimes and well thought out inside them. The Javascript Commons is similar in nature to the Apache Commons -- just not quite as huge. You could also think of the commons package as like CommonJS, just without the J -- after all, the J stands for Java, and that's not really our style.

I-D - My Internet-Drafts

  •    HTML

These are some of the Internet-Drafts I've authored or contributed to. The top-level directory contains works in progress; "Abandoned" contains drafts I'm no longer pursuing. "Published" contains those that made it into an RFC, in one manner or another.

development - A repository for the discussion and publication of the CFPB development team standards

  •    Shell

A guide for the development team at the CFPB. Capital Framework is our modular front end framework. New projects should start with the Capital Framework and the file structure generated by generator-cf.

spdx.js - SPDX License Expression Syntax parser

  •    Javascript

Development on spdx.js has moved to separate, smaller packages. spdx-expression-parse and spdx-satisfies are direct successors to spdx.js.

calver - 📅 The web's go-to resource for Calendar Versioning info.

  •    CSS

CalVer is a software versioning convention based on calendar dates of project releases, instead of arbitrary numbers. There are many benefits to this approach, and multiple variations to custom fit all projects, from Ubuntu to Twisted to PyCharm to C itself and more. If you have questions, comments, issues, or enhancements, please feel free to open an issue.

zerover - 0️⃣ Minimalist versioning scheme for devs who can't be bothered.

  •    CSS

ZeroVer is the world's most popular software versioning convention, and the only one shown to harness the innovative power of zero. The benefits are innumerable and the effects on the software world are profound. Read more at 0ver.org.

coding-standards - A collection of the official Ortus Solutions coding standards :rocket:


This repository includes all of the Ortus coding style guides. In order to have auto formatting for VSCode we will use the beautify package: https://marketplace.visualstudio.com/items?itemName=HookyQR.beautify. Once you install it just copy over to the root of your project our Ortus: .jsbeautifyrc file which will be used to format js/cfml/html and css. Then proceed to open your VS Code global settings and look for the beautify section, copy it over to your custom user settings and make sure you add the extension of .cfc or the cfml language indicator to the javascript section. We will piggy back on the JS formatter.

MangoServer - A MongoDB implementation of the W3C Web Annotation Protocol

  •    Python

A MongoDB implementation of the W3C Web Annotation Protocol

som - Stanford open modules for python

  •    Python

These are basic Python based tools for working with data (likely images and text) on Google Cloud. The base API module implements a basic token/refresh authentication, and the identifiers module is an extension of that for the Stanford School of Medicine. For complete docs, please see our documentation base and examples that coincide with each.

vue-interop - Vue InterOp Standards


Vue InterOp aims to standardize component API and code style allowing developers to switch between UI component libraries.