<commit_before># The M.A.G.E.S. CMS
This is "The M.A.G.E.S. CMS". I created long time ago in 2011, for now the project is more or less stable and I worked in SVN all my time, so decided to make the switch.  

Currently I'm trying to make workable through composer as I spent hours and days trying to think of a way to make easy updates.
The M.A.G.E.S. CMS is my hobby mostly and I just found many existing CMS too bulky or hard to understand, I don't think that my CMS is some kind of solution for this, but for me it's more or less understandable obviously because I wrote it. Since the beggining I always tried to understand "how it works" and not just take created huge library, use part of it without deep knowledge.  

It's 2015 and I still spending time on this CMS and improve it whenever I have time and motivation to do so. But mostly it's right now my "sand-box" where I implement new features that I'm interested in. I wrote bunch of plugins for this CMS while working as a freelancers on bunch of projects for 3 years. But for now, while The M.A.G.E.S. CMS is another "unknown CMS" I don't intend to make it super-pretty highly modular.  

If you find this project interesting I wouldn't mind you to join and contribute or just give ideas what could be made to make it better.

## Where is master branch?
Because I'm working alone and there are no contributions (yet?) there is no need for bunch of branches. Plus tagging is the most important part as installation update goes through composer.
<commit_msg>Update readme. Discontinuing development.<commit_after># Project discontinued
UPDATE: I stopped working on this project in favor of WordPress / Craft CMS. There are no development anymore.
Support will be provided until 1st September 2017.

# The M.A.G.E.S. CMS
This is "The M.A.G.E.S. CMS". I created long time ago in 2011, for now the project is more or less stable and I worked in SVN all my time, so decided to make the switch.  

Currently I'm trying to make workable through composer as I spent hours and days trying to think of a way to make easy updates.
The M.A.G.E.S. CMS is my hobby mostly and I just found many existing CMS too bulky or hard to understand, I don't think that my CMS is some kind of solution for this, but for me it's more or less understandable obviously because I wrote it. Since the beggining I always tried to understand "how it works" and not just take created huge library, use part of it without deep knowledge.  

It's 2015 and I still spending time on this CMS and improve it whenever I have time and motivation to do so. But mostly it's right now my "sand-box" where I implement new features that I'm interested in. I wrote bunch of plugins for this CMS while working as a freelancers on bunch of projects for 3 years. But for now, while The M.A.G.E.S. CMS is another "unknown CMS" I don't intend to make it super-pretty highly modular.  

If you find this project interesting I wouldn't mind you to join and contribute or just give ideas what could be made to make it better.

## Where is master branch?
Because I'm working alone and there are no contributions (yet?) there is no need for bunch of branches. Plus tagging is the most important part as installation update goes through composer.

{'fraction_non_alphanumeric': 0.04366543665436654, 'fraction_numerical': 0.007072570725707257, 'mean_word_length': 3.805022156573117, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, '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': '2415434', 'n_tokens_mistral': 885, 'n_tokens_neox': 802, 'n_words': 577}