Final Milestone

Deliverables

You will create a digital product that can be hosted on your personal website or linked to from your personal website. Options include:

  • Blog post (single .qmd file)
  • Standalone Shiny app (e.g., dashboard style with an app.R file)
  • Blog post with Shiny features. This is like a blog post where you scroll through text and plots, but with this format, the plots can be interactive (mini Shiny apps). (In RStudio, when you choose File > New File > Quarto Document, you can choose the “Interactive” option to generate this format.)

Presentation

During the final exam slot (Thursday May 8, 8:00 - 10:00 am), each group will present their work in a poster session format. This will be a celebration of your work and a chance to share your findings with the class.

  • Format: “Poster session”
    • Each team will set up a digital display of their work for about 30 minutes and talk to people who come by. We’ll do 3 rounds of 30 minutes with 3-4 teams presenting per round.
    • Why this format? Because we have about 10 teams, it would feel too fast-paced to do sequential presentations. I hope that this format feels more low key and celebratory.
    • We’ll have snacks to celebrate!

Final submission

By the end of the day on Saturday, May 10th:

  • If your product has Shiny components (is a standalone Shiny app or hs a blog post with Shiny features), you have the following options:
    • Publish your app on shinyapps.io using the instructions here and share the link on the Readme.md of your Github repository.
    • Push all files needed for me to view your Shiny app on my computer to the Github Repo. This will include the app.R file and any associated data files.
  • If your product is a blog post (without Shiny components):
    • Push all files needed for me to view your post to your Github Repo and ensure that it is clear where that html file is on the Readme.md. Double check my downloading your Moodle upload that all images are contained in the post.

All groups should make sure that the final codebase is pushed to your team’s public GitHub repository. Make sure that your repository can be public facing with a clear ReadMe.md and organized in a way that is easy to navigate.