-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database support to create blog pages from Notion tables #11
Comments
Hi @conradlin If you really want a quick solution to retrieve Database data, you can use Official Notion API. |
You can currently use One of the issues I encountered when building my project was that I needed to get schema of a database to be able to implement a way to filter my posts. I could have used the values inside each post but I wanted to also show categories that don't have any post attached. This led me to fork If you want to be able to manually sort your database entries without relying on a property of the table, this is your only option. Notion's public API doesn't support database's views, so using the private API is the only way I've found to be able to drag'n'drop entries to sort them any way I want. I reached out to support asking if/when will they add support for Views and I got the same response I got for years when asking about the status of the public API, so I wouldn't count of having it any time soon. They're a small team and usually take their time to build everything the way they consider best. |
Describe the solution you'd like
I'd love to work together with you to develop database support so we can iterate on posts and create the custom CMS page for each.
Describe alternatives you've considered
Previously, I was using Gatsby <> Notion integration but its since been depreciated. Your solution is great but doesn't allow me to add a custom blog template for blog pages, and also specify slug, page descriptions, etc.
Additional context
I hosted a livestream today where I built with your tool live and would love to continue developing more!
The text was updated successfully, but these errors were encountered: