Hi Dave,
Hi Andrew,
No worries, we're still gathering input from the communities.
Based on feedback received so far (including yours), I think a
hybrid approach is most likely to be best, where project specific
wiki entries are migrated to the project repo wiki and using the
LFN Confluence wiki for the main page and ancillary wiki pages
(e.g. TSC).
This absolutely makes sense ! I saw the existing confluence pages were mostly admin, so grouping them together will reduce the cognitive burden for that mode of editing.
Vanessa and I will be doing some testing using the
fdio/.github/wiki to try and figure out how to automate the
migration and see what works best to avoid a bazillion URL
redirects. We will also be putting together a short migration
document to specify the detailed plan for migration. We will
publish it to get comments from the communities once it is
available.
Is there a way to export the data from the wiki in bulk, with some way to mechanically reconstruct the original wiki url ? Then one could build a static website with redirects only (trivial to do in _javascript_), and push the rest of the contents into their places…
Casey Cain has also pointed out that there are tools in Confluence
to load content into the wiki from github repo's, so we'll figure
out if that would allow both interfaces to be used to render the
same wiki data.
This might work pretty well, if it exists!
—a
Thanks,
-daw-
On 2/19/26 6:37 AM, Andrew 👽
Yourtchenko wrote:
Hi Dave,
I've missed your original email, sorry for the late reply!
I had a look at the Confluence wiki and clicked around it
- it seems at least right now it is used to host mostly
administrative content; and looking at it, the interface
doesn't appear to add much compared to using github, do we
have the idea of what are the pros/cons of having an extra
dependency vs. having it on github in one place ?
To me intuitively having it on github would be less
cognitive load, and easier to manage (since, after all, this
is just another git repo, which I presume can be rendered into
static pages using some static site generator ?) - and if it
is static pages, there can be nonzero cost savings in terms of
hosting costs.
--a
|
