yep, the whole point is to keep the process seamless. So with the browser plugins enabling access to the network, the actual content getting fetched would just seem like the result of any other normal reply a browser gets from a GET request elsewhere.
As for getting the content itself onto the network, it is pretty much just simple data storage on the network and with the DNS module set it up as a service which can then be accessed via the browser. The current sprint(rust-3) has a deliverable to show this in usage which you can currently see getting worked on in the examples of the repo. It’s a CLI example showing the same process.