Skip to content

nerdymomocat-templates/webtrotion-astro-notion-cms-website-blog

 
 

Repository files navigation

Webtrotion Cat

Webtrotion

Note

Ideally you might want to read this page on the rendered website here to get a feel of how it looks like.

Table of Contents

  1. Acknowledgements
  2. Why Webtrotion
  3. Why Notion and Astro
  4. Key Features
  5. Quick start
  6. Preview
  7. Notion Properties
  8. Local Run
  9. Extra Configuration Options
  10. License
  11. Notes

Webtrotion is a simple to install, configurable to $n^{th}$ limit starter built with the Astro framework in conjunction with Notion. Use it to create an easy-to-use blog or website.

(Skip to features and setup)


Acknowledgements

This theme is built based off three major contributions:

  1. Astro Cactus
  2. notion-astro-blog
  3. And this person on fiverr who got me 80% there on how to integrate notion into cactus theme

Why Webtrotion

Webtrotion was built with the simple idea - most notion based builders, require at least one of these four things:

  • A custom domain, or being willing to use a vercel like domain
  • Just have blogposts be editable in Notion while pages are edited in the repo
  • Require some third party tools, or are not free to use.
  • Are not configurable because they are either based off third parties like super.so or the configuring requires editing multiple code files.

And I did not want that. We want something that converts well into a static site, can be hosted on github for free using the github.io domain, and can have both pages and blog posts and be configured pretty easily.

Why Notion and Astro

  • I use Notion for all my notes, and it did not make sense for me to download them into an md file, carefully figure out the logistics and push/pull with other SSGs like Quartro, Eleventy, Hugo or Jekyll.
  • I could have used another CMS but again, I use Notion, and it is easier to keep the content in one place. Notion also comes with interesting affordances that other CMS don’t: WYSIWYG for various components, block level permissions (to add drafts to post text), easy collaboration etc.
  • There are some NextJS options that kinda fulfill this criteria but I do not know NextJS and I did not want to figure it out at the moment, for example: Notion Next, Morethan-log, and Notion-Blog-NextJs

Key Features

  • Astro v4.11
  • Integrates with Notion to create a website and not just a blog
  • Single file configuration
  • TailwindCSS Utility classes with Notion Color Matching for everything.
  • Accessible, semantic HTML markup
  • Responsive & SEO-friendly
  • Dark / Light mode, using Tailwind and CSS variables that can be modified using a single config file
  • Satori for creating open graph png images that includes your featured image
  • Pagination
  • Automatic RSS feed
  • Webmentions
  • Giscus comments
  • Auto-generated sitemap
  • Pagefind static search library integration
  • Pinned Posts
  • Shiki Transformers for Code Blocks
  • API request output caching on Github Actions for fast build times
  • Mini blog streams (idea copied from Linus’s stream)
  • Auto-generated related content and pages that link to this page
  • Pretty looking wikipedia like popups on hover that works with links to any block on any page.

Demo

Check out the Demo, hosted on Github using Github actions

Quick start

Notion Setup

  1. Duplicate this database into your Notion account. Remember to duplicate it as a standalone new page, rather than into an existing page.
  2. Create a Notion integration
  3. Get your API secret
  4. Give your integration permission to the complete database you just duplicated
  5. Get your database id of the database you duplicated. Database id is the 32 character alphanumeric string right after your workspace in the URL. It is the easiest to get this ID on a web browser rather than the Notion app. Getting database id from Notion

Github Setup

  1. Create a new repo from this template if you want to have a one and done standalone repository. If you want to be able to access and sync changes made in the template to your repository, choose to fork it instead.

📝 If you do not choose to add a custom domain, the name of your repository matters. If the name of the repository you create is .github.io; your website will be accessible at .github.io if you use github actions. If you use any other name, the website will instead be hosted at .github.io/.

⚠️ When you first fork the repository, you will see that the github action output fails. This is because we haven’t added or changed notion integration information. Don’t worry, once you add those, it will run successfully.

  1. In your repository settings:
    1. Uncheck template repository if it is checked.
    2. Turn on Discussions in features to use Giscus
    3. Go to Actions → General and set it to Allow All
    4. Go to Pages and set Source as Github Actions
    5. Go to Environmentsgithub-pages; Scroll down to Environment Secrets, click Add New Secret. Set name as NOTION_API_SECRET and the value to the API secret you obtained in Notion Setup.
  2. Go to the actions tab, and choose I understand and want to run actions. On the left sidebar click the action “Deploy Github pages”. It will show a warning saying the scheduled action is disabled in forks. Click Enable workflow.
  3. Set up giscus as mentioned on the website giscus.app. Keep the script it produces open as we will use it in the next step.
  4. Go back to your cloned (forked or created through a template) repository.
  5. Open file constants-config.json in the web UI. This file is the complete setup file for your website. For now, we will make four major modifications:
    1. Change database-id to your database id that you obtained from Notion.
    2. Add your name to author (this is used for HTML semantics and OG image generation)
    3. Add your socials (you can also remove the value for this-github-repo)
    4. Add your giscus information to the giscus key. If you do not want you use Giscus, remove value for data-repo in giscus and that will disable the feature.
  6. Save the file and commit+merge to the main repo.
  7. The github action by default runs every 8 hours or on commits to the repo. This can be modified in .github/astro.yml file. You can choose any cron duration.

