All Projects → springernature → Frontend Playbook

springernature / Frontend Playbook

Licence: other
The Frontend Playbook

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to Frontend Playbook

guides
Dealerdirect guides for getting things done, be a programming role-model, coding in style and being the better colleague.
Stars: ✭ 21 (-94.68%)
Mutual labels:  best-practices, playbook
Forum
🍺 Portando discussões feitas em grupos (Facebook, Google Groups, Slack, Disqus) para o GitHub Discussions
Stars: ✭ 3,868 (+879.24%)
Mutual labels:  discussion, frontend
Beeva Best Practices
Best Practices and Style Guides in BEEVA
Stars: ✭ 335 (-15.19%)
Mutual labels:  best-practices, frontend
Guide
🍄 指北,A front end style guide.
Stars: ✭ 727 (+84.05%)
Mutual labels:  best-practices, frontend
Ios Handbook
Guidelines and best practices for excellent iOS apps
Stars: ✭ 337 (-14.68%)
Mutual labels:  best-practices, playbook
Kart
🎮 Frontend for RetroArch
Stars: ✭ 373 (-5.57%)
Mutual labels:  frontend
Filemanager
React based FileManager for browser ( + FS REST API for Node.js and Express)
Stars: ✭ 378 (-4.3%)
Mutual labels:  frontend
Ply
CSS inspection aided by visual regression pruning
Stars: ✭ 370 (-6.33%)
Mutual labels:  frontend
Conf
Конспекты докладов IT-конференций
Stars: ✭ 365 (-7.59%)
Mutual labels:  frontend
Create React App Typescript
DEPRECATED: Create React apps using typescript with no build configuration.
Stars: ✭ 3,759 (+851.65%)
Mutual labels:  frontend
Eslint Plugin Testing Library
ESLint plugin to follow best practices and anticipate common mistakes when writing tests with Testing Library
Stars: ✭ 384 (-2.78%)
Mutual labels:  best-practices
Mimic
Seamless client side mocking
Stars: ✭ 380 (-3.8%)
Mutual labels:  frontend
Aprenda Frontend
📚 Central de conhecimento sobre front-end
Stars: ✭ 381 (-3.54%)
Mutual labels:  frontend
Go Api Boilerplate
Go Server/API boilerplate using best practices DDD CQRS ES gRPC
Stars: ✭ 373 (-5.57%)
Mutual labels:  best-practices
Solidity Cheatsheet
Cheat sheet and best practices for solidity. Write smart contracts for Ethereum.
Stars: ✭ 384 (-2.78%)
Mutual labels:  best-practices
Kashti
Kashti is a dashboard for your Brigade pipelines.
Stars: ✭ 370 (-6.33%)
Mutual labels:  frontend
Gaze Detection
👀 Use machine learning in JavaScript to detect eye movements and build gaze-controlled experiences.
Stars: ✭ 376 (-4.81%)
Mutual labels:  frontend
Beam
✨ Expressive WebGL
Stars: ✭ 383 (-3.04%)
Mutual labels:  frontend
Hooks
FullStack | Zero Api | Using "React Hooks" to develop the back-end | Vite
Stars: ✭ 367 (-7.09%)
Mutual labels:  frontend
Unit Testing Tips
Unit testing tips by examples in PHP
Stars: ✭ 318 (-19.49%)
Mutual labels:  best-practices

The Frontend Playbook

This repo contains The Frontend Playbook. It details how we run software development and how we make web and mobile products together. It's filled with things we've learned based on our own experience and study of others' experiences.

The main motivator for this playbook is not to document a list of guidelines, but rather to create an opportunity to collaborate on them, and to gain consensus.

This is a living document that we contribute to in a public GitHub repo. Reasons for doing this in the open include (but are not limited to):

  1. Interacting with and learning from others. Receiving contributions from people who don't work here can help us, providing learning opportunities that we would not receive otherwise - for example, see this contribution from @rowanmanning.

  2. Providing a showcase for our work/ethics. This is really useful when hiring people (for both parties). We've had very positive feedback from interviewees - it's a great recruiting tool. It also means that people are quickly up and running when they join.

See "Changing the laws of engineering with pull requests" for an in depth explanation of how developing a playbook like this is of benefit.

Sections

There's no particular order to which you should read the playbook, but the Practices section is probably a good starting point.

Contributing

To contribute please clone the repo (or fork it if you're an external contributor), create a new branch for your changes, then create a pull request to merge your changes in.

Please keep discussion inside the issues and pull requests, avoiding Slack, hallway conversations etc. Remember that this repo is public, and the discussions we have can be of benefit to people apart from us.

Read the full contributor guide.

Key words

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this playbook are to be interpreted as described in RFC 2119.

License

The Frontend Playbook is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

You should have received a copy of the license along with this work. If not, see Creative Commons BY-NC-SA 4.0 license.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].