@PeterRobinson I can imagine the frustration of those conversions, a bit like groundhog day!
The kind of publishing you describe will be possible from day one (so called static website generators can facilitate this), what's more difficult is websites that allow content to be created through interaction with the user (comments on a blog, forum posts), or where content is generated in response to user input or interfaction or something else dynamic (search, word clouds, a real time clock are examples of these two).
These will happen in time - MaidSafe already demonstrated a way of allowing users to comment on a blog, which @Seneca plans to use to build a forum application. Not everything that the current dynamic web does will be possible from day one, but quite a lot of it, and more with time. Also, some things that the current web can't do, or does badly, will also become possible when SAFEnetwork launches.
@Stark, I think @Anders has a point about breaking things by hacking application code on the client. This will be possible if applications are not designed well, which might happen as quick and dirty ways of solving the issue I just mentioned in my response to Peter, above.
If an app can modify data that other users of the app can see when they use the app (e.g. blog comments) this creates the opportunity for anybody to create a modified version of the app on their own computer, which when they alone run it, messes with the behaviour of the (unmodified) app run by other users - by messing with the data (what @Anders referred to as meta data).
Blog comments are a mundane example, to illustrate the issue. When developers build dynamic apps that are designed to involve multiple users, ensuring good behaviour of the app regardless of what may be done to the dynamic data shared by users of the app is going to be a significant headache for developers. This isn't unique to SAFEnetwork though, spamming comments is an example that doesn't require modification of the code. But access to the code lowers the bar for more sophisticated "messing" with apps, so it could be more of an issue on SAFEnetwork.