Separate wireless from wired infrastructure
Wireless clients should not blur the wired plan. Put the access point on the diagram as a separate component. That keeps servers, storage, and lab infrastructure on the wired side of the topology.
HLBuilder has an access point node type, so a user can represent Wi-Fi coverage without pretending the access point is a switch or router.
Show the uplink clearly
The most useful access point detail is how it connects back to the network. Draw the uplink from the switch or router. If the access point depends on PoE, the switch branch should make that dependency clear enough for planning.
The diagram does not need to include every phone or laptop. One access point node can represent the wireless branch while the service hosts stay visible elsewhere.
Keep service hosts wired when possible
A homelab service host should usually be drawn on the wired path. That makes storage, backups, and IP assignment easier to follow. Wireless access can still be part of the user path, but it should not hide where the service runs.
Use the service library after the network path is clear. That keeps service placement tied to nodes instead of just a list of app names.
Builder checks
Check
Access point appears as its own node.
Check
Uplink to switch or router is visible.
Check
Wired servers and NAS devices remain on wired branches.
Check
Wireless branch is labeled separately from service hosting.
Common questions
Should an access point be drawn as a router?
No. If it is being used as an access point, draw it as an access point so the gateway role stays clear.
How does HLBuilder show Wi-Fi planning?
HLBuilder has an access point node type that can connect to router or switch nodes on the visual canvas.