This is a typical problem with entry level networking courses, the examples and scenarios they use are not very realistic and not the way networks are actually setup. Learning about subnets and routing is very important obviously, I just wish they would use examples that are actually more commonly used and likely to encounter.
When setting up networks for businesses VLANs are a core part of this and usually each VLAN is also it's own subnet, something to keep in the back of your mind but as you already said just ignore VLANS for now.
Also creating subnets based on departments or employee roles is not typically the way its done. Normally its done on a per building, floor, or switch cabinet basis. There are exceptions to this depending on security requirements and there are also subnets that will span the entire network i.e. Security cameras, Wireless SSID's and Wireless AP management. Go with what you are instructed to do as part of your assignment of course.
For the subnets the advise I'm going to give will likely go against what is taught in the course but is actually what is easiest and I will explain why. Try and always use /24 subnets for everything but links between routers e.g. Core switch to internet router/firewall. Reason for this is they are much easier to read and understand, especially for minimally trained or untrained IT support staff and junior networking admins.
The servers I'd account for would be:
Two virtual hosts in HA, VMware or Hyper-V. These would run VMs for things like Domain Controllers, Print Server, General File Server (Home drives etc)
Rendering Server
Archive Server
Security Camera Server
Backup Server
Subnets I'd account for would be:
Servers
Security Cameras and Server. Security server would be on both Server and Security subnets
IT Support office
Level 1
Level 2 (Pretending its a multi floor building)
Wireless AP and Wireless Controller
Wireless SSID
Core switch to firewall (/30)
Hope this is helpful and good luck
P.S @Manos When you create a topic tick the follow option