All Projects โ†’ vitorbritto โ†’ Workflow Guide

vitorbritto / Workflow Guide

๐Ÿ““ My workflow context and own code conventions

Labels

Projects that are alternatives of or similar to Workflow Guide

Expand
DevExpress XAF extension framework. ๐—น๐—ถ๐—ป๐—ธ๐—ฒ๐—ฑ๐—ถ๐—ป.๐—ฒ๐˜…๐—ฝ๐—ฎ๐—ป๐—ฑ๐—ณ๐—ฟ๐—ฎ๐—บ๐—ฒ๐˜„๐—ผ๐—ฟ๐—ธ.๐—ฐ๐—ผ๐—บ, ๐˜†๐—ผ๐˜‚๐˜๐˜‚๐—ฏ๐—ฒ.๐—ฒ๐˜…๐—ฝ๐—ฎ๐—ป๐—ฑ๐—ณ๐—ฟ๐—ฎ๐—บ๐—ฒ๐˜„๐—ผ๐—ฟ๐—ธ.๐—ฐ๐—ผ๐—บ and ๐˜๐˜„๐—ถ๐˜๐˜๐—ฒ๐—ฟ @๐—ฒ๐˜…๐—ฝ๐—ฎ๐—ป๐—ฑ๐—ณ๐—ฟ๐—ฎ๐—บ๐—ฒ๐˜„๐—ผ๐—ฟ๐—ธ and or simply ๐—ฆ๐˜๐—ฎ๐—ฟ/๐˜„๐—ฎ๐˜๐—ฐ๐—ต this repository and get notified from ๐—š๐—ถ๐˜๐—›๐˜‚๐—ฏ
Stars: โœญ 158 (-9.2%)
Mutual labels:  workflow
Gopablo
๐Ÿบ Static site generator.
Stars: โœญ 166 (-4.6%)
Mutual labels:  workflow
Travis Ci Latex Pdf
Travis CI and deployment service to build PDF from LaTeX document.
Stars: โœญ 170 (-2.3%)
Mutual labels:  workflow
Octodns
Tools for managing DNS across multiple providers
Stars: โœญ 2,090 (+1101.15%)
Mutual labels:  workflow
Fastmac
Get a MacOS or Linux shell, for free, in around 2 minutes
Stars: โœญ 1,953 (+1022.41%)
Mutual labels:  workflow
Alfy
Create Alfred workflows with ease
Stars: โœญ 2,232 (+1182.76%)
Mutual labels:  workflow
Yii2 Workflow
A simple workflow engine for Yii2
Stars: โœญ 157 (-9.77%)
Mutual labels:  workflow
Rnaseq Workflow
A repository for setting up a RNAseq workflow
Stars: โœญ 170 (-2.3%)
Mutual labels:  workflow
Git tracker
Some simple tricks that make working with Pivotal Tracker even better... and easier... um, besier!
Stars: โœญ 166 (-4.6%)
Mutual labels:  workflow
Community.activities
Repository of Windows Workflow Foundation Activities for UiPath Community
Stars: โœญ 170 (-2.3%)
Mutual labels:  workflow
Dnscontrol
Synchronize your DNS to multiple providers from a simple DSL
Stars: โœญ 2,089 (+1100.57%)
Mutual labels:  workflow
Welabx G6
welabx - antv G6
Stars: โœญ 163 (-6.32%)
Mutual labels:  workflow
Rebuild
Building your business-systems freely! ้ซ˜ๅบฆๅฏๅฎšๅˆถๅŒ–็š„ไผไธš็ฎก็†็ณป็ปŸ ไผไธšไธญๅฐ
Stars: โœญ 169 (-2.87%)
Mutual labels:  workflow
Sflive Paris2016 Workflow
Demo app for the new symfony/workflow component
Stars: โœญ 160 (-8.05%)
Mutual labels:  workflow
Baumeister
๐Ÿ‘ท The aim of this project is to help you to build your things. From Bootstrap themes over static websites to single page applications.
Stars: โœญ 171 (-1.72%)
Mutual labels:  workflow
Camunda Bpm Platform
Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Spring, Spring Boot, CDI.
Stars: โœญ 2,390 (+1273.56%)
Mutual labels:  workflow
Specification
Serverless Workflow Specification
Stars: โœญ 166 (-4.6%)
Mutual labels:  workflow
Viewflow
Reusable workflow library for Django
Stars: โœญ 2,136 (+1127.59%)
Mutual labels:  workflow
Workflow core
[Deprecated, use flor_core instead] A Rails engine which providing essential infrastructure of workflow. It's based on Workflow Nets.
Stars: โœญ 171 (-1.72%)
Mutual labels:  workflow
Git Commit Style Guide
Make git commit message more readable and useful.
Stars: โœญ 170 (-2.3%)
Mutual labels:  workflow

Workflow Guide

This is a work in progress and I will likely add (or replace) more functionality in the future.

Introduction

Hello there! I'm Vitor Britto, a Full Stack Developer extremely passionate about my work. I discovered the world of code almost two decades ago and kept the same passion from the first moment of this discovery. I have worked full time as a freelancer for nearly 4 years developing projects for the web, and I focus part of my time on researchs, collaborative projects, personal projects and writing some articles for my blog.

But, enough about me! I would like to present you this project.

What this is about?

  1. My workflow context with approaches and methods that I use.
  2. Tools that makes my Workflow easy.
  3. My own code conventions, which is inspired by what is popular within the community and flavored with some personal opinions.
  4. Major dependencies that I use.

Why was it created?

Reason #01

Apply rules and be based on a principle and methodology of process which could maintain the structure of my standards.

Reason #02

Not only have a code style guide, but relevant informations about my Workflow. Thus I always keep the same logic process and can initiate the development of my projects without any questions when making a scaffolding, building process, automation rotines, unit testing and others tasks.


Table of Contents


Workflow

You can find a complete list of applications, utilities, DevOps and Business Tools here: Stack Share

This is a simple table with approaches and methods that I use at my Workflow.

Strategy Blueprint Visual Develop Build Deploy
Research Sitemap Concepting Scaffolding Lint Test
Observe Wireframe Presentation Libraries Concatenate Optimize
Understand Prototype Refine Templates Minify LAUNCH
Analyze Style Guide Approval Frameworks Compile
Timeline Usability Database

โฌ† back to top

Strategy and Management

โฌ† back to top

Blueprint and Visual

โฌ† back to top

Development

Scaffolding

Check the Kickstarts organization where I organize and setup my stacks for every kind of project. It's a initial structure and configuration where I can start coding in a few minutes.

Coding

Front-End:

  • HTML5
  • CSS3
  • JavaScript

Back-End:

  • NodeJS
  • PHP

Database

  • MySQL
  • PostgreSQL
  • Redis
  • MongoDB

Editors

  • Visual Studio Code
  • MacVim

Build

Frameworks Libraries Template Engine Supersets Others
React Native React Pug Sass WordPress
Angular jQuery EJS PostCSS WooCommerce
Ionic Typescript Strapi
AdonisJS GraphQL
Gatsby AWS
NextJS Vercel
Express Netlify
Laravel
Lumen
Slim

... and much more!

โฌ† back to top


Guides

For web projects in which I work from planning to delivery, I use the guides below. If I am on a team that already has established guides, I'll follow the rules already adopted.already adopted. No bullshit, just follow the rules.

โฌ† back to top

General Notes

  • [STRATEGY]: Kanban or Scrum method.
  • [DEVELOPMENT]: use the SOLID principles.
  • [BUILD]: all javascript files must have two spaces (soft tab) and PHP files musta have four spaces (soft tab) FOR INDENTATION.

Be Consistent

The point of having style guidelines is to have a common vocabulary of coding so people can concentrate on what you're saying rather than on how you're saying it. We present global style rules here so people know the vocabulary, but local style is also important. If code you add to a file looks drastically different from the existing code around it, it throws readers out of their rhythm when they go to read it. Avoid this.

Google C++ Style Guide

โฌ† back to top

References

โฌ† back to top

License

MIT License ยฉ Vitor Britto

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].