Refactoring files to make a distinction between EMT and Azure docs

[sgolebiewski-intel]

Merge Checklist

All boxes should be checked before merging the PR

• [] The changes in the PR have been built and tested
• [] cgmanifest file has been updated if required
• [] Ready to merge

Description

Adding the emt- prefix to all documentation files to introduce a distinction between EMT docs and Azure docs.

Note:

• Changes need to be tested to verify the impact on the publishing process. It regards both the documentation website and the pages on Edge Microvisor Toolkit found in Edge Software Catalog.
• To make a clearer distinction, the docs folder could also be prefixed with emt- , however such change would definitely impact the CI builds, so according changes should be implemented there as well.

[magerstam]

@sgolebiewski-intel sorry this has been hanging here for a while. Can you please resolve the conflicts and push the commits and we'll try to get this merged asap.

[kblaszczak-intel]

@magerstam @sgolebiewski-intel
I just need to restate: mind you, this will change the URLs of the pages :) There is some "risk" involved.

[sgolebiewski-intel]

@magerstam @sgolebiewski-intel I just need to restate: mind you, this will change the URLs of the pages :) There is some "risk" involved.

Exactly. The existing links to published docs will stop working.
We could consider inline annotations within articles.

[magerstam]

Ok, can we try to mitigate that risk and ensure the published docs will continue working? How frequently are we runnign the publish docs workflow? It doesn't seem like is automatic with a trigger whenever there has been a change to the /docs folder

[kblaszczak-intel]

Ok, can we try to mitigate that risk and ensure the published docs will continue working? How frequently are we runnign the publish docs workflow? It doesn't seem like is automatic with a trigger whenever there has been a change to the /docs folder

I doubt it will impact documentation experience on GitHub much. On the other hand, we don't have many options at the moment to prevent breaking existing links - we could create a set of redirecting html documents if we could push them directly to the server. Creating them in the repo would be counterproductive. I'm just not sure if the html redirects wouldn't be removed with the next update. We still don't know enough about the entire publishing setup.

[magerstam]

What are the next steps to get this closed? Are we merging the changes and as a second step fixing links (assuming this is from the published documentation) to correctly point to the EMT documentation?

[kblaszczak-intel]

What are the next steps to get this closed? Are we merging the changes and as a second step fixing links (assuming this is from the published documentation) to correctly point to the EMT documentation?

Since this is a direct product requirement, let's just merge it.
Hopefully, the page has not been bookmarked extensively. And when we set up a central build, then we can decide how to proceed (we may remove the prefix as part of the build process, getting the distinctive files in Git Hub and normal URLs in html).

[anujm1]

@sgolebiewski-intel can you please rebase

[anujm1]

@sgolebiewski-intel can you please pick this for -dev branch as well?