基于 Jekyll 静态站点框架,使用 Chirpy 主题
Notebook — Jekyll 博客模板
作者 Grow-with-Open-Source
基于 Jekyll 与 Chirpy 主题的开源写作博客模板,面向技术内容贡献与文档发布。
看看你的网站会是什么样
浏览真实页面截图,比较内容排版与手机效果。点击下方缩略图切换,放大查看整页细节。
全部页面与视图 3
截图用于了解视觉与布局,交互效果请以实际项目为准。
值得关注的模板亮点
从已有项目资料中,快速了解它的特点。
支持 Markdown 写作,文章存放于 _posts 目录
通过 Front Matter 配置标题、日期、分类、标签与作者
提供 authors.yml 管理多作者信息
内置 RSS 订阅与 GitHub Pages 部署支持
附带完整的贡献指南文档
模板详细介绍
Notebook 是 Grow-with-Open-Source 组织维护的开源项目,定位为面向初学者的技术写作与贡献平台。它使用 Jekyll 静态站点框架构建,并采用 Chirpy 主题呈现博客式界面,支持 Markdown 撰写文章、分类与标签组织内容、作者信息配置以及 RSS 订阅。仓库提供完整的贡献流程文档,包括环境搭建、分支创建、文章 Front Matter 格式、图片资源目录约定和 Pull Request 提交步骤。模板适合用作个人或社区的技术博客、文档站点,也可作为学习开源协作流程的启动器。需要注意,项目资料未说明生产环境部署、性能或长期维护状态,使用前应自行核对依赖与第三方素材许可。
适合你的项目吗?
适用场景
- 个人技术博客搭建
- 社区开源写作平台
- 技术文档与教程发布
- 学习 Jekyll 与开源协作流程
适合人群
- 希望用 Markdown 写技术博客的开发者
- 需要多作者协作的内容项目
- 想练习开源贡献流程的初学者
上手与定制指南
结合仓库当前版本的说明,按下面的资料检查内容、配置与运行要求。
- 1
需安装 Ruby 与 Bundler 环境
- 2
克隆仓库后执行 bundle 安装依赖
- 3
使用 bundler exec jekyll s 本地启动,默认访问 localhost:4000/Notebook
- 4
文章需按 YYYY-MM-DD-名称.md 格式放入 _posts 目录
- 5
图片建议使用 CDN 链接或放入 assets/img 对应目录
授权与来源资料
使用条件与限制
免费使用 · 保留许可声明本次收录的是公开仓库中采用 MIT 许可的免费版本;免费范围为该版本代码,不代表外部服务或第三方素材免费。
使用时需要遵守
- 允许免费使用、修改、商用和分发该版本代码。
- 分发代码副本或实质性部分时,保留原作者版权声明和完整 MIT 许可声明。
- 代码按现状提供;担保与责任限制以原许可证及适用法律为准。
额外费用与待核对事项
- README 建议文章图片优先使用 CDN 外链,若无法使用 CDN 才将图片放入 assets/img 对应目录并配置 media_subpath。
- 贡献内容需先 fork 仓库、在本地分支撰写文章,再向原仓库提交 Pull Request,由维护者审核合并后才算完成贡献。
- 该模板定位为社区协作写作平台,内容贡献以技术文章、技巧与文档为主,需遵循仓库的贡献流程与 Front Matter 格式约定。
- 演示图片、字体、图标及其他第三方素材需按各自许可核对,不能仅凭代码的 MIT 许可判断。
- 域名、托管、数据库、支付或 AI 等外部服务可能另外收费。
查看原文依据
Permission is hereby granted, free of charge
许可证原文
It's highly suggested to use CDN links for images.
README 原文
create a pull request to the [original repo](https://github.com/Grow-with-Open-Source/Notebook)
README 原文
https://github.com/Grow-with-Open-Source/Notebook/blob/main/LICENSEhttps://github.com/Grow-with-Open-Source/Notebook/blob/main/README.mdyou're always welcome to make your techinal writing contribution by writing you own blog
README 原文
DeepSeek 根据仓库许可证和 README 整理 ·2026-10-02。结果仅覆盖已读取资料,依赖、图片、字体及后续条款变更以各自原文为准。
项目核对记录与介绍依据
模板资料
- 来源平台
- GitHub
- 资料与维护参考分
- 资料较完整 · 82 / 100
- 技术栈
- Jekyll · HTML
- 网站类型
- 博客 · 文档 · 启动器
这个分数如何计算
本站按许可资料(最高30分)、演示链接(12分)、预览图(10分)、Star数(15分)、记录的维护时间(15分)、描述完整度(8分)、功能记录(5分)和分类资料(5分)计算。它不是代码、安全或性能测试,也不是 Google 评分;有链接不代表已实测可用。
这个项目需要核对什么
- 记录的仓库更新时间
- 2025-03-08
- 截图检查日期
- 2026-10-02
已收录演示链接。请用你的内容与屏幕尺寸检查;有演示不代表表单、认证或支付已经可用。
目录记录的主要技术栈是 Jekyll。请通过依赖清单和锁文件核对实际版本与托管要求。这些说明基于收录资料,不代表代码审计或部署实测。
查看具体选型方法 →介绍的制作与核对状态
介绍由 AI 辅助整理目录与仓库资料。仓库作者不等于这篇介绍的审核者。
已完成服务器许可规则与 AI 来源核对;未经过人工编辑审核。
查看当时使用的来源资料
SHA-256: d8a36703e65197bea34894a9dd2d9cb4ed24005182065a6cee7e6ce01c63a7f7
2026-10-02T17:42:13.287Z
来源文件 / 仓库# NoteBook
<div align="center">





<br>
[](https://github.com/Grow-with-Open-Source)






</div>
Welcome to **Notebook**, an open-source project designed with beginners in mind! Notebook is all about creating a friendly and supportive environment for developers of all levels. Whether you're just starting your coding journey or you're an experienced pro, there's a place for you here.
With Notebook, you can easily contribute to technical content and gain valuable experience in the world of open source. Our blog-like platform, built on GitHub's [Jekyll](https://jekyllrb.com/ "visit offical jekyll website") framework and adorned with the user-friendly [Chirpy](https://github.com/cotes2020/jekyll-theme-chirpy "goto chripy offical repo") theme, makes it a breeze to share your knowledge and learn from others. **It's a win-win situation:** beginners learn from the insightful posts by contributors, while contributors get the satisfaction of helping others on their coding journey. Join us at Notebook and let's learn and grow together!
<div align="center">

</div>
## Contribution
Hey there, fellow developer !!!... I'm happy to see you intrested in contributing to this open source project. Since, this project is an open notebook for everyone, you're always welcome to make your techinal writing contribution by writing you own blog, tip & trick, documentation and much more. All you have to do is write down your content in `markdown` *(just like how wrote this README.md file)* and place those file within `_posts` directory.
> First time ???... Then I highly recommend you to check out [CONTRIBUTING.md](docs/CONTRIBUTING.md "goto CONTRIBUTING.md").
- **Step 1:** Setting up development environment. Refer to [CONTRIBUTING.md](docs/CONTRIBUTING.md "goto CONTRIBUTING.md") that guide you to setup the required evironment for the project.
- **Step 2:** After setting up environment, [fork](https://github.com/Grow-with-Open-Source/Notebook/fork "Let's fork this repo") this repository and clone it in your local system, using the following command:
```bash
git clone https://github.com/<your-github-profile>/Notebook.git
```
- **Step 3:** Build and run the project within your local machine.
```bash
# installing required dependencies for the project to run
bundle
# host the build within your local machine
bundler exec jekyll s
```
> [!NOTE]
> If project build is successful, then you can view the project build that is hosted through your [localhost:4000/Notebook](http://127.0.0.1:4000/Notebook/). Well done, you have successfully setted up the project within your local system.
- **Step 4:** After you have setted up the project and done analyzing it, Create a new branch to work on. Make sure your branch name is small and simple.
```bash
# create and checkout to your new branch
git checkout -b <your-post-name>
# checking which branch you currently in
git branch
```
- **Step 5:** Now, go ahead and enter your author details within the [`authors.yml`](_data/authors.yml) even before you started working on your technical writing. Just make sure you're entering the details in the following format:
```yml
# Make sure the key value does not match other authors
unique_key_value:
name: <author_name>
twitter: <twitter_id>
url: <personal (or) contact url>
```
<details>
<summary>Looking for an example ?</summary>
<div>
```yml
shamith_watchdogs:
name: Shamith Nakka
twitter: shamith_nakka
url: https://github.com/iamwatchdogs/
```
<div>
</details>
- **Step 6:** Now to the actual task, Create a new markdown file with `YYYY-MM_DD-your-post-name.md` *(make sure your post name is in small letters and separated by single dash)* within the [`_post`](/tree/main/_posts/) directory.
- **Step 7:** Each and every markdown file that you have created for content writing should contain the following meta data called `Front Matter
`:
```md
---
title: <title>
date: YYYY-MM-DD HH:MM:SS +/-TTTT
categories: [<main_categories>, <sub_categories_1>, ..., <sub_categories_n>]
tags: [<tag_1>, ..., <tag_n>]
author: <respective_author_key_value>
media_subpath: "/assets/img/<your_img_directory_name>/"
image:
path: <name_of_the_img_for_page_cover>
alt: <alternative_text>
---
# Your content writing begins here
```
<details>
<summary>Looking for an example ?</summary>
<div>
```md
---
title: Welcome to the Notebook
date: 2023-09-21 20:34:00 +0530
categories: [Welcome, Guide]
tags: [introduction]
author: shamith_watchdogs
media_subpath: "/assets/img/welcome-page"
image:
path: "welcome-img.jpg"
alt: "Welcome Page"
---
# remaining content down below
```
<div>
</details>
> [!NOTE]
> - Note that the `+/-TTTT` in the `date` section refers the **UTC offset**. You can find your **UTC offset** value by searching for your country in the [list of UTC](https://en.wikipedia.org/wiki/List_of_UTC_offsets "Goto List of UTC offsets"). And if you're from India, you can use the above UTC offset from the example.
> - Also not that `media_subpath` and `image` *(including its sub attributes)* are optional and only need when you're going to add images to your post.
> - If there are more than one person working on a single post use `authors` attribute instead of `author`. And the input for the `authors` attribute will be a list of key of authors specified within the [`authors.yml`](_data/authors.yml) file.
- **Step 8:** Now, you can proceed to write your technical content. And if you have any images that are part of your technical writing, then create a new directory using your post's name within `assets/img` directory as `assets/img/<your-post-name>`. Now add your images to your folder. After adding images to your folder, don't forget to add location to `media_subpath` attribute as `media_subpath: ../../assets/img/<your-post-name>`. Now, you can directly access your images with specifying full relative path.
> [!NOTE]
> It's highly suggested to use CDN links for images. But if you could not for any reason, then you can proceed with above process.
- **Step 9:** After you done with your changes, commit them and push them back to your forked repo.
```bash
# tracing new files and stagging new changes
git add .
# commiting your changes
git commit -m "Added <your-post-name>"
# check your branch name
git branch
# push your commits to your origin repo
git push origin <your-branch-name>
```
- **Step 10:** Now, create a pull request to the [original repo](https://github.com/Grow-with-Open-Source/Notebook). [Learn about Pull requests](https://docs.github.com/articles/using-pull-requests "offical GitHub documentaiton")
And that it, you have done it !!!... Now, it's time for the maintainer to review you work and merge you pull request. If there's any issue with your pull request, then the maintainer will contact you and asks for a few changes. And he merges your Pull request, you have successfully did your first open source contribution that actual help others.
Everybody can see you work and make use of it. Good job, mate !!...
# Contributors
Thank you for your valuable contribution to this repo. You work will not be forgotten..
<div align="center">
<a href = "https://github.com/Grow-with-Open-Source/Notebook/graphs/contributors">
<img src = "https://contrib.rocks/image?repo=Grow-with-Open-Source/Notebook"/>
</a>
</div>看看同类模板
对比同技术栈与用途的模板,找到更适合的视觉与内容结构。

al-folio
al-folio 是一个面向学者与研究人员的 Jekyll 作品集主题,设计简洁、响应式,适合搭建个人学术主页。
Jekyll · 作品集

minimal-mistakes
:triangular_ruler: Jekyll theme for building a personal site, blog, project documentation, or portfolio.
Jekyll · 作品集

Beautiful Jekyll
Beautiful Jekyll 是一个在 Jekyll 生态中经过长期打磨的博客主题,由 Dean Attali 维护,自 2015 年起积累了超过 5 万用户。
Jekyll · 博客

jekyll-TeXt-theme
💎 🐳 A super customizable Jekyll theme for personal site, team site, blog, project, documentation, etc.
Jekyll · 博客

startbootstrap-clean-blog-jekyll
A Jekyll version of the Clean Blog theme by Start Bootstrap
Jekyll · 博客

So Simple
So Simple 是 Michael Rose 开发的 Jekyll 主题,定位清晰:为文字和图片提供一个干净、可读性强的展示框架。
Jekyll · 博客
