Matt

I'm enjoying seeing these small improvements to make the layout modern. It is even better to see community participation with suggestions for improvement.
@Adriano Faria made great observations.

Thanks for reading! I've love to hear any questions you have. We plan to go into much more detail, and even beta test it right here on our own community.
No doubt there will be some questions about why it's a cloud exclusive feature, so I've created a topic for that discussion here: 
Let's keep the discussion in that topic and allow questions about the feature to be posted here on the blog.
 

Thanks for reading! I've love to hear any questions you have. We plan to go into much more detail, and even beta test it right here on our own community.
No doubt there will be some questions about why it's a cloud exclusive feature, so I've created a topic for that discussion here: 
Let's keep the discussion in that topic and allow questions about the feature to be posted here on the blog.
 

Hey, I wrote that on my childhood Casio keyboard!

Well that explains why you became a coder I guess. 

Hey, I wrote that on my childhood Casio keyboard!

Can we talk about the terrible music on the video? 😅

By the way… 30.3k unread emails.  Your inbox is worse than mine!!

It still does. 👏

Unless it has changed since I worked on this, I think one really important thing to call out is the GraphQL API respects permissions. The REST API treats requests as admin requests (unless you specifically use the OAuth flow to get a token). The GraphQL API uses the logged in member. So you can query a list of topics and it'll be accurate for that member, which is really handy.

It is satisfying to see that the IPS team is always working to modernize software, the information is a little complex for my knowledge, but I see it as a big improvement.
Some things are outdated, but like the calendar and gallery app, little by little they are being improved.

It's already automated.
Thanks, and I agree. It's on my TODO list for the next iteration.

Woohoo 🎉 It's nice to see this become public after a long time being an internal tool.
Given one of the big selling points is the type system, it would make sense for you to include the type of each field in the documentation. Personally I wouldn't even bother hand-rolling documentation - let a tool parse the schema and just make the output available to developers (and include docs on using Graphiql GUI tool too). The docs you've put together are losing the inherent relationships that GraphQL has; I think it'd be frustrating to use them as a reference (for example, here's the query to get a club, but it doesn't tell you what fields are returned, what types they are, if they have sub-fields etc.)
When I worked on customer sites at IPS I spent a lot of effort trying to query stuff in Pages blocks using raw PHP blocks and the IPS framework. Being able to write a GraphQL query to fetch everything I needed would have been great.

We have some thoughts on this, but nothing in the roadmap at this time. Generally speaking, we want Commerce to be able to handle monetisation of your content across the suite.
Not at this time, but happy to hear your thoughts? Do you mean pre-made templates you can toggle between?

We have some thoughts on this, but nothing in the roadmap at this time. Generally speaking, we want Commerce to be able to handle monetisation of your content across the suite.
Not at this time, but happy to hear your thoughts? Do you mean pre-made templates you can toggle between?

Great work, well done.
When this come I will add back Gallery to my subscription, do I got discount? (Watching Matt pull his hair) 🙂

We have some thoughts on this, but nothing in the roadmap at this time. Generally speaking, we want Commerce to be able to handle monetisation of your content across the suite.
Not at this time, but happy to hear your thoughts? Do you mean pre-made templates you can toggle between?