🥳 And we are done! You can access your website on .github.io or .github.io/ depending on what you chose. Checkout all Supported blocks but tl;dr all blocks are supported except child databases and child pages. This specific page will show up as insecure because it has a direct HTML injection.

📝 Remember, the cron schedule is by default set to every 8 hours. You can change it to run every 2 hours or if you want to push out a change immediately, you can also manually run the github action if you are deploying on github. The workflow name is “Deploy Github Pages”.

Preview

Light Mode Preview

Light mode preview Dark Mode Preview

Dark mode preview

Notion Properties

ℹ️ Pages or posts are only published if: their Published property is checked AND if the explicit publish date is empty or is before the current date.

Property Usage
Page Title of the page or post being rendered
Tags Tags displayed for the post
Excerpt Description used in OG images and RSS feeds
Collection Collection in which the post/page goes. Anything tagged with main or instead, if specified, your menu-pages-collection is rendered as a page.
Published Your post or page is only published when you tick publish
FeaturedImage Image used to generate your page’s or post’s open graph image
Specific Slug The template generates a slug using formula, but if you want a specific slug, you can specify it here
Explicit Publish Date By default, the formula considers the date notion page was created to be publish date. You can override it by setting a date for this property.
Explicit Publish Date By default, the formula considers the date notion page was last edited to be last edited date. You can override it by setting a date for this property.
Rank Want to order single pages (Updates before Papers?) Set rank in ascending order
Pinned Pins post to the top of any collection page, except those tagged with MENU_PAGES_COLLECTION

⚠️ Don’t rename the columns of DB. They are used in the astro code. You can reorder the columns or add any other columns you want.

Local Run

You can run the code locally by cloning the repo.

cd folder
export NOTION_API_SECRET=YOUR_KEY_HERE
npm install
npm run build #we need to build once because that is when all icons are downloaded
npm run dev

Extra configuration options

Key Value
public-ga-tracking-id Your google tracking property id. Steps here.
google-search-console-html-tag Content value of search console property verification tag. More here
webmention Webmention API Key and link obtained from https://webmention.io/
custom-domain If you want to host the site somewhere else
base-path Or subdomain inside the custom domain
shortocdes There are 3 shortcodes atm, two supported, two in works. html shortcode is used to embed html code blocks that start with this line directly into the page. shiki-transform is used to transform code blocks into more expressive representations
references To show related pages, external links, and mentioned media at the end of the post. Set POPOVERS to true to display a snippet when hovering over a post link in the body.
theme Colors for light mode and dark mode
fontfamily-google-fonts Combined URL link for all fonts you want to use from google fonts. Remember to escape spaces in font names if needed
number-of-posts-per-page Number of posts in a page for pagination purposes
enable-lightbox Set to true if you want people to be able to click on your image to open in a new tab
request-timeout-ms Timeout for API requests
menu-pages-collection Collection select value in Notion database that decides if these are pages or blogposts. Set this to value you use for pages.
heading-blocks Which top-level blocks blocks should form the table of contents on right
full-preview-collections Stream like view, where each post is a mini-blog in the same page as a scrollable page instead of being links to individual pages. Any Collection name added to this list will be rendered as stream view.
hide-underscore-slugs-in-lists If the slug starts with _, hide those in post lists, rss and sitemap, but still render them, so that you can share them
home-page-slug By default is set to “home” but can be anything that you want for the renderer to recognize which is your home page from the database
og-setup Open graph setup refers to the images displayed when sharing links. It includes excerpts and creates two columns if a featured image is available. You can customize the title and footnote fonts for the og-image, particularly for non-English blogs. Ensure that each URL has only one font and, if it has a weight, the weight is above 400
optimize-images Converts images to next-gen formats like webp for more responsive sites
redirects Intentional redirects, especially if you are moving systems that astro should redirect to

License

MIT

Notes

  • 📝 If you do not choose to add a custom domain, the name of your repository matters. If the name of the repository you create is .github.io; your website will be accessible at .github.io if you use github actions. If you use any other name, the website will instead be hosted at .github.io/.
  • ⚠️ Don’t rename the columns of DB. They are used in the astro code. You can reorder the columns or add any other columns you want.
  • 📝 Remember, the cron schedule is by default set to every 8 hours. You can change it to run every 2 hours or if you want to push out a change immediately, you can also manually run the github action if you are deploying on github. The workflow name is “Deploy Github Pages”.
  • ℹ️ Aggressive Caching Remember that the setup uses aggressive caching for github actions. These caches are public. If you want to remove caches, you can go to github action workflow and manually delete the caches
  • ℹ️ Multilingual/Non-English blogs Open graph setup refers to the images displayed when sharing links. It includes excerpts and creates two columns if a featured image is available. You can customize the title and footnote fonts for the og-image, particularly for non-English blogs. Ensure that each URL has only one font and, if it has a weight, the weight is above 400

If you end up using webtrotion, please consider buying me a coffee here:

Support Nerdy Momo Cat on Ko-fi! ❤️. ko-fi.com/nerdymomocat

Releases

No releases published

Sponsor this project

Packages

No packages published

Languages

  • Astro 49.6%
  • TypeScript 44.7%
  • CSS 3.8%
  • XSLT 1.5%
  • JavaScript 0.4%