Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

Project Nimrud, or how I learned to stop worrying and love the microsite by Mind Map: Project Nimrud, or how I learned to stop worrying and love the microsite
0.0 stars - 0 reviews range from 0 to 5

Project Nimrud, or how I learned to stop worrying and love the microsite

Principles

Open Source, using a liberal license

A minimum of technologies

Keep pieces simple

Core components provide basic services

Provide migration paths in case scope creeps

Components are independent but provide common services to one another

Extensions through plugins to defined extension points

Feature-growth through distributions

Separation of concepts to separate roles

Repeatability is more important than simplicity

Components

Concave, a Simple Content Management System

Convex, a Simple Digital Asset Management System

Leica, a simple ecommerce system

Yes, this is really more of a pipe-dream than a serious proposal

Converging, a Simple Social Network

Conex, a big pile of experimental code

3rd party components

Low-level compontents

Design

Use WSGI and Grok where possible, with Pylons or Turbogears 2 for data-heavy applications

Ensure that all components can speak the same authentication protocol

Leverage something like Deliverance to provide consistent, cross-component themes

Use z3c.chameleon so we have a common templating language for most tasks

We need some sort of basic page-composition framework and viewlet provider system that could be shared by Convex and Grokfire.

Pretty much everything will plug into Convex for storing blob files

Develop on the ZODB, store in the ZODB, deploy with Relstorage

Create Slicehost and Amazon VMs with various distributions to simplify deployment

Problems

Each component has its own authorization concerns and should handle authorization itself, but people might expect authorization to "just work" logically across applications

Theming and template designs are actually pretty tightly integrated, and it's hard to draw a solid line between them

Audiences

Boutique web design and PR firms

Do we care about end users at all (that is, random individuals who want a simple CMS for themselves)?

Absolutely non-technical content managers

Highly technical content managers