Include design concepts in documentation
As a new senior developer/engineer to Avocode I feel like the product/documentation is still skewed towards those that come from a Design background. I really like what gap Avocode is trying to fill but I think it would be more helpful to define design terminology in the documentation. Developers - especially junior developers won't often have the same mental model as Designers
For example, what does "Layers" mean? Why would I want to use Slices? What benefit does XYZ have to me as a Developer? How does XVZ improve my workflow? The documentation is about how to use the product - which is still necessary for new players. However having sidebars or links to other pages that explain Design concepts and how they relate to Avocode would be more helpful in understanding how I - as a Developer - can use Avocode and the designer to achieve the best outcomes.