Skip to content

HausBrewer -- Jon Rutishauser #362

@jrutishauser

Description

@jrutishauser

Phase 1

  • Begin Planning, define precise MVP
  • Define necessary tech at bottom
  • set timeline for project with checkpoints
  • choose the appropriate generator
  • shave that yak! get those dependencies!
    • git flow
  • get comfortable with karma and jasmine test to start driving tests during development

MVP (so far)

  • create basic website layout
  • mobile first!
  • capability for a recipe to be input
  • ability to take that recipe and create a step by step brew process
    • initially no major measurements, step by step generated will be generic
  • capability for a user to login and see their recipes they have input
  • 2 storage zones, recipes and brewed batches of beer, maybe 3
  • notes blank

Stretch goal 1

  • fermentation schedule can be added to google calendar or iphone calendar(maybe both)
  • input from brewers everywhere for what to add!

Stretch goal 2

  • start getting more detailed with information that can be input
    • gravity readings
    • temperature readings
    • start calculating brewhouse efficiency
  • input from brewers everywhere for what to add!

Stretch goal 3

  • temperature of water needed can be derived from average room temperature and target grain steep temperature
  • more ridiculous measurements like this
  • input from brewers everywhere for what to add!

Stretch goal 4

  • input from brewers everywhere for what to add!

Necessary Tech

  • HTML/CSS
  • SCSS
  • Javascript
  • Angular.js
  • Firebase / Angularfire
  • dependency tools, Npm / Bower / Wiredep
  • things that make our life easier, Gulp / Browser-sync / Yeoman generator / git flow
  • Karma and Jasmine for testing
  • Chrome Developer Tools

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions