Different switch chips with different capabilities are used in different Mikrotik models. You can use some of them for VLAN handling, but for a beginner, it is definitely better to use the software bridge which works the same on all models, and has the full set of capabilities. The only drawback, which may however be quite significant, is the associated CPU load.
The best tutorial regarding VLANs on Mikrotik is here.
The command line configuration exports can be easily used to setup the configuration using GUI, as the configuration structure is a single one. E.g. the /interface bridge vlan table in the configuration export means “press the [Interface] button, then press the [Bridge] button, and then choose the [VLAN] tab” on GUI.
The “old way” (one bridge per VLAN) has some advantages in certain niche scenarios. You can also create several bridges supporting many VLANs each, and the same VLAN IDs can be used on multiple bridges without leaking to each other. But that’s also only necessary for very specific use cases.