Oh…it could mean a lot of things. Primarily, if you look at the tool Postman, it has the ability to group things into a “collection” and export them as a single json file. Not that you would use json as the format, but if you can’t add the ability to allow us to point to a directory on disk and say “this is the root of my RAML project” and then have everything relative to that directory work within the designer, to me…the next best thing is some sort of zip import/export, where by I could use my favorite SCM, “checkout” my RAML root project with any sub-directories to a location on my local disk. I’d then zip up that directory, then import that zip into the RAML designer so that the entire structure, subdirs and all, would show up in designer. I could then work on all the files as needed, then export the entire thing back out as a zip file that I could then unzip over my existing SCM directory, and the commit the differences. That is NOT my ideal work flow, just a thought on how we might get an improved workflow over the initial designer process.
Having said all that, it would be more ideal, in my opinion, to work on the RAML plugins for IDEs, such as Eclipse, Visual Studio, and Sublime, with code completion, so that we could work within our familiar workflows and on disk, and still benefit the code completion that is very useful especially for new RAML designers. Even better, given the current threads on how large RAML files slow things down considerably when scrolling and such, using an IDE plugin would probably eliminate that issue as well.