docs: update logo and links

docs/source/_templates/indexsidebar.html

 <h3>Other resources</h3>
 <ul>
   <li><a href="https://woob.tech/">Official website</a></li>
-  <li><a href="https://git.woob.tech/woob/woob/issues">Bug Tracker</a></li>
-  <li><a href="https://git.woob.tech/woob/woob/-/tags">Download stable version</a></li>
+  <li><a href="https://gitlab.com/woob/woob/issues">Bug Tracker</a></li>
+  <li><a href="https://gitlab.com/woob/woob/-/tags">Download stable version</a></li>
 </ul>

docs/source/conf.py

@@ -120,7 +120,7 @@
 # The name of an image file (within the static path) to use as favicon of the
 # docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
 # pixels large.
-html_favicon = '_static/favicon.ico'
+html_favicon = '_static/favicon.png'
 
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,

docs/source/guides/contribute.rst

@@ -9,7 +9,7 @@ Write a patch
 
 Help yourself with the `documentation <http://docs.woob.tech/>`_.
 
-Find an opened issue on `this website <https://git.woob.tech/woob/woob/issues>`_, or write your own bugfix or feature.
+Find an opened issue on `this website <https://gitlab.com/woob/woob/issues>`_, or write your own bugfix or feature.
 Then, once it is necessary, commit with::
 
     $ git commit -a
@@ -31,12 +31,12 @@ To aid in verifying Python 3 compatibility, also run::
     $ tools/run_tests.sh -3 yourmodulename
 
 Perhaps you should also write or fix tests. These tests are automatically run by
-`Gitlab CI <https://git.woob.tech/woob/woob/pipelines>`_ at each commit and merge requests.
+`Gitlab CI <https://gitlab.com/woob/woob/pipelines>`_ at each commit and merge requests.
 
 Create a merge request or send a patch
 --------------------------------------
 
-The easiest way to send your patch is to create a fork on `the woob gitlab <https://git.woob.tech>`_ and create a merge
+The easiest way to send your patch is to create a fork on `the woob gitlab <https://gitlab.com>`_ and create a merge
 request from there. This way, the code review process is easier and continuous integration is run automatically (see
 previous section).
 
@@ -45,11 +45,11 @@ previous section).
     Using the ``git+ssh`` protocol to clone the repository will only work when connected from an
     IPv6 compatible network:
 
-    `$ git clone gitlab@git.woob.tech:woob/woob.git`
+    `$ git clone gitlab@gitlab.com:woob/woob.git`
 
     But it is possible to use the ``git+https`` protocol from everywhere (IPv4 and IPv6 networks):
 
-    `$ git clone https://git.woob.tech/woob/woob.git`
+    `$ git clone https://gitlab.com/woob/woob.git`
 
 If you prefer good old email patches, just use
 

docs/source/guides/setup.rst

@@ -8,7 +8,7 @@ Git installation
 
 Clone a git repository with this command::
 
-    $ git clone https://git.woob.tech/woob/woob.git
+    $ git clone https://gitlab.com/woob/woob.git
 
 We don't want to install woob on the whole system, so we create local directories where
 we will put symbolic links to sources::

docs/source/guides/tests.rst

@@ -21,7 +21,7 @@ Then, it run every method which name starts with ``test_``.
 
 .. note::
     Some environment variables are available, to use specific backend file or send the test results. Refer to `the
-    comments in the script <https://git.woob.tech/weboob/weboob/blob/master/tools/run_tests.sh#L4-8>`_ for more infos on this.
+    comments in the script <https://gitlab.com/weboob/weboob/blob/master/tools/run_tests.sh#L4-8>`_ for more infos on this.
 
 If a module name is passed as argument, only this module will be tested. For example, to only run ``lutim`` tests::