Added HTML tables to documentation page to improve UX. #514
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.
Motivation
To create a patch to help resolve this change request: #436
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Tested by re-running server to confirm page is still rendered properly and that the page is still being correctly served. I then ran 'yarn test' and that passed all test cases.
Related PRs
#508
Tests
All Yarn tests passed locally up to most recent commit
Change Impact Analysis
For #436, only Markdown code was changed to support HTML5 table elements, and some basic CSS3 styling. No other components were modified or changed.
Do any existing requirements in the baseline conflict with the proposed change?
No.
Do any other pending requirements changes conflict with the proposed change?
No.
What are the business or technical consequences of not making a change?
A less ideal UX (user experience).
Will the proposed change adversely affect performance requirements or other quality attributes?
No, for this change there will be 0 impact to performance requirements. Quality of code remains the same.
Is the proposed change feasible within known technical constraints and current staff skills?
Yes.
Will the proposed change place unacceptable demands on any computer resources required for the development, test, or operating environments?
No, computer resources should stay the same.
Must any tools be acquired to implement and test the change?
Contributors may use the built-in test suite to test the change using command yarn test
How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the project plan?
No dependencies needed to be changed and no new dependencies needed to be added in order to implement this change.
Will prototyping or other use input be required to verify the proposed change?
Yes, the user may request the page that's been modified /en/docs/... and check that the changes have been rendered correctly.
How much effort that has already been invested in the project will be lost if this change is accepted?
Maybe an hour.
Will the proposed change cause an increase in product unit cost, such as by increasing third-party product licensing fees?
No.
Will the change affect any marketing, manufacturing, training, or customer support plans?
No.