Community Ask: How should we rename/move templates? about azure-quickstart-templates HOT 6 CLOSED

Broken URLs in the GitHub repo are tolerable (history will help people find the new URL). It's a different story for website URLs. Since related here appear on Microsoft.com will we be able to create redirects there?

from azure-quickstart-templates.

I don't see any problem with the proposed method.

From a parctical point of view I always search based on resource types and specific keywords (ie. template functions and/or templateLink).
I pay very little attention to the folder name compared to the readme found based on the search.

from azure-quickstart-templates.

I think the most frustrating thing for me is trying to find open/closed issues / PRs.

Since ALL of the templates are in the same repo, all issues / PRs for any of the templates show up in the same place, even though I might be looking for something specific to just one of the templates.

from azure-quickstart-templates.

@rgardler Yes, we should be able to remap the ACOM template page to the correct folder.

@desek Thanks!

@scottzilla Are you asking trying to find issues/PR that affected a particular template? Have you instead tried to use the git history in the file of the template you want to get more hisotrical information?

from azure-quickstart-templates.

I like the idea to have 101, 201, 301 folders at top level, it would reduce the noise/number of items at the parent level and offer a clear categorization by complexity level. Search is always there to help you find something if needed.

I understand the rename need but we'll need to constantly take a look here to see if the folder(s) we depends on has moved. Can you setup a notification of some sort (RSS or something else) that we could subscribe to? When a rename of a folder is performed, a process would update a file or use another mechanism to trigger a notification that we can consume and be notified as soon as it happen, this way we could be proactive instead of reactive for our dependencies.

I link one template here from my blog and was thinking about doing this more and more in the future. No problem having to go back and update my articles but I need a notification mechanism instead of having to check each day/week if a link I use is broken.

from azure-quickstart-templates.

@slapointe I'm not sure if such a notification mechanism exists. Let me know if you have something in mind and I can investigate. How about if we use the releases tab (https://github.com/Azure/azure-quickstart-templates/releases) on the root of the repo to maintain a table of movement of templates? Something like (Old URL -> New URL).

Ideally, we want the users to use the Azure.com searchable index URLs for bookmarking templates and not have to take a dependency on direct Github folder URLs to avoid these issues.

from azure-quickstart-templates.