How to read this documentation
- First of all, you should already know the basics of HTML, CSS and JavaScript. You should especially know CSS selectors, or at least know that they are there and have at least a vague idea of them. You should already have basic knowledge of selectors in the bag before you try and study Active CSS. You don't have to be an expert in CSS to the degree the CSS animation wizards are expert, but you should at least know some of the CSS selectors. The more CSS selectors you know, the more tools you have.
- Study or look over all the sections in sequence. The docs have been written in a way that you build up knowledge as you go and don't skip any major concepts. You should just look over the commands, just to get an idea of what they are, and refer to them when you need to use them. Areas such as using the "prevent-default" command, using selectors, the closest selector (<), using attributes "(@data-my-attr}" and the event flow are very useful.
- Check out the concept examples section. That section gives examples of various techniques.
All the main topics really should be looked at, so you know what is possible. Otherwise you may miss something important.
More things will be added over time, so be sure to check back every now and again. Let us know if you need any specific tutorials.
To get started, follow the installation steps in the Installation section. This will guide you through setting up a blank "config" file so you can start coding.
This is a relatively unknown language, so there probably won't be anything on Google or stackoverflow, but there is a search box to the top right, and you can always get in contact via the support form if you have any questions. Right now, using the support form is probably your quickest option.
Important note: You need to also be aware right away before you start playing around that <a> tags and perhaps some other tags may need the command "prevent-default: true;" in order for events to work as expected and to not redirect to a new page when you click on them. You would have had to do this natively anyway if you were writing functionality like this. You can set up a general event for this so you don't have to type it in a lot, or you can set up specific rules - like set a class in the <a> tag for internal or external events so prevent-default only happens on those.
Let us know if you make any great websites!
Good luck!