Cupcake Template

This is Cupcake🧁, a mirror of my personal website. It contains all the features of that website, including the blog! Cupcake is best served as a portfolio or online resume. This project will be actively maintained to be a better codebase, and implement new features. It is also open to any kind of contribution - features, bug fixes, improvements or documentation. Some features of the website:

• Randomization on-visit for colour theme 🌈 (with setup to dynamically generate css files)
• Randomization of quotes and images
• CSS striped background
• Trapezoidal top bar with typing-info
• Dynamic portfolio/resume section with content read from JSON file.
  • Includes a slider to filter content, and animations to show content enter/exits Scroll down to see incoming features!

I'd love to see anything people do with this template so drop an email at [email protected] any time. I'm also available for technical support.

Getting started

Run the following to set up the project and install dependencies. (You can also use the "Use this template" button at the top instead of cloning)

# follow instructions at https://www.getzola.org/documentation/getting-started/installation/
git clone https://github.com/kipply/cupcake-template.git && cd cupcake-template
npm install -g node-sass-chokidar 
npm install -g react-run-all 
npm install -g react-scripts 
npm install

Then to start serving the website;

npm start

This will auto-refresh and build CSS on all changes!

To find all the points in the website where data should be replaced with something specific to you, search the project for 🧁. Sometimes the 🧁 is accompanied by {{}} and some kind of description.

Deployment

The general deployment process usually involves running npm run build and placing that into a static site generator. To see all the options, check out Create React App's Guide. I listed some options with pros and cons below, I personally use Firebase.

Firebase Hosting

Pros: Deploy logs, UI for rollback, not tied to github commits

Cons: May cost some money (it's like 20 cents a month for me for like 1000 visits including some image-heavy pages)

Github Pages

Pros: Free forever

Cons: Tied to your github commits/pushes

Customizations

Blog

There is a blog folder that is more or less a distinct website. It is built statically with zola which you should have installed. npm run build will simply run the standard build for the React website, then statically build the blog into the public/ folder. Note that there are a lot of links in the source that have to be replaced! Do a big search for 🧁 to find points where your information is required.

Adding Routes

The template ships by default with / pointing to index.html and that is also be configured and reflected in Firebase. If additional pages are desired there are a few options.

1. For all deployment paths. Using React Routes, which should be intuitive and easy and work well with the project structure.

2. For Firebase Deploy. Using additional files in public/. This is better for any raw HTML files or PDFs. If you added Resume.pdf to public/, then yourwebsite.com/Resume.pdf will work. If you want /resume to be a valid path, add the following to the firebase.json under "rewrites".

{
    "source": "/resume",
    "destination": "/Resume.pdf"
},

3. For other static hosting. Adding additional files in public/ will generally work.

Analytics

An analytics service such as Google Analytics will give you a script that should be added to public/index.html in the footer element.

Favicon

The favicon is the little icon that'll appear in the browser tab. It is defaulted to a sparkly heart, though can be changed by replacing public/favicon.ico.

Upcoming features

1. Remove dependency on Bootstrap. This was a sad mistake made by fourteen year-old Carol that has lasted many years

2. Proper 404 pages

3. Add linting rules that work well for this project

4. Use a different object notation format for the portfolio data that's less vertically-intensive. Probably YAMLs, which I actually don't hate.