<commit_before>---
layout: about
title: Poole
---


**Poole** is a web-interface dedicated for managing dynamic content of Jekyll-based websites. Users of Jekyll can create, edit and delete files that live within the _posts directory. Poole can be considered a smart way of publishing for hackers and humans, solving the issue that Jekyll is has not yet been suitable for less-technical content editors.

While developers can still enjoy all freedom the Jekyll framework provides, editors can easily access, edit and publish content using a visual interface.


Separation of Concerns
===============

Ordinary Content Management Systems (Wordpress et. al) are trying to solve many things at once. They allowed users to maintain content, such as articles plus styling them and so on. We believe that concerns should be separated.


Website Development
---------------

Website developers prefer to have full freedom about how to structure their site. They know how to deal with HTML and CSS. And most of them are familiar with template languages. We've found that Jekyll is a perfect foundation for building a website, from a developer point of view. There's nothing we want to add here.


Content Management
---------------

This is where Jekyll has it's weaknesses. Content Editors often do not have a technical background, and they don't have to. With Poole, non-technical people can use a visual interface for maintaining the contents of a website (built with Jekyll).


**Content not layout**

Editors should not be concerned with styling tasks. They should be able to focus on structured, content-oriented writing. That's why we removed all styling capabilities from the interface.


Limits
===============

Of course there are limits with this approach. Poole goes with Markdown and YAML, thus only allows content to be authored in plaintext. With Substance I'm working on a larger scale solution of web-based content composition. In the future we may be able to offer WYSIWYG composition, But without the drawbacks of an unpredictable output. At the end of the day, building websites should be easier. And our mission is to make it happen.<commit_msg>Updated 0100-01-01-about.md<commit_after>---
layout: about
title: Poole
published: false
---


**Poole** is a web-interface dedicated for managing dynamic content of Jekyll-based websites. Users of Jekyll can create, edit and delete files that live within the _posts directory. Poole can be considered a smart way of publishing for hackers and humans, solving the issue that Jekyll is has not yet been suitable for less-technical content editors.

While developers can still enjoy all freedom the Jekyll framework provides, editors can easily access, edit and publish content using a visual interface.


Separation of Concerns
===============

Ordinary Content Management Systems (Wordpress et. al) are trying to solve many things at once. They allowed users to maintain content, such as articles plus styling them and so on. We believe that concerns should be separated.


Website Development
---------------

Website developers prefer to have full freedom about how to structure their site. They know how to deal with HTML and CSS. And most of them are familiar with template languages. We've found that Jekyll is a perfect foundation for building a website, from a developer point of view. There's nothing we want to add here.


Content Management
---------------

This is where Jekyll has it's weaknesses. Content Editors often do not have a technical background, and they don't have to. With Poole, non-technical people can use a visual interface for maintaining the contents of a website (built with Jekyll).


**Content not layout**

Editors should not be concerned with styling tasks. They should be able to focus on structured, content-oriented writing. That's why we removed all styling capabilities from the interface.


Limits
===============

Of course there are limits with this approach. Poole goes with Markdown and YAML, thus only allows content to be authored in plaintext. In future projects like the Substance Composer, may allow us offer WYSIWYG composition as well. At the end of the day, building websites should be easier. And our mission is to make it happen.

{'fraction_non_alphanumeric': 0.06269149186896064, 'fraction_numerical': 0.0018854584020740043, 'mean_word_length': 4.138014527845036, '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': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4196128', 'n_tokens_mistral': 1006, 'n_tokens_neox': 942, 'n_words': 643}