Remove documentation on confirming plugins work #132
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes being introduced:
The how-to page on confirming whether all of our various plugins are working is something that the UX group has indicated an interest in helping to maintain, and the testing itself will be followed by both engineers and site builders.
Given this, it makes sense to move this documentation to the service documentation in Confluence.
Relevant ticket(s):
https://mitlibraries.atlassian.net/browse/lm-60
How does this address that need:
This removes the stub page on confirming plugin operation, as the content has been moved to the Confluence space. This isn't a link that needs to be maintained in this way.
(We will eventually want to make sure that this repo links to the Confluence space at some level, but with the service being renamed soon I'm not sure what URLs will be changing in the next few days. We'll need a separate PR soon-ish once that happens)
Document any side effects to this change:
None
Developer
Stylesheets
string incremented.
Secrets
Documentation
Accessibility
our guide and
all issues introduced by these changes have been resolved or opened as new
issues (link to those issues in the Pull Request details above)
Stakeholder approval
Dependencies
NO dependencies are updated
Code Reviewer
(not just this pull request message)