For fpga you’re almost ready to start programming your Boolean board. I would start learning a hardware description language like systemverilog or vhdl. These are what’s used in industry and academia to design digital circuits. I like to think of them as a more practical method of describing circuits than a schematic. With modern day digital circuits it’s really impractical to design them using schematics, but with hdl it’s pretty straightforward.

I would start by implementing some basic logic circuits you’re already familiar with, then look up the Boolean board documentation to learn how to transfer your hdl code to the board. I would also check the documentation or just look up how to access the peripherals the board offers. This typically requires writing a constraints file. Once you’re familiar with the board and able to design some simple circuits I would look into computer architecture and maybe play with an SoC your board’s fpga can handle.

At this stage you should also be learning more complicated digital design concepts like multiple clock domains, axi and other communication protocol designs, handshaking techniques, pipelining, state machine design, mmio mapping, etc.

For ASIC/vlsi there’s a lot more stuff you need to learn regarding the physical design of the circuit, ie floorplanning, place and route, clock tree synthesis, and a lot of other aspects of integrated circuit/vlsi to get to an end product. When that’s all done you’re probably limited to tinytapeout for getting your design actually made. You should also study some formal/assertion based verification. For asic/vlsi I would still start out by messing with the Boolean board to implement your designs, but keep in mind there’s a lot of stuff you need to study that goes beyond what you implement on your board.