This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tapestry-5-site.git
The following commit(s) were added to refs/heads/main by this push:
new c29a975 Update README for this repo's new home at ASF
c29a975 is described below
commit c29a975a82156b6a8e850314cfa7163a8c63b47a
Author: Volker Lamp <[email protected]>
AuthorDate: Tue May 5 18:15:04 2026 +0200
Update README for this repo's new home at ASF
---
README.md | 30 ++++++++----------------------
1 file changed, 8 insertions(+), 22 deletions(-)
diff --git a/README.md b/README.md
index 54f01da..d7563c9 100644
--- a/README.md
+++ b/README.md
@@ -1,28 +1,14 @@
-# tapestry-antora-site-poc-content
+# tapestry-5-site.git
## About
-Proof of concept of how the Tapestry website and documentation could be based
on Antora.
-Intended for futher discussion with the Tapestry team.
+This is the home of the source files of the Apache Tapestry website.
+The content is mostly written in [AsciiDoc](https://asciidoc.org/) and is
organized in a way the [Antora](https://antora.org) site generator likes it.
+The build logic is in another repo, see
[tapestry-5-site-builder.git](https://gitbox.apache.org/repos/asf/tapestry-5-site-builder.git).
-This repo exclusively contains the website and documentation sources.
-See the
[tapestry-antora-site-poc-builder](https://github.com/vjlamp/tapestry-antora-site-poc-builder)
repo for how Antora is configured to build a static website from these sources.
-
-## Why isn't this hosted in an official Apache repo?
-We may convert it into one eventually.
-To get started, this personal repo was a quick and easy for me to have a
shared repo - essential for the intended Antora setup.
-
-## Migration Strategy
-Currently, the Tapestry website is generated from a Confluence Wiki hosted by
the Apache Software Foundation.
-In contrast, Antora works with Asciidoc sources.
-The strategy is to migrate the content manually.
-1. Copy the content from the current Tapestry website and paste it into the
corresponding Asciidoc page.
-2. Enhance the source by recreating (i.e. adding missing) typography and by
adding `javadoc:` and `issue:` macros where appropriate.
-3. Copy the Asciidoc page to the version branches.
-4. For each version branch, remove content no longer, or not yet, relevant for
that branch.
-
-Using automated scripts to convert Confluence sources to Asciidoc sources
could be of some use. However, the larger part of the work is to split up the
version-specific parts across the branches. Probably not worth the time to
develop scripts for that.
+## Original Content
+Most of the content up to version 5.9 was migrated from the ASF Confluence
wiki which has served the project well for many years.
## Contributing
-This is hosted on GitHub so please feel invited to send **pull requests**.
-If you would, please follow the [One sentence per
line](https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line)
principle.
+Yes, please! This repo is also hosted on GitHub so please feel invited to send
a **pull request**.
+When authoring content please follow the [One sentence per
line](https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line)
principle.
