blog | single config file ) Robust support

by jtsang4 TypeScript Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | blog Summary

blog is a TypeScript library. blog has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

blog

Support

Quality

Security

License

Reuse

Support

blog has a low active ecosystem.

It has 0 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

blog has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of blog is current.

Quality

blog has no bugs reported.

Security

blog has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

blog is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

blog releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of blog

Get all kandi verified functions for this library.

blog Key Features

No Key Features are available at this moment for blog.

blog Examples and Code Snippets

No Code Snippets are available at this moment for blog.

Community Discussions

No Community Discussions are available at this moment for blog.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install blog

I tried to make configuration as easy as possible. All you really need to do to get started is edit rootNotionPageId. It defaults to rendering my site's public notion page 78fc5a4b88d74b0e824e29407e9f1ec1. You'll want to make your root Notion page public and then copy the link to your clipboard. Then extract the last part of the URL that looks like d1b5dcf8b9ff425b8aef5ce6f0730202, which is your page's Notion iD. In order to find your Notion workspace ID (optional), just load any of your site's pages into your browser and open up the developer console. There will be a global variable that you can access called block which is the Notion data for the current page, and you just have to type block.space_id which will print out your page's workspace ID. I recommend setting up a collection on your home page (optional; I use an inline gallery here) that contains all of your articles / projects / content. There are no structural constraints on your Notion workspace, however, so feel free to add content as you would normally in Notion. There are a few parts of the code with logic to only show comments on blog post pages (collection item detail pages).
Fork / clone this repo
Change a few values in site.config.js
npm install
npm run dev to test locally
npm run deploy to deploy to vercel 💪

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: