Skip to content

Docs: No "latest" path in our doc #367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ijemmy opened this issue Dec 29, 2021 · 1 comment
Closed

Docs: No "latest" path in our doc #367

ijemmy opened this issue Dec 29, 2021 · 1 comment
Assignees
@ijemmy
Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Milestone
production-ready-...

Comments

@ijemmy
Copy link
Contributor

ijemmy commented Dec 29, 2021 •
edited
Loading

Description of the improvement

Summary of the proposal
When entering the root of documentation (http://awslabs.github.io/aws-lambda-powertools-typescript), it should be redirected to the alias "latest", just like in the Python version doc.

image

However, the current version redirects twice:

  1. First to /latest
  2. Immediately redirect from /latest to the actual version /0.2.0-beta.10.

image

We should make this behavior the same as the one in Python doc.
@ijemmy ijemmy added the documentation Improvements or additions to documentation label Dec 29, 2021
@ijemmy ijemmy changed the title (docs): No "latest" path in our doc docs: No "latest" path in our doc Dec 29, 2021
@ijemmy ijemmy mentioned this issue Dec 29, 2021
Merged
10 tasks
ijemmy added a commit that referenced this issue Dec 31, 2021
@ijemmy
fix: documentation generation on on-release.yml workflow (#368)
bb887fa 
* Limit concurrency of "publish" job to just one to avoid concurrency issue (Issue: #365)
* Generate "latest" alias doc instead of just redirect to the latest version (Issue: #367)
* Generate main version
@ijemmy ijemmy closed this as completed Dec 31, 2021
@github-actions
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@dreamorosi dreamorosi added this to the production-ready-release milestone Feb 28, 2022
@dreamorosi dreamorosi changed the title docs: No "latest" path in our doc Docs: No "latest" path in our doc Nov 14, 2022
@dreamorosi dreamorosi added completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ijemmy ijemmy

Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
None yet
Milestone
production-ready-release
Development

No branches or pull requests
2 participants
@ijemmy @dreamorosi