[
https://issues.apache.org/jira/browse/BEAM-12777?focusedWorklogId=701680&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-701680
]
ASF GitHub Bot logged work on BEAM-12777:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Dec/21 20:13
Start Date: 28/Dec/21 20:13
Worklog Time Spent: 10m
Work Description: roger-mike commented on pull request #16327:
URL: https://github.com/apache/beam/pull/16327#issuecomment-1002265594
Hi @aaltay, I tested these changes in a
[fork](https://github.com/roger-mike/beam-site/tree/updates_release_2.99.0) of
`beam-site`. I simulated a release (2.99.0) and pushed the pydocs and javadocs
to the usual place but also to a `current` folder but I'm not sure what are the
next steps to apply these changes to `https://beam.apache.org/releases/`.
Could you give me some pointers on this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@beam.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 701680)
Time Spent: 2h 50m (was: 2h 40m)
> Stable URL for "current" API Documentation
> ------------------------------------------
>
> Key: BEAM-12777
> URL: https://issues.apache.org/jira/browse/BEAM-12777
> Project: Beam
> Issue Type: Improvement
> Components: website
> Reporter: Ahmet Altay
> Assignee: Mike Hernandez
> Priority: P2
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Discussion:
> https://lists.apache.org/thread.html/rc23610839204f2bba1ea148885ef9f496a3087a47d7bb25662a46bc5%40%3Cdev.beam.apache.org%3E
> Summary of the proposal:
> """
> You may have noticed that our API Documentation could really use some SEO.
> It's possible to search for Beam APIs (e.g. "beam dataframe read_csv" [1] or
> "beam java ParquetIO" [2]) and you will be directed to some documentation,
> but it almost always takes you to an old version. I think this could be
> significantly improved if we just make one change: rather than making
> https://beam.apache.org/releases/javadoc/current redirect to the latest
> release, we should just always stage the latest documentation there.
> To be clear I'm not 100% sure this will help. I haven't talked to any search
> engineers or SEO experts about it. I'm just looking at other projects as a
> point of reference. I've found that I never have trouble finding the latest
> pandas documentation (e.g. "pandas read_csv" [3]) since it always directs to
> "pandas-docs/stable/" rather than a particular version number.
> We should also make sure the version number shows up in the page title, it
> looks like this isn't the case for Python right now.
> """
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
