Compare commits

..

1 Commits

Author SHA1 Message Date
803144d4a5 fixing the figure 2023-02-23 00:56:18 +00:00
8 changed files with 7 additions and 32 deletions

View File

@ -47,12 +47,3 @@
.navigator-container .card li { .navigator-container .card li {
padding: 0.2rem 1rem; padding: 0.2rem 1rem;
} }
/* A "nice" workaround to let us keep l2 level permanently open
* but hide child ul's not underneath current selection.
* The only eventually open issue is that this way the whole child tree is
* open including all subtrees.
*/
.docs-sidebar-toc li.toctree-l2:not(.current) > ul {
display: none;
}

View File

@ -1,18 +0,0 @@
Context - Whom to address for Feedback?
=======================================
In case you have any feedback, proposals or found any issues regarding the HelpCenter 3.0, you can address them in the corresponding GitHub or Gitea repositories.
Issues or feedback regarding the **internal Helpcenter** as well as new feature requests can be addressed by filing an issue on the internal **Gitea** repository under https://gitea.eco.tsi-dev.otc-service.com/docs/docsportal/issues
If a documentation to a service is missing, please open a ticket on the doc-exports repository: https://gitea.eco.tsi-dev.otc-service.com/docs/doc-exports/issues
If you have found any problems which affects the **production Helpcenter** please instead open an issue on **GitHub**.
- In case it is a general issue, create it in the docsportal repository: https://github.com/opentelekomcloud-docs/docsportal/issues
- If you have found anything wrong regarding a specific documentation, please open an issue on the corresponding repository under opentelekomcloud-docs. For example, on ECS you can open an issue here: https://github.com/opentelekomcloud-docs/elastic-cloud-server/issues
If there is a request for completely new service or new document type (which was not yet introduced to HelpCenter 3.0) then please open an issue on the otc-metadata repository: https://gitea.eco.tsi-dev.otc-service.com/infra/otc-metadata/issues
For general questions you can write an E-Mail to the `Ecosystems Squad <mailto:dl-pbcotcdeleco@t-systems.com>`_.

View File

@ -8,5 +8,4 @@ Helpcenter Training
introduction introduction
workflow workflow
difference_gitea_github difference_gitea_github
context
faq/index faq/index

Binary file not shown.

Before

Width:  |  Height:  |  Size: 506 KiB

After

Width:  |  Height:  |  Size: 478 KiB

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View File

@ -29,7 +29,11 @@ Document Change Process Description
8) Assigned squad member(s) start the review process of the auto-created Pull Request and communicate their feedback. This can be done via the included functionality of Gitea to provide comments to a specific line of code. 8) Assigned squad member(s) start the review process of the auto-created Pull Request and communicate their feedback. This can be done via the included functionality of Gitea to provide comments to a specific line of code.
9) If the Pull Request fullfils all expectations, the Pull Request will be approved by the reviewer via ``Approve`` selection and the steps 10 and 11 can be skipped. The Pull Request is marked as ``approved``. 9) If the Pull Request fullfils all expectations, the Pull Request will be approved by the reviewer via ``Approve`` selection and the steps 10 and 11 can be skipped. The Pull Request is marked as ``approved``.
10) The Pull Request does not fullfil all expectations and review comments needs to be added to the specific lines of code in the target repository of the specific service. After all comments are placed, the review of the Pull Request must be finished with ``Request changes`` selection instead of ``Approve``. 10) The Pull Request does not fullfil all expectations and review comments needs to be added to the specific lines of code in the target repository of the specific service. After all comments are placed, the review of the Pull Request must be finished with ``Request changes`` selection instead of ``Approve``.
11) Huawei collects comments and prepare new documentation change or reply to the comments. They update existing Pull Request with new commit on docs/doc-exports repository. 11) Huawei collects comments and prepare new documentation change or reply to the comments. There are two possible options to go further:
a. Huawei member uses the comments to prepare a new documentation delivery from the beginning (out of Huawei documentation system). The whole process starts from the beginning.
b. Changes are made directly in the Pull Request. The changes are tracked by the Huawei employee and changed in the Huawei documentation system afterwards.
12) After the review has been approved, the Squads product owner or a privileged squad member can add the ``gate`` label to the Pull Request. 12) After the review has been approved, the Squads product owner or a privileged squad member can add the ``gate`` label to the Pull Request.
13) The ``gate`` label triggers another CI/CD pipeline of Zuul to render the final PreProd documentation on https://docs-int.otc-service.com/. 13) The ``gate`` label triggers another CI/CD pipeline of Zuul to render the final PreProd documentation on https://docs-int.otc-service.com/.

View File

@ -6,7 +6,7 @@
{%- if theme_sidebar_mode == 'toc' %} {%- if theme_sidebar_mode == 'toc' %}
{{ toc }} {{ toc }}
{%- elif theme_sidebar_mode == 'toctree' %} {%- elif theme_sidebar_mode == 'toctree' %}
{{ toctree(maxdepth=3, includehidden=True, collapse=False, titles_only=True) }} {{ toctree(maxdepth=2,includehidden=True, collapse=False) }}
{%- endif %} {%- endif %}
</div> </div>
{%- endif %} {%- endif %}