Home

Awesome

jekyll-fetch-notion

The Jekyll plugin introduces the fetch_notion command. This command fetches all Notion content as specified by the _config.yml file and places it directly into your git repository, respecting the corresponding directory structure. This project is a fork of jekyll-notion, created due to incompatible synchronization methods. You can find more details in this pull request.

Note: Data and page fetching are planned for future releases but are not yet available.

The original project was designed with the idea that Notion content should be fetched during site building and not tracked by git. This project, however, takes a different approach. It arranges your workflow so that your Notion content is git-tracked and fetched before site building.

I believe this method aligns better with Jekyll's "ideology" and also offers several advantages:

However, every implementation has its own pros and cons. Choose the one that best suits your needs.

For more insights into my experience with jekyll-fetch-notion, check out these posts:

Installation

Use gem to install:

gem install 'jekyll-fetch-notion'

Or add it to the Gemfile:

gem 'jekyll-fetch-notion'

And then update your jekyll plugins property in _config.yml:

plugins:
  - jekyll-fetch-notion

Usage

Before using the gem, create an integration and generate a secret token. For more in-depth instructions refer to the Notion "Getting Started" guide.

Once you have your secret token, make sure to export it into an environment variable named NOTION_TOKEN:

export NOTION_TOKEN=<secret_...>

Then you can run command to fetch all the Notion content and place it inside your's site repository:

jekyll fetch_notion

Then you probably need to stage, commit and push all the fetched files to trigger your default CI build flow and make your updated site deployed.

Databases

Once the notion database has been shared, specify the database id in the _config.yml file as follows:

notion:
  databases:
    - id: 5cfed4de3bdc4f43ae8ba653a7a2219b

By default, the notion pages in the database will be loaded into the posts collection.

We can also define multiple databases as follows:

collections:
  - recipes
  - films

notion:
  databases:
    - id: b0e688e199af4295ae80b67eb52f2e2f
    - id: 2190450d4cb34739a5c8340c4110fe21
      collection: recipes
    - id: e42383cd49754897b967ce453760499f
      collection: films

After running jekyll fetch_notion command, the posts, recipes and films collections will be fetched with pages from the notion databases.

Database options

Each dabatase support the following options.

notion:
  databases:
    - id: e42383cd49754897b967ce453760499f
      collection: posts
      filter: { "property": "Published", "checkbox": { "equals": true } }
      sorts: [{ "timestamp": "created_time", "direction": "ascending" }]

Posts date

The created_time property of a notion page is used to set the date in the post filename. This is the date used for the date variable of the predefined variables for posts.

It's important to note that the created_time cannot be modifed. However, if you wish to change the date of a post, you can create a new page property named "date" (or "Date"). This way, the posts collection will use the date property for the post date variable instead of the created_time.

Notion properties

Notion page properties are set for each document in the front matter.

Please, refer to the notion_to_md gem to learn more.

Page filename

There are two kinds of documents in Jekyll: posts and others.

When the document is a post, the filename format contains the created_time property plus the page title as specified in jekyll docs.

YEAR-MONTH-DAY-title.MARKUP

The filename for any other document is the page title.

Alternatives

Actually, there are a lot of alternatives available, but, however, mostly all of them are not so mature and hard to extend. This one (like jekyll-notion) is tested by time and easy to extend because of notion_to_md usage.