Final Project

[github-learning-lab[bot]]

Submitting Final Project Proposals

Congratulations! You're on the final stretch, and we'll now begin working on our final projects!

Here are the proposal instructions.

Flowchart: Create a flowchart on draw.io that demonstrates how you will implement your solution. Your flowchart should show all APIs (including your Azure Function) that you will be using, and what data is being passed between each step.

For example:

Project Proposal: Create a pdf of your flowchart and a description of your project. Include the problem that you aim to solve and describe how your project provides a viable solution. Please include any questions that you currently have or anticipate to have about your project’s implementation.

To move on, commit the PDF of your project proposal to the repo, and comment a one sentence summary of what your project is about!

[a-padman]

ProjectProposal.pdf

Dine the Distance recommends restaurants between two friends locations.

[github-learning-lab[bot]]

Submitting an MVP

A minimum viable product (MVP) is a version of a product with just enough features to be usable. Releasing an MVP means that developers potentially avoid lengthy and (ultimately) unnecessary work.

Submit a working (loose definition) version of your MVP. Your project does not have to work smoothly or look presentable; it just needs to have a few main components (Azure Function included) that are interacting with each other.

To move on, commit your MVP to this repo, and comment a brief summary of the problems you ran into while building it!

[a-padman]

https://github.com/a-padman/Dine2

Here's a link to my public repo. Some problems I ran into involved passing the restaurant info back and forth between front and back end. Additionally, I needed to modify the file structure of my function app before deploying.

[github-learning-lab[bot]]

Submitting the Final Project

Once your MVP has been completed, it's time to finish the final project!

In addition to the project, write a blog tutorial that describes step-by-step how a beginner could go around recreating your project.

The outline of your blog tutorial should look like the following:

1. Abstract: A 200-250 word description of your project including why you made this project, what problem it solves, what your solution is, and what impact it has on the world.
2. Image of yourself working on the project (candid or posed, as high quality as possible)
3. Profile Picture (also as high quality as possible)
4. Tag line: An IMPACTFUL description of your project (with a maximum of one sentence)
5. Step-by-step blog
   • Beginning: why you made this project, what problem it solves
   • Middle: clear instructions on how to make this project from scratch, split code up into small parts and explain each part concisely but precisely
   • End: what impact does this project have, what would you like to do to improve it, how you feel about this project, etc.
   • Tip: use simple language and a lot of visuals, make it easy to read and follow

To write your blog tutorial, it might be a good idea to use a markdown editor like Typora.

To move on, commit your final project WITH a markdown file of your blog tutorial. Comment any changes you made to your final project in comparison to your project proposal!

[a-padman]

I'll be finishing up the slides first for the lightning talk and coming back to the blog post after!

[github-learning-lab[bot]]

The Lightning Talk

Your final step is to prepare a 15 minute talk and demo of your project. Describe your vision, your process, and any challenges that occured. Use slides to enhance your talk through images, gifs, and perhaps short code snippets - not paragraphs of text.

To complete this week, comment a link to your Google Slides presentation!

[a-padman]

https://docs.google.com/presentation/d/16-0h8HIwyZ4Xm9iawuk1jA1mKxCjKxyvHs6q3gUMHjc/edit?usp=sharing

[github-learning-lab[bot]]

Great job completing the course!