update OBS UMN according to helpcenter 2.0.17

[MrGourd]

• Added the description about the SMN message structure: smn-enabled-event-notification.md
• Fixed some descriptive and ease-of-use issues.
• Deleted unnecessary .rst files.

[gtema]

Thanks for the update. There are however some critical issues with it:

• not a single rst file in the project is currently unnecessary. The whole documentation tree is build on those rst files. They replace index.md and other md files simply including other files. This is required to be able to properly render complete otc documentation
• due to dropping of rst files the build is now broken, see https://swift.eu-de.otc.t-systems.com/v1/AUTH_73733c21728443609ee0b47f64b5ce0b/zuul_logs/e3b/103/719244eae3219e0a35337c1749ea59ad6ac13f33/check/tox-docs/e3bb074/job-output.txt for details
• you reintroduce public_sys-resources for the images common between all services. Due to the overall size of documentation and trying to improve maintenance we moved those into common doc/source/images

[MrGourd]

Hi, @gtema
Since the overall structure of the Git repository has changed, I still have some questions about this. I hope you can answer thme so that I can synchronize the update request to my colleagues.

1. Does this mean that all .rst files in the current repository are built automatically and that we only need to update the .md file when updating the document?
   2.If a new .md file is added during the update, how can the system identify the location of the new file in the document directory structure? Is the document tree built based on the Help Center production environment? If so, then I understand the logic here.

[gtema]

1. Does this mean that all .rst files in the current repository are built automatically and that we only need to update the .md file when updating the document?

They are not built automatically, but manually. If you look at index.rst in the doc/source/index.rst you will see what it includes and so on and so on. rst files are currently describing the whole skeleton of the documentation, while the text itself remains in md files

2. If a new .md file is added during the update, how can the system identify the location of the new file in the document directory structure? Is the document tree built based on the Help Center production environment? If so, then I understand the logic here.

When a "leaf" .md file is introduced it must be included in the .rst file of the corresponding documentation level.
When a index like .md file is introduced (what previously was used for creating sections of the documentation) a corresponding .rst file pointing to the leaf .md files should be introduced. It (in turn) is then included in the index.rst of the upper level - See like obs/UG/cors.rst is including cors-overview-(console).md and configuring-cors.md while being itself included in obs_console_operation_guide.rst (included in index.rst). The best way of file structuring is currently implemented in vpcep service where the dirctory structure stricktly follows expected documentation structure what makes it really easy to navigate in the repo. It would be really great if every service starts using this structure to make all our lives easier.
And yes, the tree is based on the current documentation structure

[MrGourd]

I think I see what you mean. My colleagues and I need to analyze this requirement before communicating with you. Thank you.