OSPF is one of the dynamic routing protocols that make the network automatically know how to reach everything connected to the network, and automatically route around failed links.
It's pretty easy to get it working in a basic way, but designing ospf-based networks that work well and scale well is something that takes more understanding and practice with it.
My first piece of advice: don't get into the habit of just redistributing all static and connected routes into OSPF - this works in a basic way, but it's hard to see why this isn't a good idea at first. Even so, try to originate routes properly from day 1 so that you've established good habits for the future.
(i.e. if you have an interface with 192.168.1.1/24 configured there, then add a network 192.168.1.0/24 into the networks list, or if you want all interfaces in a range of networks to be ospf-enabled, then possibly define a block of them like 192.168.0.0/16 so that any interface in those ranges will be advertised properly)
Redistributing routes into OSPF from static is generally okay as long as the next hop of the static route points to a non-ospf router.
When given a spoon,
you should not cling to your fork.
The soup will get cold.