Vampazon - Sassa, Elle, Trish, and Maya (parens)

[mayawang]

Heroku live: https://vampazon.herokuapp.com/
Trello: https://trello.com/b/J4ogujNT/lumberjanes
ERD diagram: https://www.lucidchart.com/documents/edit/55c5fe2f-6916-4b42-9233-538039a9e2d9?shared=true&

Vampazon

Shop till you drop again, at Vampazon! We have a wide array of products to meet all your bloody needs. Minions, Home Decor, dental care, and more! Commence shopping at Vampazon here. Vampazon is an e-commerce venue for Vampires and beyond.

Authors

• Elle Vargas
• Maya Wang
• Sassa Kitka
• Trish Griego

Contribution

All authors are students at Ada Developers Academy

Versions

• Rails 4.2.6
• Ruby 2.3.1p112

Built with

• Foundation - The CSS framework
• OAuth - OmniAuth is a library that standardizes authentication for web applications. Project only connected to github authorization.
• Rails - is a server-side web application framework written in Ruby under the MIT License. Rails is a model–view–controller (MVC) framework, providing default structures for a database, a web service, and web pages
• factory_girl - Allows you to create templates for valid and re-usable objects. They were created in response to fixtures. Helpful for creating flexible, semantic tests. Project tester took lots of notes on implementation.

Best Practices/key take aways.

• to be continued.

Assignment Details

• Guidelines, Expectations, and learning goals can be found here.
• Also found within this repo here

[RedSquirrelious]

Team: What helped us stay organized and working together?

Our team was very warm and open with each other. We made an effort from the get-go to connect and do a daily morning checkin to see how everyone was doing and what folks might need.

Team: What should we have been doing differently?

We could have used the Trello board more.

Team: What would you recommend to C7? One piece of advice.

Stay connected! Your classmates have lives outside the classroom that can interfere with the project. (families, commutes, mortal bodies, etc.)

Technical: What went well?

We got our code to play together nicely. It took time, but we got it to!!

Technical: What was most challenging?

Version control. It’d be good to have had more time with Git and Git Commit Best Practices (tm).

Overall: How do you feel about your project overall?

I am glad I got to work with other folks on it. We didn’t quite end up where we wanted to be, but we certainly grew in all directions, not just technically. We got better at communicating what we were doing, which helped make merging smoother. It was cool to watch the team’s rhythm and workflow improve as we got to know each other better.

[Trishthedish]

Here is my relfection for project Vampazon: https://gist.github.com/Trishthedish/d7a319cbdc354f8ed97bdf2a39d71a23
@CheezItMan && @Hamled

[mayawang]

Reflection:

Group Dynamics:

We are a loving team!

How did you team work together:

• What helped you stay organized and working together?
  • We made team rules regarding github and posted it on first column in Trello board. It streamlined and kept a great practice on github merging, and also unified our other practice like routing naming etc. This sets up a good start and reduced potential cross end developer bugs and merge conflicts.
  • We set up "PEMS(Physically, Emotionally, Mentally and Spiritually) check-in" in standup meeting. So we are not only caring about each other's work process, but also caring about each other as friends. This helps us quickly build trust and care as a team, and really set up an open and warm foundation for future work.
  • We swapped standup leader and task leader roles a little more frequent than required. It increased ownership and empathy of each team member(which are already very high to begin with), and also helped us better support each other in varies conditions flexibly.
• What should you have been doing differently?
  • We probably should have started testing earlier so the test coverage will be better. The field to be test is increasing while we build more features.
• What would you recommend to C7? Once Piece of Advice.
  • Set up some group guidance for github merge upfront.
  • Keep detailed documentation on github.
  • Keep appreciate each other's contribution, help and existence.
  • Believe in your team no matter what. Count on each other. Communicate and be patient. This is a learning not only for technologies, but more importantly, for teamwork. :)

Technical:

• What went well?
  • We developed great technical collaboration habits. I was able to ship quality code/complete features steadily and consistently, and submit detailed PR descriptions for documentation, also streamlined the git merge practice rules for our team.
  • I tried my best within the time constrain and feel productive. I have built the following features:
    1. Product Feature as a guest(all mvc logic) :
       • 1. Show products by category, show all products, show products by seller;
       • 2. Product review: calculating average review, individual review and show bats on product show page.
    2. Cart/Order Features as a guest and a sign-in user(all mvc logic):
       • 1. Add product to cart; Delete an order item from cart;
       • 2. Change product quantities and adjust inventory, edge case handling and flash notices;
       • 3. Checkout, payment and confirmation.
    3. User Management - buyer management and seller management as a sign-in user (all mvc logic)
       • 1. Buyer manage panel. To show buyer user information and linked to order details, by all and by status. CANCEL an order.
       • 2. seller manage panel. To show seller created order-items, orders, by all and by status. SHIP and fulfill orders.
• What was most challenging?
  • The cart part is somewhat challenging at beginning, and it went well later. It helped me to understand much more on sessions controller.
  • The user management part is a little tricky as well. But after I refactored the user story, it becomes clearer.

How do you feel about your project overall?
Overall, I am really proud of our team and the project we accomplished together!

This time I worked on backend intensively and learnt a lot. I have more thorough understanding on ruby on rails, and dig deeper in backend architecture and UX design.

The project itself is only a mvp. There are a lot more features and corners need to be polished. I love our vibe and creativity.

Thank you Elle for the super witty and smart product contents and amazing frontend design, you put so much hearts in this project. Thank you Sassa for the absolute shining oAuth part, front end and products features, and for always being there(and being so considerate and supportive!) whenever team calls for...and the Vampire gears!! Thank you Trish for introducing the wonderful "PEMS" check-in(really important), testing, search bar, favicon and all the beautiful layers you added on the project and the team.

Thank you my team for all trust, support and love!