New chapter for continuous translation

docs/admin/admin.rst

@@ -4,119 +4,6 @@ Administration
 Administration of Weblate is done through standard Django admin interface,
 which is available under :file:`/admin/` URL.
 
-Updating repositories
----------------------
-
-You should set up some way how backend repositories are updated from their
-source. You can either use hooks (see :ref:`hooks`) or just regularly run
-:djadmin:`updategit --all`.
-
-With Gettext po files, you might be often bitten by conflict in PO file
-headers. To avoid it, you can use shipped merge driver
-(:file:`examples/git-merge-gettext-po`). To use it just put following
-configuration to your :file:`.gitconfig`:
-
-.. code-block:: ini
-
-   [merge "merge-gettext-po"]
-     name = merge driver for gettext po files
-     driver = /path/to/weblate/examples/git-merge-gettext-po %O %A %B
-
-And enable it's use by defining proper attributes in given repository (eg. in
-:file:`.git/info/attribute`)::
-
-    *.po merge=merge-gettext-po
-
-.. note::
-
-    This merge driver assumes the changes in POT files always are done in branch
-    we're trying to merge.
-
-.. seealso:: http://www.no-ack.org/2010/12/writing-git-merge-driver-for-po-files.html
-
-.. _push-changes:
-
-Pushing changes
----------------
-
-Each project can have configured push URL and in such case Weblate offers
-button to push changes to remote repository in web interface.
-
-I case you will use SSH for pushing, you need to have key without passphrase
-(or use ssh-agent for Django) and the remote server needs to be verified by you
-first, otherwise push will fail.
-
-.. note::
-
-   You can also enable automatic pushing changes on commit, this can be done in
-   project configuration.
-
-.. seealso:: :ref:`private` for setting up SSH keys
-
-.. _merge-rebase:
-
-Merge or rebase
----------------
-
-By default Weblate merges upstream repository into it's own. This is safest way
-in case you also access underlying repository by other means. In case you don't
-need this, you can enable rebasing of changes on upstream, what will produce
-history with less merge commits.
-
-.. note::
-
-    Rebasing can cause you troubles in case of complicated merges, so carefully 
-    consider whether you want to enable them or not.
-
-Interacting with others
------------------------
-
-Weblate makes it easy to interact with others using it's API.
-
-.. seealso:: :ref:`api`
-
-.. _processing:
-
-Pre commit processing of translations
--------------------------------------
-
-In many cases you might want to automatically do some changes to translation
-before it is committed to the repository. The pre commit script is exactly the
-place to achieve this.
-
-Before using any scripts, you need to list them in
-:setting:`PRE_COMMIT_SCRIPTS` configuration variable. Then you can enable them
-at :ref:`subproject` configuration as :guilabel:`Pre commit script`.
-
-The hook script is executed using system() call, so it is evaluated in a shell.
-It is passed single parameter consisting of file name of current translation.
-
-The script can also generate additional file to be included in the commit. This
-can be configured as :guilabel:`Extra commit file` at :ref:`subproject`
-configuration. You can use following format strings in the filename:
-
-``%(language)s``
-    Language code
-
-Example - generating mo files in repository
-+++++++++++++++++++++++++++++++++++++++++++
-
-Allow usage of the hook in the configuration
-
-.. code-block:: python
-
-    PRE_COMMIT_SCRIPTS = (
-        '/usr/share/weblate/examples/hook-generate-mo',
-    )
-
-To enable it, choose now :guilabel:`hook-generate-mo` as :guilabel:`Pre commit
-script`. You will also want to add path to generated files to be included in
-Git commit, for example ``po/%(language)s.mo`` as :guilabel:`Extra commit file`.
-
-
-You can find more example scripts in ``examples`` folder within Weblate sources,
-their name start with ``hook-``.
-
 .. _voting:
 
 Suggestion voting

docs/admin/continuous.rst

