Public map of Webflow's focus of development and growth

As Webflow is growing, more and more people would ask for more and more features in all sorts of directions. Loss of focus is really dangerous, as it can bog down the whole development process, make the interface clumsy and distort market positioning.

Therefore my suggestion is for Webflow to publish a diagram of its planned areas of focus - where features should be natively developed, along with its areas of focus proximity - where features should be available via integration with third-party services and area out of focus - where Webflow should know not to get involved, but only suggest third-party services, at best. 

This would help both the Webflow team and the community better decide what should be developed and what not. 

As an illustration of my suggestion, I am attaching a sample "focus map":

  • John Smith
  • Feb 9 2017