[freetype2] master a4f3e858a 1/2: docs/freetype-web.txt: New file.

[Werner Lemberg]

branch: master
commit a4f3e858ae70570971b91c0d8093a1de4562c2b4
Author: Anurag Thakur <anuthadev@gmail.com>
Commit: Werner Lemberg <wl@gnu.org>

    docs/freetype-web.txt: New file.
---
 docs/freetype-web.txt | 42 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/docs/freetype-web.txt b/docs/freetype-web.txt
new file mode 100644
index 000000000..03058fae1
--- /dev/null
+++ b/docs/freetype-web.txt
@@ -0,0 +1,42 @@
+How to update the FreeType web pages
+------------------------------------
+
+The 'freetype.org' website is hosted via the 'freetype-web' repo
+located at
+
+   https://gitlab.com/freetype/freetype-web  ,
+
+which in turn is a mirror from the master 'freetype-web' repository
+located at
+
+  https://gitlab.freedesktop.org/freetype/freetype-web  .
+
+Due to Cloudflare caching, changes take time to appear on
+'freetype.org', so visit
+
+  https://freetype.gitlab.io/freetype-web
+
+for instant feedback.
+
+All the commits should *only* be done to the 'freetype-web' repo at
+
+  https://gitlab.freedesktop.org/freetype/freetype-web
+
+When a commit is done to this repo, the CI pipeline runs and the
+website is deployed via gitlab pages at
+
+  https://freetype.pages.freedesktop.org/freetype-web  .
+
+The pull mirror automatically updates the repository in 'gitlab.com',
+and the CI pipeline deploys the website at:
+
+  https://freetype.gitlab.io/freetype-web
+
+Since the 'freetype.org' website uses Cloudflare caching, it will take
+a while for the changes to show up in 'freetype.org'.
+
+If you have access to the Cloudflare dashbouard you can purge the
+cache from there; this will cause the cache to be fetched again
+resulting in the website being updated instantly.
+
+--- end of freetype-web.txt ---