Creative Projects - Technical Discoveries

tl;dr; Research and report on gems, code snippets or technical approaches that you might use

Creative Projects: Discoveries

Explore the technical needs of the project and open solutions that you can leverage in your web app to quickly build out the functionality you intended. Simply put, find and report resources that will help you make better web applications as part of this course.

Instructions

Building on your workflow diagram, functionality priorities and data map, work out the tricky parts of your application and begin to find open solutions for them

  • If you know you want to work with a third party service, is there a gem that will let you do that or is there a tutorial or code sample out there already that will give you a boost in getting there?

  • Is there an open source application you could borrow from or abstract to build out what you wanna do faster?

  • Is there code snippets, samples or solutions that you can borrow?

Search the web and find five things you can immediately use in your final project.

Add a link to the source and describe why you think its relevant, what it will help you achieve and how it’s been used by others. Priotize one of these and begin a technical investigation/experimentation of it.

Starting points

To help guide your explorations, a list of potential places is below:

Submitting your work

Append this update to your project documentation. Either edit the ‘README.md’ in your Student Folder or create a new file called ‘FinalProject.md’ use this to add all documentation to.

These files are written in Markdown pages (see this cheatsheet too)

You can edit this in one of the following ways:

  • You can edit it raw within your text editor of choice
  • GitHub provides an online inline editor - visit the repo, open the file, and click the edit icon in the toolbar (right hand side).
  • You can use an online tool like Dillinger or StackEdit to develop your document, and then copy and paste to your repo.