I’m sorry that your expectations are not being met by the documentation or the community or the project.
I’ve done a lot of work on the backend but have to admit to have not touched the frontend at all. Today I looked into it for the first time to see if I can understand your grievances and maybe help out a bit.
I personally found the tutorial to be understandable. Having said that, the tutorial was not structured well and it lacked focus / context / motivation; but I am not here to criticise the tutorial, I’m here to try to help you build something cool.
The thing that struck me about the tutorial is it builds a high level API out of a low level API, which is not a beginner thing to be doing! The reason it’s doing that is because the network still being built and the high level APIs and libraries hasn’t had a chance to be created. Later there will be better libraries that will do what you want from your first post, so maybe you just need to wait a bit?
If you have specific suggestions for how you think an API should look (you started along this path in the first post) then that’s valuable to people who write libraries (which is something I have done and may do again one day). I encourage you to more fully conceive a ‘nice api design’ and post it here for a keen developer to implement. Everyone would benefit.
Back to the tutorial, the function “createMutableData” is very close to your method “createTextContainer”. The main difference is the tutorial just creates the data, whereas your function intends to also create an html element with that data in it. Frustratingly, the method “createMutableData” has some hardcoded data in it which should be refactored as inputs to the function. So I’d encourage you to go straight to that function and try to understand what is happening in it, because that’s almost the same as your createTextContainer idea.
If you’re wanting to build an app for SAFE network right now I suggest putting the network storage and retrieval operations into their own file / functions and then you can isolate the complexity of SAFE (maybe don’t even do any SAFE stuff there, just mock the storage for later implementation). When a better library comes out the complexity of that file can be reduced when you need to. And it means you can build your app now rather than wait for the ‘perfect library’ to be made. I’d be keen to hear what you plan to build!
Hope this helps and if you have any specific questions I’m happy to try to help further.