Since everyone else here has done an excellent job on the technical aspect, I'll speak to planning aspect of this:
The most important thing is what you want to do with the network.
Is it going to be used exclusively for Internet access? If so, your needs are fairly relaxed, and worrying about switching topologies is unnecessary.
On the other hand, it's also possible to use your LAN for filesharing among local computers. In that case, having a fast local network becomes quite important, particularly if you invest in a centralized file server that uses some RAID variety.
If you want to use this network as a learning tool, spending the time to make it truly reconfigurable (e.g. patch panel, etc...) is very much worth the time.
You mentioned you're wiring a half-duplex. Are you wiring the whole building (probably worth the effort, if you're already in the attic)? If it has multiple tenants, it might be worth considering using VirtualLans to segregate the various networks apart. Alternatively, you could just give each building section it's own switch.
Again, VirtualLans are powerful, and worth learning about if you're interested in networking, but not really worth the bother if pure utilitarian functionality is your goal.
Basically, what I'm saying is that the expected usage of the network is (or should be) a critical factor in determining what and how it's laid-out and configured.
Until you determine this, worrying about cat5e vs cat6 and other hardware related decisions is pointless.