render-engine 2025.11.1__tar.gz → 2025.11.1a1__tar.gz

{render_engine-2025.11.1 → render_engine-2025.11.1a1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: render_engine
-Version: 2025.11.1
+Version: 2025.11.1a1
 Summary: A Flexible Static Site Generator for Python
 Project-URL: homepage, https://github.com/render-engine/render-engine/
 Project-URL: repository, https://github.com/render-engine/render-engine/

{render_engine-2025.11.1 → render_engine-2025.11.1a1}/docs/docs/collection.md

@@ -46,8 +46,7 @@ sort_reverse: bool = False
 title: str
 template: str | None
 archive_template str | None: The template to use for the archive pages.
-ContentManager: type[ContentManager] | None = FileContentManager: The `ContentManager` to use.
-content_manager_extras: dict[str, Any]: Configuration options to send to the `ContentManager` during instantiation.
+skip_site_map: bool = False: Flag to indicate whether this Collection should not be included in the SiteMap.
 ```
 
 ## Attributes

{render_engine-2025.11.1 → render_engine-2025.11.1a1}/docs/mkdocs.yml

@@ -26,7 +26,6 @@ nav:
     - Site Objects: site.md
   - Extending Render Engine:
     - Plugins: plugins.md
-    - Content Managers: content_manager.md
   - Parsers: parsers.md
   - CLI: cli.md
   - Templates and Themes:

{render_engine-2025.11.1 → render_engine-2025.11.1a1}/src/render_engine/__version__.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '2025.11.1'
-__version_tuple__ = version_tuple = (2025, 11, 1)
+__version__ = version = '2025.11.1a1'
+__version_tuple__ = version_tuple = (2025, 11, 1, 'a1')
 
-__commit_id__ = commit_id = 'g3ef9c0acb'
+__commit_id__ = commit_id = 'g5ed5705d6'

{render_engine-2025.11.1 → render_engine-2025.11.1a1}/src/render_engine.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: render_engine
-Version: 2025.11.1
+Version: 2025.11.1a1
 Summary: A Flexible Static Site Generator for Python
 Project-URL: homepage, https://github.com/render-engine/render-engine/
 Project-URL: repository, https://github.com/render-engine/render-engine/

{render_engine-2025.11.1 → render_engine-2025.11.1a1}/src/render_engine.egg-info/SOURCES.txt

@@ -34,7 +34,6 @@ docs/requirements.txt
 docs/docs/archive.md
 docs/docs/cli.md
 docs/docs/collection.md
-docs/docs/content_manager.md
 docs/docs/custom_collections.md
 docs/docs/feeds.md
 docs/docs/index.md

render_engine-2025.11.1/docs/docs/content_manager.md

@@ -1,67 +0,0 @@
----
-title: "Enhancing Functionality with Content Managers"
-description: "Guide to using creating Content Managers to use alternate content storage systems."
-date: August 22, 2024
-tags: ["content_manager", "render-engine", "customization"]
----
-
-Content Managers are a way to control how and where your content is stored.
-
-## Introduction
-
-Render Engine `Collection` uses a `ContentManager` to manage the storage of content for site generation. By default
-content is stored in the file system with each piece of content existing in a discrete file. With an alternate
-`ContentManager` the content can be stored in a database, JSON file, or other alternate data store.
-
-## Selecting a `ContentManager`
-
-The `ContentManager` for a given [`Collection`](collection.md) is controlled by the `ContentManager` attribute. When
-the class is instantiated the `ContentManager` is also instantiated with any `content_manager_extras` being passed
-as arguments. To access the `ContentManager` of a given `Collection` use the `content_manager` attribute.
-
-## Creating a `ContentManager`
-
-To create a `ContentManager` create a sub-class of `ContentManager` that implements the following methods:
-
-```python
-@property
-@abstractmethod
-def pages(self) -> Iterable:
-    """The Page objects managed by the content manager"""
-    ...
-
-@abstractmethod
-def create_entry(self, filepath: Path = None, editor: str = None, metadata: dict = None, content: str = None):
-    """Create a new entry"""
-    ...
-```
-
-### `pages`
-
-The `pages` property is how the `Collection` accesses its content. It is a method that _must_ be implemented by
-every `ContentManager`. An example `pages` implementation (from the
-[`FileContentManger`](https://github.com/render-engine/render-engine/blob/main/src/render_engine/content_managers/file_content_manager.py)) is:
-
-```python
-@property
-def pages(self) -> Iterable:
-    if self._pages is None:
-        self._pages = [self.collection.get_page(page) for page in self.iter_content_path()]
-    yield from self._pages
-```
-
-### `create_entry`
-
-The `create_entry` method is used by the Render Engine CLI tool to add new entries. It is responsible for adding
-the new entry to the datastore and, if an `editor` is specified, giving the user the ability to edit the new entry
-prior to committing the entry to the datastore.
-
-#### Arguments
-
-- `filepath: Path`: The path on the filesystem to store the new entry.
-- `editor: str`: The text editor to open for editing the new entry.
-- `content: str`: The initial content for the new entry.
-- `metadata: dict`: The metadata for the new entry.
-
-!!! Note
-    Not every `ContentManager` actually needs all the arguments that are passed.