no more /assets folder in Revo 2 beta 5 onward?

Correct me if I’m wrong,
There is no more /assets folder in Revo 2 Beta 5 onward, right?
So where all the elements should be placed?
/core/components?
Shaun’s video MODx Revolution :: Creating a 3rd Party Package, Vol 1 still uses /assets folder.
I just want to know this, since I want to make a new snippet in Revo.

Installing tiny creates an assets/componants folder.

There is no more default assets folder on install but most of the available 3rd party components for Revolution create it on install if they have files that have to be accessed from the front end.

You can install Quip and look at the directory structure (core/components for classes - assets/components for accessible files like connectors, js, etc...).

Jason always say that he don’t want to enforce the use of an assets folder since it’s no more mandatory, so it’s up to you wether you want to use a similar structure or just create your own.

I see.
And where the image/vids/template files should go (as recommended)?

From what i can see and make out the whole idea is that there is no recommendations it is up to each developer, the whole idea is to make it mega flexable, "I think"

I.E I have a folder for each context that runs it own site to contain the stuff for those plus one to share amongst sites.

That’s the idea yes!

I still use an assets directory like i did for Evo, but it’s my choice not a particular recommendation.

Hmm...
It can be an obstacle if the "freedom" goes to "anarchy".
What I can see right now, this unordered flexibility will bring a confusion when deals with documentation or tutorial.
A convention can be taken just for the sake of clarity.

In Revolution, none of the traditional directories are there anymore. This is evident if you download the advanced package; all of the standard core file locations (manager/, connectors/, or even the base_path) are completely configurable and the installer deploys them where you configure them. As for assets/, this also needs to be configurable (which it is, though not at install time) to support all the new possibilities for deploying Revolution. Consider multi-domain deployments that share one core configuration (i.e. manager/database) and a common path for web resources: this "assets" location is configurable for that reason, and you can even use the common shared location and override this per context (using context settings), if needed.

This is not an attempt to create anarchy, though I do believe strongly that humans need clear, simple principles rather than detailed rules and regulations to innovate and create to their full potential. Best practices will evolve as more people make use of all of the changes/features in Revolution; I do not pretend to know all of the possibilities that can be achieved using these features and I don’t want the product to get in the way of those who want to find out. It’s a delicate balancing act, between creating potential and generating confusion, but once more documentation is completed that describes the motivations that went into these changes/features I think it will be completely understandable and provide some powerful tools for MODx component developers as well as the end-users they are developing for.

OK then.
I will try to start creating something first.
We’ll see how it goes.

Thx a lot, guys.