+Continuous translation
+======================
+
+Weblate provides you great infrastructure for translation to closely follow
+your development. This way translators can work on translations whole time and
+are not forced to translate huge amount of new texts before release.
+
+Updating repositories
+---------------------
+
+You should set up some way how backend repositories are updated from their
+source. You can either use hooks (see :ref:`hooks`) or just regularly run
+:djadmin:`updategit --all`.
+
+With Gettext po files, you might be often bitten by conflict in PO file
+headers. To avoid it, you can use shipped merge driver
+(:file:`examples/git-merge-gettext-po`). To use it just put following
+configuration to your :file:`.gitconfig`:
+
+.. code-block:: ini
+
+   [merge "merge-gettext-po"]
+     name = merge driver for gettext po files
+     driver = /path/to/weblate/examples/git-merge-gettext-po %O %A %B
+
+And enable it's use by defining proper attributes in given repository (eg. in
+:file:`.git/info/attribute`)::
+
+    *.po merge=merge-gettext-po
+
+.. note::
+
+    This merge driver assumes the changes in POT files always are done in branch
+    we're trying to merge.
+
+.. seealso:: http://www.no-ack.org/2010/12/writing-git-merge-driver-for-po-files.html
+
+.. _push-changes:
+
+Pushing changes
+---------------
+
+Each project can have configured push URL and in such case Weblate offers
+button to push changes to remote repository in web interface.
+
+I case you will use SSH for pushing, you need to have key without passphrase
+(or use ssh-agent for Django) and the remote server needs to be verified by you
+first, otherwise push will fail.
+
+.. note::
+
+   You can also enable automatic pushing changes on commit, this can be done in
+   project configuration.
+
+.. seealso:: :ref:`private` for setting up SSH keys
+
+.. _merge-rebase:
+
+Merge or rebase
+---------------
+
+By default Weblate merges upstream repository into it's own. This is safest way
+in case you also access underlying repository by other means. In case you don't
+need this, you can enable rebasing of changes on upstream, what will produce
+history with less merge commits.
+
+.. note::
+
+    Rebasing can cause you troubles in case of complicated merges, so carefully 
+    consider whether you want to enable them or not.
+
+Interacting with others
+-----------------------
+
+Weblate makes it easy to interact with others using it's API.
+
+.. seealso:: :ref:`api`
+
+.. _processing:
+
+Pre commit processing of translations
+-------------------------------------
+
+In many cases you might want to automatically do some changes to translation
+before it is committed to the repository. The pre commit script is exactly the
+place to achieve this.
+
+Before using any scripts, you need to list them in
+:setting:`PRE_COMMIT_SCRIPTS` configuration variable. Then you can enable them
+at :ref:`subproject` configuration as :guilabel:`Pre commit script`.
+
+The hook script is executed using system() call, so it is evaluated in a shell.
+It is passed single parameter consisting of file name of current translation.
+
+The script can also generate additional file to be included in the commit. This
+can be configured as :guilabel:`Extra commit file` at :ref:`subproject`
+configuration. You can use following format strings in the filename:
+
+``%(language)s``
+    Language code
+
+Example - generating mo files in repository
++++++++++++++++++++++++++++++++++++++++++++
+
+Allow usage of the hook in the configuration
+
+.. code-block:: python
+
+    PRE_COMMIT_SCRIPTS = (
+        '/usr/share/weblate/examples/hook-generate-mo',
+    )
+
+To enable it, choose now :guilabel:`hook-generate-mo` as :guilabel:`Pre commit
+script`. You will also want to add path to generated files to be included in
+Git commit, for example ``po/%(language)s.mo`` as :guilabel:`Extra commit file`.
+
+
+You can find more example scripts in ``examples`` folder within Weblate sources,
+their name start with ``hook-``.

docs/admin/index.rst

@@ -8,6 +8,7 @@ Administrators guide
     upgrade
     auth
     projects
+    continuous
     checks
     machine
     admin