sparkbox / standard

How we work and best practices

Sparkbox Standard

How we manage products.

How we make things beautiful.

How we write code.

How we dance.

• Almanac Our list of browser bugs and quirks.
• Apprenticeship How we teach.
• Build Process How we build, deploy, and deliver.
• Career How career growth happens and descriptions of roles.
• Code Style The way we write documentation and code.
• Culture How we Sparkbox.
• Design How we do design.
• Development Process How we develop.
• Foundry How we write on the Foundry.
• Platforms How we host applications and content.
• Meetups Our MO for preparing and facilitating meetups.
• Office How we interact with traditional office supplies and services.
• Project Management How we manage our projects.
• Security How we keep safe.
• Services we Use Dropbox, Skype, etc.
• Software Vim, Sublime, etc.
• Laptop Maintenance How we re-image machines and set new ones up.

Inspired by Thoughtbot's Playbook

standard's Issues

Services: CodePen

Code Styles: Hub

Code Style: Code Reviews

Software: CMSs

• Craft
• Drupal
• Wordpress
• EE

Software: Command Line

• Zsh
• Bash

Services: Invision

Apprenticeships interview process

• How we interiew
• Once signed

Code Styles: JS

Basics outlines of code standards
Modules, Variables
Links to How we are Linting JS

Services: Rollbar

Redo all of PM section

So out of date

Code Styles: Password Requirements

Services: Browserstack

Services: ZenHub

Services: Snyk

Culture: General Updates

Meetups: Include food places for non-meat eaters

https://github.com/sparkbox/how_to/blob/master/meetups/README.md

Services: Heroku

1Password

Update the 1Password info from Dropbox -> Teams

Services: Creative Cloud + Typekit

Clarify `style` value for <type>

"no code change"...I'm wondering where this leaves css changes.
Do you consider that "code"?

feat: style admin layout
vs.
style: admin layout

Contents: Build Process + Almanac

Design

Code Styles: Pattern Libraries

Software: Atom

Services: Zoom

Services: Fonts

List of services we use and have used
Quick links
How-tos

Review by: @aspencer116

Drops process

https://docs.google.com/a/heysparkbox.com/document/d/1Om-EcXb8BsdNpxxWOIFeLaZUDorTVT-v4bqtPSfS78A/edit?usp=drive_web

Let's get this into the foundry under either Development or Planning.

Software: Sketch + Plugins

Meetup: Speaker prep instructions

• Quicktime recording trial run
• Post and send us slide deck/resources

Code Styles: Non-Code

Move to better sections

Services: Harves, Kin, Gusto

• Assigned to Josiah

Software: Squarespace

@zastrow to review

Code Styles: Sass & CSS

• BEM

Services: 1Password

Project Management: General Updates

Foundry: StyleGuide

@emilykggray to review

Proposal: Add `dep` as commit message `type` option

I find myself upgrading an npm or ruby dependency and feeling really weird about using feat. I feel like a unique dep type might help:

Examples:

dep: upgrade grunt to version 0.4.5

This version brings magical unicorn spit for slippery
fast concats on large directories like ./js.  This required 
an options update to the concat task: `useUnicornSaliva: true`.

dep: upgrade ActiveRecord to 2.1.666

We ran into a bug with outer joins via Arel tables
that is resolved in this incremental build.  

Services: Remove Divshot

Services: Slack

Style: Rename to Code Styles

Rename to Code Styles, move email formatting to onboarding section.

Software: Emacs

IA

How are we going to organize the new version? Just two levels?

## Topic 
### Section

Examples:

## Project Management
### Kickoffs
### Estimating
### Managing Work
### Gauging Progress
### Site Completeness

## Meetups
### Scheduling
### Food
### Day Off

## Security
### SSH & Servers
### Endpoint Security
### 2FA

Build & Deploy Process

The intent isn't to describe how we build and deploy per-se, because that can change depending on the project & client scenario. Instead, we talk about our principles of automation, collaboration, tight feedback loops, etc. We can describe common scenarios like Capistrano, Mina & mina-circle, Heroku Review Apps & Pipelines, etc.

Office / Operations: Apple ID for retired laptops

Going off of what @asimpson started for #48 should we not have an office "generic" Apple ID that is used on all of our retired/loaner laptops? We could easily setup the laptop with this ID and register the mac with find my ____ etc. We could have different IDs for Apprentices vs general use laptops.

Software: Remove Pow & Capistrano

Bootstrapping new team members

• Public Keys
• Services: Dropbox, Harvest, etc.
• 1Password

Services: Mailchimp

Code Styles: Git

Rebasing vs. Merging
Emoji / Sparkbox commit guide
Gifs

Services: Alfred

Meetup: How to create the eventbrite event for RSVP