Documentation source

[iliakur]

Hi!

I can't seem to be able to find the source for the documentation neither in this repo, nor in the organization. We started using the library at work and I have come across some points that I think would make sense to add in the documentation. I think they have been addressed recently, but for the future I'd like to know where I can add stuff I come across.

Thanks for your time!

[AngledLuffa]

gh-pages branch

…

On Tue, Dec 7, 2021 at 5:51 AM Ilia Kurenkov ***@***.***> wrote: Hi! I can't seem to be able to find the source for the documentation <https://stanfordnlp.github.io/stanza/> neither in this repo, nor in the organization. We started using the library at work and I have come across some points that I think would make sense to add in the documentation. I think they have been addressed with a recent, but for the future I'd like to know where I can add stuff I come across. Thanks for your time! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#892>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2AYWLCQSLD4WT5MZU75KDUPYGMZANCNFSM5JRJYJVQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[iliakur]

Thanks!

[iliakur]

Oh, hmm, does this mean however, that there's no way to see the documentation for older versions of Stanza?

[AngledLuffa]

Hmm, that is a good point. It's still available in git, of course. In general we try to not make backwards-incompatible API changes, although it does occasionally happen, and there's really very little reason to use an old version. Going forward, perhaps I could archive older versions of the documentation.

…

On Wed, Feb 16, 2022 at 7:42 AM Ilia Kurenkov ***@***.***> wrote: Oh, hmm, does this mean however, that there's no way to see the documentation for older versions of Stanza? — Reply to this email directly, view it on GitHub <#892 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2AYWNJOGDKFTCCFTSFRBTU3PAX3ANCNFSM5JRJYJVQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[iliakur]

You'd be surprised how easy it is in a multi-team environment to get bogged down in an older version. I applaud the aggressive backwards-compatibility policy!

I would really appreciate archives or commit names in the gh-pages branch that communicate version transitions. I guess tags could also achieve a similar thing, though that means you'd have basically duplicated tags for releases.

One other possibility is to store the docs with the source code and only push them to the gh-pages branch at release time.