Add new licensing page #1756
Add new licensing page #1756
Conversation
|
🎊 PR Preview has been successfully built and deployed to https://localstack-docs-preview-pr-1756.surge.sh 🎊 |
|
Rewrote/refactored the doc and fixed the metadata to improve clarity, structure, and user experience. The original version was hard to read and for readers to find information. This rewrite makes it easier for readers to take action. What Changed:
re: service table formatThe current service table proposed in this PR is unnecessarily long and practically impossible to navigate. It presents the same UX challenges we identified on our AWS API features & coverage docs:
As part of the current work on a new documentation site and information architecture, we’ll need to replace and redesign this table entirely with an improved UX. (likely a searchable, filterable table as we are doing for the aws service pages) IOW, this improvement will come as part of the v2 docs rollout. |
| @@ -0,0 +1,376 @@ | |||
| --- | |||
There was a problem hiding this comment.
Refactored the introduction and improved the metadata to improve clarity, structure, and user experience. The original version was hard to read and for readers to find information.
This rewrite makes it easier for readers to take action.
What Changed:
- Rewrote doc for better readability and logical flow.
- Restructured licensing, usage, and tier information into clearly defined sections.
- Replaced unclear phrasing (legal-jargon-sounding-stuff) with developer-friendly language.
- Clarified the difference between service availability vs. feature coverage level.
- Improved metadata (Title, linkTitle, and Description is more specific, better for search bots)
- Rewrote the Legacy Plans section to improve clarity and present CI credit rules in a more structured, scannable format.
- Clarified continuity terms and emphasized key limits per plan to support easier decision-making for legacy users.
content/en/references/licensing.md
Outdated
|
|
||
| To learn more about how a service behaves in LocalStack, refer to that individual service page or contact Support. | ||
|
|
||
|
|
There was a problem hiding this comment.
re: service table format
The current service table proposed in this PR is unnecessarily long and practically impossible to navigate. It presents the same UX challenges we identified on our AWS API features & coverage docs:
- Excessive vertical scrolling
- Lack of searchability or filtering
- Hard to quickly identify relevant service info
As part of the current work on a new documentation site and information architecture, we’ll need to replace and redesign this table entirely with an improved UX. (likely a searchable, filterable table as we are doing for the aws service pages)
IOW, this improvement will come as part of the v2 docs rollout.
if you are, 
This is a new licensing page supplied by PMM to go with our updated pricing and packaging.