Skip to content

My portfolio website for displaying personal projects and public work. A statically generated site with incremental regeneration. At build time and during revalidation it makes a graphql query my github pulling down public repositories and displaying them on the projects page. Viewers may click through the cards to get more details or access lin…

Notifications You must be signed in to change notification settings

CarpentersKeys/portfolio

Repository files navigation

Logo

Portfolio

My site for displaying past, ongoing work, and a little personal background. It is intentional modest in terms of styling as I wanted to trying styling everything from scratch with SCSS. The site is statically rendered and incrementally regenerated, so it should provide a snappy experience, other than cold starts. Much of the content is pulled down my repos through Github's grapqhql api at build time.

View Demo · Report Bug

About The Project

Image

(back to top)

Built With

Check it out!

The site is hosted on Vercel so please go ahead and take a look around.

(back to top)

Current State

Home/About/Resume

All the content is hardcode on these pages, most of the work went into styling them to apear conistent and responsive across various viewports. There are three breakpoints on all pages placed strategically to accomodate most mobile devices, tablets and monitors.

Projects

Githubs grapql API makes it possible to query for details about ones repositories and other profile information. Using an Auth Token the site is able to proxy as the repository owner, the permissions for this instance are limited to public access as the use case is simplistic but theoretically much more powerful interface with Github functionality is possible. Image

Individual Projects

Clicking through the Projects page takes the user to a dynamically generated details page for the given project. The Nextjs framework is capable of running programatic datafetching at build time on the Vercel servers before populating and statically generating the list of paths based on the given data. That's what's done here. Image (back to top)

Future

Improvements could be made to the data fetching, as it stands multiple fetches are made during the population of the paths, and rendering of pages. This unfortunately reduces to value gained by making a graphql query rather than a REST. However, some data was not available through the REST API so graphql needed to be used as a matter of course. This isn't a significant problem as these calls only happen in the background when it's time for a new build, but build time could be optimized by sharing the data from one call across the different server processes.

Contact Joshua -

[email protected]

(back to top)

License Distributed under the MIT License.

About

My portfolio website for displaying personal projects and public work. A statically generated site with incremental regeneration. At build time and during revalidation it makes a graphql query my github pulling down public repositories and displaying them on the projects page. Viewers may click through the cards to get more details or access lin…

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages