Skip to main content
Version: v1.4

✏️ 3.5.5.1 React with APIs Independent Project

Independent Projects Overview​

Before you begin your project, make sure to take a moment to review the Independent Projects and Code Reviews lesson.

React with APIs Project Objectives​

Revisiting Your Portfolio​

Unlike previous independent projects, this one isn't about the technical content you just learned in this section - it's about keeping your portfolio and professional profiles current.

There is plenty more out there, but you have taken a significant leap in your understanding of popular front-end languages, tools, and libraries.

For this last code review in the React course, you'll spend time updating your personal portfolio and online profiles.

Update Your Personal Portfolio Website​

Earlier in the program, you created a personal portfolio website. You should update it! Optionally, you can recreate this website using modern JavaScript and React. It is completely acceptable as well to have a website that simply uses HTML and CSS, or another setup of your choosing.

Why are we doing this now? Well, you should consider your coding portfolio and profiles as living documents. This means they need to be updated regularly in order to be viable. What better time to update your most important job-search tools than now?

Additionally, you are encouraged to feel confident in applying to front-end roles in the field with JavaScript and React under your belt. Use this portfolio project as an opportunity to create a real-world application that will be seen by employers.

Create a new website using JavaScript and React, update your existing website using HTML and CSS, or use another setup entirely - the choice is yours. Updating your existing site is generally the faster option, especially if front-end isn't your main focus. Rebuilding it in React gives you more practice with the tools from this course and a project that specifically demonstrates your React skills. Whatever you choose, pick whichever serves you best.

Your code will be reviewed for the following objectives:

  • The project demonstrates a best effort at creating or updating a portfolio project
  • The README contains accurate information for the project in the state it's submitted in
  • Project is in a polished, portfolio-quality state.
  • The prompt's required functionality and baseline project requirements are met.

You are not required to have a finished application, since this will be a real-world living document that you will hopefully continue to update as you continue your coding journey.

What is a polished, portfolio-quality state?​

When a project is both polished and in a portfolio-quality state, this means:

  • You've reviewed your project and your README prior to submitting it to make sure there are no errors or missing information and you are consistent in your indentation, spacing, and code structure.
  • You are following the best practices and coding conventions we teach.

What are the baseline project requirements?​

All independent coding projects at Fidgetech have these baseline requirements:

  • A complete and informative README
  • The project's commit history demonstrates steady, incremental progress rather than a single large commit
  • Completion of the project based on the prompt and objectives. The prompt contains details on the project's theme and features that are not always detailed in the objective. Carefully read through the prompt before submitting to make sure that you are not missing anything.

Further Exploration​

Update Your GitHub Profile​

GitHub allows you to store and manage code but more importantly it is your most meaningful coding portfolio. When you apply to jobs, employers will expect to see a link to your GitHub profile on your resume. If you include a project on a resume or on your LinkedIn profile, employers will want to see the source code on your GitHub account. GitHub tracks your activity via commits. The more commits you have, the more likely employers will see you as a practiced programmer.

Below is a checklist of actions you can do to make sure your GitHub Portfolio is good. The items start from most simple to more complex:

  1. Add an image to your profile.
  2. Add contact and LinkedIn information to your bio.
  3. Pin your best/favorite repositories.
    • These should be repositories you are going to be most excited to talk about when asked. Another consideration is to pick repositories that demonstrate you using the tools and technologies you have learned so far.
  4. Turn on private contributions.
  5. Add a README to your GitHub profile to tell other people about yourself.
    • Read Managing your Profile README from GitHub Docs.
    • Some advice on what to include:
      • Keep it simple: GitHub supports images, gifs, emojis, and even fancy scripts. Remember though the goal of your profile README is to communicate your projects and skills as concisely as possible. Don't overwhelm your profile README with too many visuals.
      • Add an image of yourself or a decorative banner: This simply gives your profile README some personalization.
      • Include a short introduction about yourself
      • List your skills:
      • List your contact info: What's the best way for someone to contact you?
      • Include links to other profiles: We recommend you include a link to your LinkedIn and your personal website.
        • Optionally include links to social media sites if you are using those accounts to further build out your portfolio. For example:
          • DO include your Instagram if you mainly share pictures about coding events such as hackathons.
          • DO include your X (Twitter) account if you primarily talk about topics as they relate to coding and the tech field.
          • We recommend NOT including social media accounts that are primarily about your personal life, hobbies, special interests, and hot takes. This is just a recommendation because the subject is tricky. On the one hand, including a social media account that documents your hobbies can be a great way to help people get to know you. On the other hand, you don't want to forget that this account is now associated with your career portfolio and have employers see something you wish they didn't. There is no right answer to this. It really just depends on your comfort level and how you want to personalize yourself in your resume. One thing you could do is include a hobbies section in your profile README and then link social media sites from there.
      • Other resources
  6. Make sure each repository has a README or set the visibility to private.
    • Every repository should have a README to provide the repository with context. They can be simple READMEs that just include your name and one to two sentences for what the repository is about. This is especially useful for practice repositories.
    • Set a repository's visibility to private if there is no README and you don't remember enough about the project to write a README. Generally, for junior developers, it is best to keep repositories public if you can. Employers and other developers may be interested in seeing your coding journey. Setting a repository's visibility to private instead of deleting it will preserve your commit history on your GitHub profile.

Update your LinkedIn profile​

Revisit the LinkedIn Profiles lesson from earlier in the program. Since you've already made a LinkedIn profile, simply update what is needed. Be sure to especially update the "Skills" section! It's a good idea to read through your own LinkedIn profile every so often to look for updates. Giving yourself time in between visiting your own profile will allow you to examine it with some new perspective.

Take this time to explore more of LinkedIn, too! You should be exploring LinkedIn regularly, especially the job board section.

Submission​

Submit your code for review to the React with APIs code review on Fidgetech Code Central.

Visit Independent Projects and Code Reviews for details on how to submit, how feedback works and course completion requirements.