<commit_before><?xml version="1.0"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <title>About</title>
</head>
<body>
<h3>About</h3>
<p>
Everything is content management (WCMS/Wiki, DMS, CRM, <a href="http://en.wikipedia.org/wiki/Enterprise_content_management">ECM</a>, ERP, PIM/E-Mail, DRM, ...) and Yanel
is a humble attempt to provide a solution for all your content management needs by offering an Open Source service oriented Content Management Framework written in Java.
</p>
<p>
The Yanel community has defined a set of <a href="../principles.html">principles</a> to sustain long-term development.
</p>
<h3>Download</h3>
<p>
See the <a href="../en/download/index.html">download</a> page for information on releases, snapshots, source code, etc.
</p>
<h3>Main Focus</h3>
<p>
</p><ul>
  <li>Usability<br/></li>
  <li>Maintenance<br/></li>
  
  <li>Integration<br/></li>
  </ul>
</body>
</html><commit_msg>more details added<commit_after><?xml version="1.0"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <title>About</title>
</head>
<body>
<h3>About</h3>
<p>
Everything is content management (WCMS/Wiki, DMS, CRM, <a href="http://en.wikipedia.org/wiki/Enterprise_content_management">ECM</a>, ERP, PIM/E-Mail, DRM, ...) and Yanel
is a humble attempt to provide a solution for all your content management needs by offering an Open Source service oriented Content Management Framework written in Java.
</p>
<p>
The Yanel community has defined a set of <a href="../principles.html">principles</a> to sustain long-term development.
</p>
<h3>Download</h3>
<p>
See the <a href="../en/download/index.html">download</a> page for information on releases, snapshots, source code, etc.
</p>
<h3>Main Focus or &quot;Why another CMS&quot;!</h3>
<p>
There are a lot of content management systems/frameworks out there and it's very reaonable to ask &quot;why develop another CMS?&quot;!
Our answer is that we care deeply about the people actually involved with a CMS, which are for example editorial stuff, administrators, integrators and managers.<!--
Our answer is that we really care about people actually using a CMS, which are for example editorial staff, administrators and integrators,
because we are these people ourselves.
-->
</p>
<ul>
  <li><b>Usability:</b> In the case of the editorial staff it's all about usability, for example how easy it is to create/edit/delete data.<br/></li>
  <li><b>Maintenance</b></li>
  
  <li><b>Integration</b></li>
  <li><b>Secure Investment:</b> It's not so much about of RoI, but rather what are the recurrent costs, what about lock-in, what about dead ends and having to start from scratch<br/></li>
  </ul>
</body>
</html>
{'fraction_non_alphanumeric': 0.1552259399793032, 'fraction_numerical': 0.013107968264918937, 'mean_word_length': 4.513307984790875, 'pattern_counts': {'":': 0, '<': 95, '<?xml version=': 2, '>': 95, 'https://': 0, 'lorem ipsum': 0, 'www.': 4, 'xml': 4}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 6, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7479665', 'n_tokens_mistral': 1016, 'n_tokens_neox': 953, 'n_words': 332}