If you are not an experienced admin, setting up a brand new network with multiple subnets and VLANs is going to be very challenging.
First off, let's explain VLANs. In very basic terms, setting up VLANs on your switch partitions it into several separate switches. So if I take a 48 port switch, I could setup two VLANs and have the equivalent of two 24 port switches.
Some firewalls will also support VLANs, and can be setup so it can talk to several different VLANs through a single interface, instead of having to run multiple cables. The documentation for your firewall should tell you if this is possible and how to set it up.
Each subnet (that wants to communicate outside of that subnet, to others or two the internet) will need a default gateway inside that subnet. So your firewall will actually need to have IP addresses like 10.70.0.1, 10.70.0.2, 10.70.0.3, and 10.70.0.10.
Communication between the subnets can ONLY take place through the default gateway, so all traffic between subnets will be going through your firewall. This can be a good thing, if you need to filter traffic between them, or a bad thing if your firewall is slow and becomes a bottleneck.
Instead of segmenting the network like this, I'd strongly recommend using fewer, larger subnets. Start off with one for servers, and one for clients. If you think you will grow quickly, use /16 subnets instead of /24. You can still choose to use specific ranges for specific purposes.
If you use a /16 network, say 10.50.xxx.xxx, you can give all your server equipment addresses in the 10.50.0.xxx range and setup DHCP to hand out addresses in 10.50.2.xxx. Since they are all on the same subnet, they can communicate with each other easily. Later on, if you start running out of DHCP addresses, you can simply start handing out DHCP addresses in the 10.50.3.xxx range, without having to reconfigure ANYTHING.
Down the road, when you expand, have a bit more experience, and decide you need some servers to be isolated from the rest of your network, you can setup another interface on the firewall, and start using another range like 10.51.0.0/24 for those systems. Then setup VLANs, or get a second switch. That is easy to add later. If you don't need it now, I wouldn't start with it. The more complicated you make your network, the harder it is to troubleshoot.
If you really want to be clever, when you pick which address ranges to use for different purposes, choose ones that can easily be subnetted later, so you only have to change the subnet mask on everything if you want to isolate them. That tends to be an easier task than changing server IP addresses.