standards/meta

The Standard to create Open Standards

meta's Issues

`feross/standard` pkg and `standards/standard` CLI

• can be transferred here
• i think it should be rewritten
• it will continue to have backward compatibility
• it would support flags for
  • javascript (gfm) code blocks in md files (maybe only READMEs?)
  • checking against standards/readme standard for README code style
  • semistandard case, cuz it is just overriding of one prop of config that is passed to eslint
  • using the other style standards from the org (assuming which to use on per extension basis?)
  • using -u flag for .useing other standards and passing them to standards/engine?
  • and all current flags
  • support for different reporters with -R
• it would be just CLI
• eslint-(semi)standard-config (aka shareable configs) to be in org
• standards/js maybe core of standards/standard backward compatible, just for js, lightweight?
  • maybe it would be my experimental implementation of feross/standard using my glob-fs and micromatch instead of node-glob + minimatch implementation when it is almost rdy and when whole stack of github.com/vinyljs stack is done

TBC...

Badges and Logos

For each of the standards, some like feross/standard

[![js-standard-style](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard)

and

[![js-semistandard-style](https://cdn.rawgit.com/flet/semistandard/master/badge.svg)](https://github.com/Flet/semistandard)

And the badge for all can be simple like

[![](https://img.shields.io/badge/code%20style-standard-brightgreen.svg)](https://img.shields.io/badge/code%20style-standard-brightgreen.svg)

or for CSS Standard Style

[![](https://img.shields.io/badge/standard-css-brightgreen.svg)](https://img.shields.io/badge/standard-css-brightgreen.svg)

for HTML Standard Style

[![](https://img.shields.io/badge/standard-html-brightgreen.svg)](https://img.shields.io/badge/standard-html-brightgreen.svg)

and etc

standard-engine

• To be more general in first place
• To be in standars/engine
• Using (passing to it) different linters for each of the style standards.
• It is possible to transfer flet/standard-engine here or rewrite it?
• Without CLI in it, it would be core factory mechanism for loading lint configs and linting #3

Validate standards/meta v1.0.0

This issue is a symbolic request to validate the meta standard as a valid standard. It obviously is as it defined how it should be written. Standard-ception!

Javascript project standard

What is the purpose of this Issue?

• Propose a new Standard

Describe the purpose of this Issue a bit further

I would be really useful to have a common way to write Javascript projects. That would mean that a developer could easily identify certain things about the projects in order to work on it effortlessly.

There are many components to have into account like relying on @feross/standard or its forks which are slightly the same standard with some variations.

As far as how deep this standard should go, the premise is very simple and yet powerful. A standard should just cover what could be verifiable, whether is automatically through a very well supported tool or manually going through any project that asks for validation. For example, it would be very difficult to have verifiable code style guides without any automatic tool, like the one standardjs uses (running standard CLI once it is installed).

Also, a Javascript project is not just only about code style. It's also about certain files that needs to be present to have a very good idea about the project itself. For example, should a JS project have a package.json file (https://docs.npmjs.com/files/package.json) to describe dependencies and other useful information? Should it have a .editorconfig file (http://editorconfig.org) to describe IDE behaviors? Let's get the best practices together to have the best JS projects possible.

I'm just opening the discussion to hopefully get buy-in from other devs to work together towards a better developer experience for all.