https://github.com/ryojerryyu/blog-next

My blog, build on Next.js static export feature, fully automated deployment, hosted on AWS S3 and Cloudfront.
https://github.com/ryojerryyu/blog-next

blog nextjs

Last synced: about 2 months ago
JSON representation

My blog, build on Next.js static export feature, fully automated deployment, hosted on AWS S3 and Cloudfront.

• Host: GitHub
• URL: https://github.com/ryojerryyu/blog-next
• Owner: RyoJerryYu
• License: mit
• Created: 2023-01-27T16:44:46.000Z (almost 2 years ago)
• Default Branch: master
• Last Pushed: 2024-04-14T15:44:09.000Z (9 months ago)
• Last Synced: 2024-04-14T16:25:21.509Z (9 months ago)
• Topics: blog, nextjs
• Language: TypeScript
• Homepage: https://blog.ryo-okami.xyz
• Size: 54.2 MB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 31
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Ryo's Blog

Here is the source code of my blog.

- [Release Version](https://blog.ryo-okami.xyz/)

- [Preview Version](https://test.ryo-okami.xyz/)

- [GitHub Pages Version](https://ryojerryyu.github.io/blog-next/)

# Features

## Fully Statics! 

It can be deployed to GitHub Pages! 

It build on Next.js Framework, and using it's Static Export feature. Thanks to this, the website is very fast and SEO friendly.

## Support MDX! 

Besides, it support GFM, KaTeX, Mermaid, and some self-defined feature. 

This feature is based on [remark](https://github.com/remarkjs/remark) and [rehype](https://github.com/rehypejs/rehype) ecosystems ([unified](https://github.com/unifiedjs/unified) plugins). You can find the plugin I have built in `src/plugins`. (Sorry but I do not intent to publish them to npm.) 

## Fully Automated Deployment!

There is a set of GitHub Actions defined in `.github/workflows`, which will automatically build and deploy the blog to GitHub Pages and AWS S3. I could preview it by opening a PR, and deploy it by merging into `master` branch.

## Non-trailing slash url style, on AWS S3 + CloudFront!

Yes, it's worth mentioning. You should have noticed that it's a bad idea to use non-trailing slash url style on S3, because it will not return `some/page.html` when you visit `some/page`. But it could be done by using lambda@edge.

If you are interested in this, you can find the code in another repo: [RyoJerryYu/aws-blog-infra](https://github.com/RyoJerryYu/aws-blog-infra). I use [Pulumi](https://www.pulumi.com/) to define the infrastructure as code. And of cause, the infrastructure deployment is also fully automated by GitHub Actions. 

(Pulumi is a great tool!)