Option in settings to paste link to your Revue form ✔

(Still working progress + adding options)

Select where it appears.

• Home page only

• Bottom of every blog post

• Bottom of every subpage

• Bottom of every blog post and subpage

• Bottom of every page

Allow users to set category tags on posts. On Blotion, categories can be used to filter list of posts.

• Filter posts by category
• Categories available at /blog/category/[category-name]

This is working, need to add UI for displaying categories in post header.

Solution here is to use Umami API to create a new site and store the tracking url as field along with the site details. On page load the tracking code is passed down through to the Document component, where the Umami header script lives.

Users will be able to set a custom logo for their blog.

• Could logo be custom icon for page in Notion? Pull it in from there?

This could be made possible a few different ways.

• Users can sign up with Supabase (login with password) and subscribe to Blogs to gain access.

• Or users need to subscribe to email list to gain access to the blog. This could be using the Revue API ? Check if email is already subscribed if not Subscribe them. On success it will forward user to the password protected blog?

• Easy option would be to just set a password field and Blog owner could distribute the password to users as they see fit.

Users can now choose to display thumbnail images for blog posts. This can be set in the site settings.

If set to ‘show’, a new type of blog post card will be displayed on the home page and posts list page that includes a thumbnail image.

This thumbnail image is determined by the cover image set for the post in the Notion Database.

Currently blog posts are cached at equal rates allowing for fast updates.

To improve page speed performance and reduce unnecessary API calls, as blog posts increase in age the cache headers will incrementally increase.

Current Solution

Allows for the blog content to be edited and update on the live site quite quickly. Usually under a minute with a a few refreshes.

This is good when you first publish a blog post, but if you have finished making edit after the first few hours of publishing, you are forcing unnecessary API calls to regenerate fresh content!

The New Solution

Each time a blog post is requested from the server, the post date will be used to calculate a cache multiplier.

For example a post is last updated 3 days ago.

We can presume the post is probably completed and won’t have any major edits that would require instant updates.

So let’s say any post 3 days old or older will be fresh for 1 day, and it can be stale 2 days if no one comes along to view the post.

For everyday over 3 days we will use the day as a multiplier to aggressively cache the post.

So a post that is 4 days old will be fresh for 4 days and stale for 8 days