LoCoDjango

Differences between revisions 7 and 13 (spanning 6 versions)
⇤ ← Revision 7 as of 2007-12-08 23:19:41 →
Size: 5618
Editor: c-67-165-213-225
Comment: blogmaker
← Revision 13 as of 2007-12-12 03:12:08 → ⇥
Size: 5727
Editor: c-67-165-213-225
Comment: http://code.google.com/p/blogmaker/
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
Loco Django Development is a project aimed at developing a framework for LoCo teams to use as a website. Loco Django Development is a project aimed at defining, customizing and/or developing a Django-based CMS for LoCo teams to use as a website.
Line 26: Line 26:
First flesh out the brainstorming section below, then come up with a design and implementation plan. First flesh out the discussion/brainstorming section below, then come up with a design and implementation plan.
Line 30: Line 30:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: ''This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:''
Line 34: Line 34:
Should cover changes required to the UI, or specific UI that is required to implement this ''Should cover changes required to the UI, or specific UI that is required to implement this''
Line 38: Line 38:
Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.		 ''Code changes should include an overview of what needs to change, and in some cases even the specific details.''
Line 49: Line 42:
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release. ''It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.''
Line 51: Line 44:
This need not be added or completed until the specification is nearing beta. ''This need not be added or completed until the specification is nearing beta.''
Line 55: Line 48:
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. ''This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.''
Line 80: Line 73:
See also an interesting post by James Bennet on blogs and django:
http://www.b-list.org/weblog/2007/nov/29/django-blog/
Line 92: Line 88:
 http://code.google.com/p/blogmaker/
Line 94: Line 91:

Luambo multi-user multi-blog: http://svn.luamboblog.org/

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Loco Django Development is a project aimed at defining, customizing and/or developing a Django-based CMS for LoCo teams to use as a website.

Release Note

Better integration with Launchpad.

Rationale

Python for LoCo sites!

Use Cases

Assumptions

Design

First flesh out the discussion/brainstorming section below, then come up with a design and implementation plan.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

Outstanding Issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

Feature Discussions

All are welcome to view the current specs for each of these and provide input. If you have any other ideas for features please add them as well.

Discussion

Here are some links to related projects and apps.

See also an interesting post by James Bennet on blogs and django: http://www.b-list.org/weblog/2007/nov/29/django-blog/

https://launchpad.net/banjo/

  • http://coderseye.com/ Banjo will be a blog app with CMS features, a modular extension system, and all the bells and whistles needed to be a real alternative to Mephisto or WordPress. multi-blog system, which needs to be easily skinnable Atom feeds are implemented - looking for a suitable publishing engine.

Blogmaker - "a full-featured, production-quality blogging application for Django. It supports trackbacks, ping and comments with moderation and honeypot spam prevention."

Djog: http://dev.oebfare.com/projects/djog/ - a Django blog app

Luambo multi-user multi-blog: http://svn.luamboblog.org/

https://launchpad.net/kaleidoscope/ Kaleidoscope - CMS for Real content

  • "A Django CMS for Real Content", but I don't see any code....

https://launchpad.net/swing42/

https://launchpad.net/ubuntu-nl-website/

  • A django app with moinmoin backend for the homepage
  • A django app for authentication
  • A heavily customized PunBB forum
  • A django pastebin with pygments syntax coloring and hashcash spam protection
  • A wordpress-mu install for blogs
  • A planetplanet blog aggregator
  • Several maintenance scripts

https://launchpad.net/django-forum/

https://launchpad.net/django-xmlrpc/ graham.binns

https://launchpad.net/django-survey/

KSS Django - Kinetic Style Sheets. A beautiful AJAX framework.

  • http://code.djangoproject.com/wiki/KSSInDjango

    • KSS is a javascript framework that aims to allow Ajax development without javascript. It uses stylesheets with CSS-compliant syntax to setup behaviours in the client and a set of well-defined commands that are marshalled back from the server to manipulate the DOM. get AJAX features but without losing accesibility.

https://launchpad.net/kaplan/ Kaplan TODO

https://launchpad.net/geekgrep/

https://launchpad.net/loco-drupal/

CategorySpec

LoCoDjango (last edited 2008-10-06 21:16:04 by c-67-165-213-225)