<commit_before>uSync 
=
![Build Status](https://jumoo.visualstudio.com/_apis/public/build/definitions/e5bc8d11-6d47-4620-9e6e-dd8199b2843e/6/badge)

**Documentation : http://usync.readthedocs.io/**

uSync is a synchronization tool for the Umbraco CMS. It serializes the database config and data
within an Umbraco site, and reads and writes it to disk as a collection of XML files. 

uSync can be used as part of your source control, continuous deployment or site synchronisation plans. 

Out of the box, uSync reads and writes all the database elements to and from the `usync/data` folder.
It will save:

* Document Types
* DataTypes
* MediaTypes
* Templates
* Macros
* Languages
* Dictionary Items
* MemberTypes

You can use **uSync.ContentEdition** to manage content and media if you also want to write them to disk.

The basics workings of uSync
-
The main elements of uSync are the Serializers and Handlers:

### Serializers
Serializers manage the transition between Umbraco and the XML that uSync uses,
they control how the configuration is written in and out, manage things like 
internal IDs so your settings can move between Umbraco installations. 

Serializers do the heavy lifting of usync, and live in the uSync.Core package, 
you can use this package to programmatically import and export data to Umbraco. 

### Handlers
Handlers manage the storing of the XML and passing to the serializers. By default
this means reading and writing the XML to disk from the uSync folder. Handlers 
are the entry point for imports and exports, and they capture the save and delete
events inside of Umbraco so that things are saved to disk when you make changes via
the back office. 

You can add your own handlers by implementing the `ISyncHandler` interface.

### Mappers 
Mappers help with the content and media serialization process, they 
allow uSync to know how to find and map internal ids from within properties on your 
content. 
Within Umbraco when you use links, and things like content pickers store the internal
id to link the property to the correct content. Between Umbraco installations these
ids can change so uSync needs to find them and map them to something more global (often GUIDs).

Mappers allow uSync to do this. as of v3.1 uSync.ContentEdition includes mappers for: 
* Built in editors *(RTE/Multi-Node TreePicker, Content picker, etc)*
* The Grid
* Archetype
* Nested Content
* Vorto
* LeBlender
* DocTypeGridEditor
<commit_msg>README updates<commit_after>uSync 
=
![Build Status](https://jumoo.visualstudio.com/_apis/public/build/definitions/e5bc8d11-6d47-4620-9e6e-dd8199b2843e/6/badge)

**Documentation : http://usync.readthedocs.io/**

uSync is a synchronization tool for the Umbraco CMS. It serializes the database config and data
within an Umbraco site, and reads and writes it to disk as a collection of XML files. 

uSync can be used as part of your source control, continuous deployment or site synchronisation plans. 

Out of the box, uSync reads and writes all the database elements to and from the `usync/data` folder.
It will save:

* Document Types
* DataTypes
* MediaTypes
* Templates
* Macros
* Languages
* Dictionary Items
* MemberTypes

You can use **uSync.ContentEdition** to manage content and media if you also want to write them to disk.

The basics workings of uSync
-
The main elements of uSync are the Serializers and Handlers:

### Serializers
Serializers manage the transition between Umbraco and the XML that uSync uses,
they control how the configuration is written in and out, manage things like 
internal IDs so your settings can move between Umbraco installations. 

Serializers do the heavy lifting of uSync, and live in the uSync.Core package, 
you can use this package to programmatically import and export data to Umbraco. 

### Handlers
Handlers manage the storing of the XML and passing to the serializers. By default
this means reading and writing the XML to disk from the uSync folder. Handlers 
are the entry point for imports and exports, and they capture the save and delete
events inside of Umbraco so that things are saved to disk when you make changes via
the back office. 

You can add your own handlers by implementing the `ISyncHandler` interface.

### Mappers 
Mappers help with the content and media serialization process, they 
allow uSync to know how to find and map internal ids from within properties on your 
content. 
Within Umbraco when you use links, and things like content pickers store the internal
id to link the property to the correct content. Between Umbraco installations these
ids can change so uSync needs to find them and map them to something more global (often GUIDs).

Mappers allow uSync to do this. as of v3.1 uSync.ContentEdition includes mappers for: 
* Built in editors *(RTE/Multi-Node TreePicker, Content picker, etc)*
* The Grid
* Archetype
* Nested Content
* Vorto
* LeBlender
* DocTypeGridEditor

{'fraction_non_alphanumeric': 0.045704958171801674, 'fraction_numerical': 0.009793919608243216, 'mean_word_length': 4.470982142857143, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6732895', 'n_tokens_mistral': 1373, 'n_tokens_neox': 1322, 'n_words': 713}