Asset Store and Packages

I've been working on a project that I'm reasonably close to submitting to the asset store. It consists of editor and runtime scripts mostly to extend Unity functionality. I was wondering if I should submit it as a package, in the sense of a folder with a package.json etc as per https://docs.unity3d.com/Manual/PackagesList.html. In trying to search for information about submitting a package to the asset store, it seems that the asset store just uses the word 'package' to mean "thing that you submit to the asset store" - i.e. just a normal Unity project is referred to as a package in the asset store.

This is confusing and unhelpful, and is making it hard for me to find any useful information about this. So - is it worth converting my project to a package? It seems to be the way Unity is going, and I wouldn't mind learning more about authoring packages. Secondly, is there a good source of guidelines for structuring packages - the documenation here https://docs.unity3d.com/Manual/cus-layout.html is really not adequate.

Can I include anything I would include in a traditional Unity project? For example, in my existing project I have examples which include scenes assets - I'm not sure whether this is appropriate for a package or where the example scene would live in the package folder hierarchy. Thanks.