Dun.Gen()

Overview: Dun.Gen() is a procedurally generated fantasy story application. The existing generator applications using the D&D 5e API don't provide the user with a story to begin their quest. Dun.Gen() not only generates the elements required to start a quest, but most importanly provides the user with a quest in a story based format to begin their adventure.

Authors: Robb Alexander, Chuck Altopiedi, Joshua McCluskey

Version: 1.0.0

Getting Started

Requirements

Change Log

GitHub Insights

Trello

Cooperation Plan

Team Strengths and Growth Targets

• Robb Alexander:
  • Strengths: Writing, communication, proofreading, loop logic,
  • Growth: Results Proficiency, Craft (Managing component inheritance)
• Chuck Altopiedi:
  • Strengths: Listening, inclusion, API call logic & grooming,
  • Growth: Tools, Technical Proficiencies
• Josh McCluskey:
  • Strengths: Growth Mindset, Business acumen, React
  • Growth: Communication, ...React
• Whole Team: Regex!,

Day-to-Day Plan

• (Remo) Hours: 9:00AM – 6:00PM PST (1 hour lunch, variable time)
  • No coding after hours (barring contingency discussions)
• Breaks: At-will, averaging 10 minutes per hour worked
• Merge Parties: Before lunch & End-of-day (or extenuating circumstances)

Project Management

• Trello board
• Communication methods:
  • Remo (during work hours)
  • Slack (availability but not expectation after-hours)
• Work division: All members will identify 1+ growth area(s) and 1+ strength area(s) to improve upon or show off with, respectively, and be responsible for those features.

Git Flow

• Don’t merge your own PR’s (required reviews in GitHub settings)
• Separate tasks by front/back and by file when possible to limit conflicts
• Branches:
  • Naming convention: {dev first initial}-{day of week 1st 2 letters}-{feature}-{#}
• Merge Parties: Before lunch & End-of-day (or extenuating circumstances)

Catch-up Contingencies (OSP’s)

• All members willing to accept longer work days as necessary if MVP is behind schedule

Conflict Plan

• Vote on timeline/feature divergence from plan
• Hearing differing opinions is required-- point out if a comment has been missed or forgotten
• Emergency plan: contact Ryan for any irreconcilable differences
• Project Mission Statement: This project is first and foremost a learning experience – team member growth is the priority over end results.

Domain Modeling and Database Schema Diagram

Wireframe

Credit and Collaborations

• Ryan Gallaway for providing the amazing knowledge, help and troubleshooting

Photos by: engin akyurt on Unsplash Larisa Koshkina Darkmoon_Art Tree vector created by jcomp - www.freepik.com Irina-Metsu

• API used: D&D 5e API

Feature Log

Name of feature: Auth0

Estimate of time needed to complete: 4 hours

Start time: 9:00 PST

Finish time: 4:00 PST

Actual time needed to complete: 8 Hours

Name of feature: Server

Estimate of time needed to complete: 3 Hours

Start time: 9:00 PST

Finish time: 12:00 PST

Actual time needed to complete: 3 Hours

Name of feature: MongoDB

Estimate of time needed to complete: 1 hour

Start time: 9:00 PST

Finish time: 1:00 PST

Actual time needed to complete: 4 Hours

Name of feature: Heroku Deployment

Estimate of time needed to complete: 30 min

Start time: 2:00 PST

Finish time: 2:20 PST

Actual time needed to complete: 20 min

Name of feature: Netlify Deployment

Estimate of time needed to complete: 1 hour

Start time: 3:00 PST

Finish time: 3:30 PST

Actual time needed to complete: 0.5 hours

Name of feature: About Us

Estimate of time needed to complete: 30 min

Start time: 3:30 PST

Finish time: 4:30 PST

Actual time needed to complete: 1 Hour

Name of feature: API Call Functions and State and Props Passing

Estimate of time needed to complete: 6 Hours

Start time: 9:00 PST

Finish time: 6:00 PST

Actual time needed to complete: 8 Hours

Name of feature: Data to Text

Estimate of time needed to complete: 5 Hours

Start time: 9:00 PST

Finish time: 4:00 PST

Actual time needed to complete: 7 Hours

Name of feature: Boostrap

Estimate of time needed to complete: 8 Hours

Start time: 9:00 PST

Finish time: 6:00 PST

Actual time needed to complete: 10 Hours

Name of feature: Style

Estimate of time needed to complete: 5 Hours

Start time: 10:00 PST

Finish time: 6:00 PST

Actual time needed to complete: 7 Hours

Name of feature: Story

Estimate of time needed to complete: 1.5 Hours

Start time: 10:00 PST

Finish time: 11:00 PST

Actual time needed to complete: 2 Hours