Import Data from LinkedIn! ⚡️

One of the biggest pain points as I have heard from people (and faced myself) is the daunting task of filling your data for the portfolio website. This is especially true when all the data sits in your LinkedIn profile.

So announcing a feature allowing you to import your LinkedIn data to quickly populate your portfolio. Here's how to use it:

1. Export Your LinkedIn Data:

   • Follow LinkedIn's guide to download your account data
   • The export process may take up to 48 hours
   • Once ready, download and extract the ZIP file

2. Prepare the Data:

   • Move the extracted directory inside the snippets folder
   • Rename the directory to linkedin-export

3. Run the Import Script:

   python3 snippets/bulk_import_from_linkedin.py

   This will:

   • Read your LinkedIn data
   • Convert it to the portfolio format
   • Create/update src/constants/index-example.js

4. Finalize the Import:

   • Review the generated index-example.js file
   • Replace src/constants/index.js with the contents of index-example.js
   • Customize the imported data as needed

Important Notes:

• This is a beta feature and may require manual adjustments
• You'll need to manually add:
  • Icons for skills and frameworks
  • Project images
  • Company logos
  • Any additional customizations following instructions in Enter your data manually section of the README.
• Some fields may need manual adjustment to match your preferred presentation style

Security Update

Noticed a security flaw.

When using environment variables via Vite, these tokens are exposed in the bundle output that is created for a production build upon running npm run build. This is not good as the token is exposed and anyone can get access to this token by inspecting the website.

Since we don't have a backend to store the env variables, added a Netlify function to fetch the contributions using the GitHub GraphQL API. This keeps the GitHub token (and others in future), outside the build output.

If you are using Netlify to deploy the website, please update your deployment configuration and keep the checkbox for 'Contains secret values' as checked. This will ensure that 'secret values are only readable by code running on Netlify’s systems. With secrets, only the local development context values are readable and unmasked on Netlify’s UI, API, and CLI.'

This will also mean that local testing would change hereafter. Please refer to the Installation Guide in the readme for the updated instructions.