Move from Jekyll to Next.js

hawkins / is

A blog system built on Next.js catering to `.is` TLDs

https://www.hawkins.is

0 stars 0 forks source link

Move from Jekyll to Next.js #2

Closed hawkins closed 7 years ago

hawkins commented 7 years ago

Really just testing the waters right now. I'd love to get away from Jekyll and move to something more sophisticated like server side rendering and writing posts in React for more versatility, but I'm going to hit quite a number of adoption issues at first.

The first commit lays the groundwork for how this new structure will look and work, but much work is left to be completed.

Additionally, I've removed the shawk folder because I deployed that to now.sh at shawk.now.sh.

[x] Set up Next.js routes for basic pages
[x] Style the website more uniquely
[ ] Add mobile-friendly web styles
[x] Add all old posts
[x] Add all projects
- [x] All old projects
- [x] Add newer projects
[ ] Maybe blog about moving from Jekyll/GitHub Pages to Next.js/Now.sh?

hawkins commented 7 years ago

I'm really not crazy about all the code and ReactMarkdown tags. I want a better way to deal with code (particularly for syntax highlighting) but I'm not sure what else exists yet. It's likely I'll want to involve better third-party components for these.

hawkins commented 7 years ago

Moved to react-highlight to make this a bit easier. Still not perfect, but its a decent start

hawkins commented 7 years ago

Reviving this effort... new things I'd like to do:

[x] Add a backend with GraphQL and interacting via Apollo Client
[ ] Organize posts in /_posts instead and export as JS modules
[ ] Improve article writing by creating a set of components for reusability in writing
[ ] Add link to download latest version of my resume by compiling from source at hawkins/resume

hawkins commented 7 years ago

Need to rename Twitch Flow to Streamflow and correct link to project (https://github.com/hawkins/streamflow)

hawkins commented 7 years ago

Consider writing posts in markdown again, but better explore the possibilities of using react. Embedded content and more interesting content is a possibility with using posts in JS. Regardless, processmd is the key I've been missing for better markdown posts, and there's a decent example of it here: https://github.com/tscanlin/next-blog/blob/master/package.json