struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yasser Zamani <>
Subject RE: Migrating the Migration Guide
Date Sat, 21 Sep 2019 09:25:45 GMT

Sorry I cannot recall why we should migrate -- Have INFRA compelled us and Confulence is going
to be removed? Or just to beautify?

Anyway, I think we can use a Jekyll/Ruby custom tag component which at site build time, downloads
that Confulence's page html as an anonymous user and includes it in output -- like what I've
already done for some snippets.


>-----Original Message-----
>From: Lukasz Lenart <>
>Sent: Friday, September 20, 2019 11:20 AM
>To: Struts Users Mailing List <>
>Subject: Migrating the Migration Guide
>The very last thing to migrate from Confluence to Markdown is our Migration
>Guide [1]. The only problem with having all in .md files and exposed via Git is that
>with Confluence we can restrict access to particular pages which is useful when
>we are preparing a security release. We can prepare the Version Notes without
>exposing any information to public, clarify things and so on. Having all in .md files
>won't be possible to do so.
>I wonder what can of flow would help us still use Confluence in such cases but
>keep the final docs in .md files, do you have some ideas?
>+ 48 606 323 122
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:
View raw message