An accessible and fast portfolio starter for Gatsby integrated with Contentful CMS.
The target audience are Developers ๐ป and Tech Writers โ๏ธ.
In case you are looking for a quick setup portfolio or upgrade your current, you have to definitely try Mate!
This starter is totally content based on Contentful, which is a headless CMS where you can write the content for your page. In summary, Contentful is the Model when Gatsby with React is the View.
At the same time, as this portfolio is written with Gatsby is extremely easy to add more than one source of data! For example, the demo comes with an integration of Medium posts based on a user name โ๏ธ
- Gatsby
- Rebass: styled component system
- React Awesome Reveal
- Typescript
- CMS Integration with Contentful
- PWA ready
- SEO
- Responsive design
- Icons from font-awesome
- Netlify Deployment Friendly
- Medium integration
- Social sharing (Twitter, Facebook, Google, LinkedIn)
- Developer tools:
eslint
prettier
- Google Analytics integration
- End to End with Cypress:
As this process needs more steps compared to other starters, I decided to made a tutorial video of how to set up your own instance of Mate. You can follow the video or jump directly to the written documentation.
If you never used Gatsby before, I highly recommend you to Set up your development environment!
To copy and install this starter run this command:
$ gatsby new mate-portfolio https://github.com/EmaSuriano/gatsby-starter-mate
At this point you have the repository download with all the dependencies installed, but if you try to start by running yarn develop
you are going to received this message in the console:
TypeError: Expected parameter accessToken
This is because you didn't specify from which Contentful
space the portfolio will take the information. So the next step is create an empty space in Contentful!
After the space is created, run the following command:
yarn setup
This CLI will request 3 values:
Space ID
Content Delivery API - access token
Personal Access Token
These 3 values are inside the Settings section --> API keys.
After you provide them the CLI will automatically starts copying all the Content models
and Contents
from mate-demo-contentful
to your space โจ
If everything went smooth you should see something like this in your terminal:
Writing config file...
Config file /Users/my-user/Git/test/mate-portfolio/.env written
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ The following entities are going to be imported: โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโค
โ Content Types โ 3 โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโค
โ Editor Interfaces โ 3 โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโค
โ Entries โ 8 โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโค
โ Assets โ 6 โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโค
โ Locales โ 1 โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโค
โ Webhooks โ 0 โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโ
โ Validating content-file
โ Initialize client (1s)
โ Checking if destination space already has any content and retrieving it (2s)
โ Apply transformations to source data (1s)
โ Push content to destination space
โ Connecting to space (1s)
โ Importing Locales (1s)
โ Importing Content Types (4s)
โ Publishing Content Types (3s)
โ Importing Editor Interfaces (3s)
โ Importing Assets (7s)
โ Publishing Assets (3s)
โ Archiving Assets (1s)
โ Importing Content Entries (1s)
โ Publishing Content Entries (5s)
โ Archiving Entries (1s)
โ Creating Web Hooks (0s)
Finished importing all data
After this step we can finally run the project and see the result in http://localhost:8000/ ๐
$ yarn start
As the starter is a SPA it only has two routes:
/
: main page with the sections ofHome
,About me
,Projects
andWriting
./404
: error page for unexpected route.
Section | Screenshot |
---|---|
Home | ![]() |
About me | ![]() |
Projects | ![]() |
Writing | ![]() |
404 | ![]() |
This starters come with a hand-made color palette made by myself, but I highly encourage you to go and customize the colors to match your preference! The colors can be found inside theme.ts
, which are going to be loaded by ThemeProvider
of styled-components
and apply across all the components inside the application.
// colors.js
module.exports = {
background: '#FFFFFF',
backgroundDark: '#f0e6f6',
text: '#333333',
primary: '#7c37ad',
primaryLight: '#ae66df',
primaryDark: '#4b007d',
secondary: '#ff4081',
secondaryLight: '#ff79b0',
secondaryDark: '#c60055',
};
Some examples I made by using palettes from Color Hunt:
As we are dealing with environment variables, the .env
file is excluded from .gitignore
file. Therefore, in order to deploy the website you have to send SPACE_ID
and ACCESS_TOKEN
with the build
command.
SPACE_ID=xxxxx ACCESS_TOKEN=yyyyy yarn build
The result will be stored inside the public
folder, so you can upload to your web host. I highly suggest using this starter with Netlify when you can define which command will build the project and also send the environment variables inside the website configuration.
All the text of this starter live inside Contentful, specifically inside the Content of About
. In order to change it, just go to Content
section and change the entity of About with the information you want.
Regarding the projects and social links the process is the same! Contentful is really easy to learn so don't be afraid of breaking everything, remember that you can restore to the start point by running yarn setup
๐
The starter comes with a built in End to End Setup using Cypress. As there are no complex logic flow, there are only two tests in place:
- Accessibility check: using the cypress-axe plugin you can easily check a lot of a11y rules at once powered by Axe!
- Visual testing: using percy-cypress plugin you can take screenshot with different resolutions and easily the difference inside their platform. Here you can check the Percy dashboard for this project.
By default, the visual testing will fail due to Percy needs a Token in order to know with which project of your account is related. The steps to set up your own visual testing workflow is:
- Create a project in Percy.
- Go to "Project settings" -> "Project token" and copy the whole line saying "PERCY_TOKEN=<YOUR_TOKEN>".
- Open the
.env
file located in the root of the project and add the token to your credentials. - Try running
yarn e2e:ci
and you should be able to see a new build inside your Project Dashboard in Percy.
Mate starter is a SPA (Single Page Application), so basically you have only two pages:
Main.js
: portfolio itself404.js
: 404 error page with the same style
The structure for the main page is the following:
<Layout>
<Landing />
<About />
<Projects />
<Writing />
</Layout>
Layout
is the core of the application, it manages the theme for the application, the navigation between sections, also it defines the header
.
All the components inside Layout
are Section
components. A section can have a link inside the Header
or not, in order to add you need to wrapped the exported Section
with withNavigation
HOC and it will be automatically registered (Context magic โจ).
This starter has the analytics plugin inside the gatsby-config
, so the only need to do in order to enable it is to provide the Tracking Id
for your site (starts with UA-
). Just set a new variable inside your .env
file called ANALYTICS_ID
and analytics will be turn on automatically ๐
In case you cloned this repository before and you want all the latest changes of it, you can execute the following command to update the code in your repository with the one in this repository:
# Add repository remote entry
$ git remote add mate https://github.com/EmaSuriano/gatsby-starter-mate
# Get changes from master branch of gatsby-starter-mate
$ git pull mate master --allow-unrelated-histories
# Reset changes in unnecessary folder/files
$ git reset media/ bin/ README.md manifest-config.js
# Remove files affected by the reset
$ git checkout .
# In this step you might need to fix a lot of conflicts, you can do fix manually or use just accept all the changes from mate
$ git checkout --theirs .
# WATCH OUT that some configuration can be overwritten in this last step, like package.json, colors, etc. I highly recommend to do an overall look up at the end of fixing the conflicts.
# Install in case there is any new dependency added to the starter
$ yarn
# Build the project to see if everything is working as expected
$ yarn build
I came with the idea of creating the starter after the positive feedback I received when I deployed my website. Therefore this starter is not perfect! I tried my best to remove all the personal information, also improve the code to make it easier to understand.
I'm totally open for pull requests with bug fixes, changes in Documentation, or new features to the starter ๐
Please check the Contribution guidelines before opening yours ๐
MIT.