Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/teplostanski/nextjs14-gh-pages-markdown-static-blog-starter-kit
Starter kit for Next.js 14 with Static Site Generation (SSG) from markdown files, configured for deployment on GitHub Pages.
https://github.com/teplostanski/nextjs14-gh-pages-markdown-static-blog-starter-kit
blog deployment generation gh-pages github github-pages headless-cms markdown md next nextjs nextjs14 ssg ssg-nextjs starter starter-kit starter-template static static-site-generation template
Last synced: about 1 month ago
JSON representation
Starter kit for Next.js 14 with Static Site Generation (SSG) from markdown files, configured for deployment on GitHub Pages.
- Host: GitHub
- URL: https://github.com/teplostanski/nextjs14-gh-pages-markdown-static-blog-starter-kit
- Owner: teplostanski
- Created: 2024-05-15T22:24:58.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2024-05-25T23:57:03.000Z (7 months ago)
- Last Synced: 2024-10-15T02:25:49.469Z (3 months ago)
- Topics: blog, deployment, generation, gh-pages, github, github-pages, headless-cms, markdown, md, next, nextjs, nextjs14, ssg, ssg-nextjs, starter, starter-kit, starter-template, static, static-site-generation, template
- Language: TypeScript
- Homepage: https://blog.teplostanski.dev/
- Size: 2.53 MB
- Stars: 6
- Watchers: 3
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Starter kit for `Next.js 14` with Static Site Generation (`SSG`) from `markdown` files, configured for deployment on `GitHub Pages`.
This setup functions as a `headless CMS based on Git`, providing a seamless workflow for content management.
Without tailwind
Without MDX
A potential error in the browser console is nothing to worry about:
```
XHR GET https://YOUR_USERNAME.github.io/YOUR_REPONAME.txt?_rsc=8lxu9 [HTTP/2 404 247ms]
```This occurs due to a peculiarity with GitHub Pages (if you are not using a CNAME). The repository is configured to accommodate both the specific requirements of GitHub Pages, where the URL must include `/YOUR_REPONAME` after the domain, and the use of a custom domain where `/YOUR_REPONAME` is not required.