Building an extensible platform is an essential part of our vision for Space. This manifesto should shed some light on what can be extended in Space, as well as how it can be extended.

Today we are speaking with Scott McKinny of Manifold Systems (scott@manifold.systems,) the author of the Manifold plugin for IntelliJ Platform-based IDEs. As a Java compiler plugin, Manifold adds new capabilities directly and seamlessly to the Java language such as type-safe metaprogramming, extension methods, operator overloading, and more. Welcome to the JetBrains Platform Blog, Scott. Before we discuss the plugin, would you tell us a bit about yourself and your background? Most of my programming experience is rooted in tooling. It goes way back to my employment with Borland beginning in 199

Just over a year ago, we announced the launch of paid plugins on the JetBrains Marketplace. Today we want to highlight some of the major updates we’ve made to paid plugin functionality on the Marketplace and in our IDEs during the first year of the Marketplace’s operation.

Most of the data and operations available in JetBrains Space can be accessed using an HTTP API. The API documentation, as well as the HTTP API playground for your Space organization do a good job in describing the types of interactions that are possible. In this blog post, we want to look at a few details about working with the Space API more efficiently. Why would I use the Space API? Having an HTTP API to access Space makes it easy to share content and data with other applications. We've seen our users experiment with creating issues in Space projects, using the API. At JetBrains, we ha