Debating Standards Roadmap

[RicCastelhano]

Please, use this channel to share ideas concerning which standards we should stick to, which additional standards we should adopt, and other ideas about the subject. Remark that we should debate for each language we use: PHP and WordPress, JavaScript, HTML, CSS (other if you think needed).

We, all, will have a meeting in a couple weeks to design a roadmap for our internal-book production (writing, revision, "shipping").

[RicCastelhano]

10UP Standard base: https://10up.github.io/Engineering-Best-Practices/

[RicCastelhano]

Our HandBook, a work-in-progress https://bitbucket.org/log-oscon/handbook

[Narayon]

I'll list all technologies that we currently use and open a section to add alternatives to discuss.

I don't think that this thread will be enough to talk about everything, but it can serve as a list of links to all threads that will be open - optimally, one for each specific suggestion for change.

All will be supported with in-person talks, presentations and examples, when needed, and it should be everyone responsibility to document those live inputs to the correspondent thread.

PHP:

Dependency manager:

• Composer

  Linter:

• PHPCS, with Wordpress-Extra standards, minus YodaConditions and LowercasedFilename rules

  Tests

• PHPUnit

JS:

Frameworks/Libs:

• Backbone (legacy)
• React (only used in some specific products)
• Handlebars

  Dependency manager:

• npm

  Bundler:

• Browserify, with some plugins
  • browserify-shim
  • watchify
  • hbsfy
  • aliasify
  • uglifyify
  • envify
  • babelify

    Linter:

• ESLint - with airbnb rules

  Transpiler:

• Babel

  Tests:

• Ava

CSS:

Libs:

• SASS
• Susy

  Linter:

• Stylelint

  Transpiler:

• PostCSS

Task runner/helpers:

• Gulp
• BrowserSync

Alternatives:

Alternatives must have a link to the discussion thread about pros/cons of that specific technology.
When adding alternatives, be aware of some suggestions:

• describe the technology;
• describe the problems that will solve;
• list some pros and cons;
• show some examples;
• show some numbers (performance, size, support, community).

Be aware that these are only suggestions. Some may not apply.

List of discussions threads:

• Webpack vs Browserify (not open yet)
• Add a template engine to PHP (not open yet)

I'll edit this comment to add missing technologies and alternatives.

[RicCastelhano]

Guys, I dont want to push up the pressure level but we must have this figured out and written down before the end of August. Please, avoid the urge to reinvent the wheel.