Potential Supported Sources

👨‍💻 Framework Development » Framework Design
1

This is a post to talk about possible sources for Frontity. Right now we have in mind these:

WordPress.org REST API

https://developer.wordpress.org/rest-api/

This is the default REST API for self-hosted WordPress sites.

WordPress.com REST API:

https://developer.wordpress.com/docs/api/

This is the REST API of the sites hosted on WordPress.com by Automattic.

  • The idea of using WP.com as a free Headless CMSs for new blogs it’s very interesting because they won’t need to host a WP server themselves.
  • Frontity would be also useful for big sites hosted in WordPress VIP (Techcrunch? :wink:)

WordPress.org WPGraphQL plugin:

https://www.wpgraphql.com/

This is a very interesting plugin that gives a GraphQL endpoint to WordPress.

  • It may be more efficient for some type of queries that require more than one request in the REST API otherwise.

Other Headless CMSs (Contentful, Sanity…):

https://headlesscms.org/

There are many other Headless CMS’s out there that offer APIs.

  • It opens the door to no WordPress CMSs.

Ghost.org REST API:

https://blog.ghost.org/jamstack/

It looks like Ghost is exploring the Headless CMS possibilities. It may be interesting to see what’s their approach. For example, they have a webhook service which may be used to trigger a new deploy of static pages.

2

We think we should go for both the WP.org REST API and WP.com REST API because they are pretty similar and that way we make sure the abstraction on top makes sense. It’s easier to make decisions about the abstraction for two things than for one.

We should also look at the other options to make sure they can be easily integrated in the future with the chosen abstraction.

1 Like
3

For this possible future CMS we could also analyze Strapi. It is free and open source like Frontity and it seems they are doing really well

1 Like
4

Following this post

2 Likes