Problems to think about (and solutions)

Table of contents

Blogreen Core

Document inclusion

status: to discuss.

The deprecated implementation used to split pseudo-static content. The result was that a basic template would for example be as this:

/templates/default/template.htm

! (header)
@(Plugin)
! (footer)

/templates/default/header.htm

<html>
  <head>
    <title>$ (param[site_title])</title>
  </head>
  <body>

/templates/default/template.htm

  </body>
</html>

A system based on two files may be easier to handle:

/templates/base.xml

<?xml version="1.0" encoding="utf-8"?>
<html>
  <head>
    <title><blogreen:param name="site_title" /></title>
  </head>
  <body>
    <blogreen:area name="page_content" />
  </body>
</html>

/templates/template.xml

<?xml version="1.0" encoding="utf-8"?>
<blogreen:include template="base">
  <blogreen:element area="page_content">
    <blogreen:plugin name="Plugin" />
  </blogreen:element>
</blogreen:include>
pros

  • Clean XML

cons

  • May not be more WYSINWYG...

Multi-site support

status: to discuss.

Model View Controler model

status: to discuss.

Searching system

status: to discuss.

The searching machanism may rely on external tools such as tsearch2 for the PostgreSQL data-storages.

Authentification & user management

status: to discuss.

Dynamic JS inclusion and dependencies management

status: to discuss.

Blogreen.org

Provide subdomains for different kinds of users.

status: on discussion.

How to navigate easily between subdomains?

Architects use plugins, developers code plugins. How to submit plugins and update them?


Edit [Edit this page] [Move to parent directory] Up