[
https://issues.apache.org/jira/browse/AVRO-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791989#comment-17791989
]
Oscar Westra van Holthe - Kind edited comment on AVRO-3651 at 12/8/23 8:40 AM:
-------------------------------------------------------------------------------
A few notes on our website deployment:
* The main website is hosted via
[subversion|https://svn-master.apache.org/repos/asf/avro/site/publish]
([source|https://infra-reports.apache.org/#sitesource]).
* Publishing was broken, but updates should now be reflected in the website
again (thanks to Daniel Gruno from the ASF infra team)
* We can publish to subdirectory locations via git using a
{{[.asf.yaml|https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features]}}
file (an example is in our own
[asf-site|https://github.com/apache/avro/tree/asf-site] branch)
* Publishing to subdirectories via git does not remove stale locations, to we
have 6 subdirectory locations from 2 branches now. They'll be clobbered by
publishing the main website via git.
was (Author: opwvhk):
A few notes on our website deployment:
* The main website is hosted via
[subversion|https://svn-master.apache.org/repos/asf/avro/site/publish]
([source|https://infra-reports.apache.org/#sitesource]).
* Publishing was broken, but updates should now be reflected in the website
again (thanks to Daniel Gruno from the ASF infra team)
* We can publish to subdirectory locations using a
{{[.asf.yaml|https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features]}}
file (an example is in our own
[asf-site|https://github.com/apache/avro/tree/asf-site] branch)
* Publishing via git does not remove stale locations, to we have 6
subdirectory locations from 2 branches now. They'll be clobbered by publishing
the main website via git.
> [web] Build and separate release-specific pages.
> ------------------------------------------------
>
> Key: AVRO-3651
> URL: https://issues.apache.org/jira/browse/AVRO-3651
> Project: Apache Avro
> Issue Type: Task
> Components: website
> Reporter: Ryan Skraba
> Priority: Major
>
> One of the major complications with the Avro website is maintaining the pages
> for old version. The website documentation is treated as a release artifact
> for the release, which makes sense since the pages are contained in the
> release.
> The Flink community separates the pages that apply to the flink project from
> the pages that apply to a speciific release. They are integrated together to
> navigate easily from release 1.x.0 -> project -> release 1.y.0
> This technique would make it quite a bit easier to deploy the website, and
> allow us to have links to "Edit this page" that can automatically open a PR
> on GitHub.
> Project: [https://flink.apache.org/]
> Release:
> [https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/try-flink/local_installation/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
