2009-03-13T20:56:25+01:00 0 304795 1 false cF5WWE_k4r3BUGeJe5aVNr 1 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Improve installation document on getbanjo.com

2010-08-24T12:06:00+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T20:56:50+01:00 0 304796 2 false cF5WWE_k4r3BUGeJe5aVNr 2 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Add instructions on creating skins to getbanjo.com

2010-08-24T12:06:00+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T20:57:27+01:00 Here are my suggestions for making Banjo more maintainable and more accessible to future users: * There should be a bias towards using released versions of projects. This makes it easier to install a version that works, and it makes it easier to monitor the libraries for security updates. * If a dependency project doesn't have an active community, Banjo should consider folding that code into the Banjo core. * Even if a dependency project does have an active community, if it isn't likely to get distributed by an OS package manager, Banjo should consider including the project with the banjo source in a libs subdirectory. * The maintainers should consider putting all the various Banjo and Satchmo libraries into a single package. In addition to making this easier to find and install, it also makes it easier to maintain. Currently they are scattered across various source repositories, issue trackers, and project home pages. This fragments an already small community. * The necessary Satchmo libraries should be factored out of Satchmo and put into the shared libraries package as soon as possible—it will only get harder with time. Banjo shouldn't require the installation of a full blown shopping cart, and the Satchmo users will benefit from the larger community using their libraries. Satchmo and Banjo can then select which version of the libraries to depend on for each release, which will simplify both projects. * Though the multi–site capabilities are excellent, I think the defaults can be improved so that it doesn't get in the way of a simple single–site deployment. It doesn't currently prevent single site deployment, but it makes it harder than it needs to be. 0 304797 3 false cF5WWE_k4r3BUGeJe5aVNr 3 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Make the installation process easier

2010-08-24T12:06:00+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T21:00:17+01:00 Needs to be cleaned up. Perhaps comments should just be turned off on that page. Or we could move it to the information to the Assembla space wiki and get rid the page in getbanjo.com completely. 0 304821 4 false cF5WWE_k4r3BUGeJe5aVNr 4 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

getbanjo.com->Documentation->Remote Posting Tools has spam

2010-08-24T12:06:00+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T21:04:44+01:00 This is confusing. It should point to getbanjo.com. 0 304826 5 false cF5WWE_k4r3BUGeJe5aVNr 5 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

banjo-users description at Google Groups points to launchpad.net

2010-08-24T12:06:01+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T22:49:55+01:00 The current pages don't look very maintained. This ticket tracks ideas for sprucing them up. Pros of getbanjo.com: * It gives us a homepage that we control, so we can transition off of Assembla if necessary. * It is a lot easier to navigate for a new user (my first time at Assembla I found confusing). * It provides a demo of what Banjo can do. Cons: * Two places to keep up to date. * Two places to look for everything. Suggestions: # Put on GetBanjo->Download page links to Assembla->Files. # Make GetBanjo->Documentation links point to Assembla->Wiki # Get rid of FAQ link (if we want one we'll put it in the Wiki). # Get rid of Apps link, as Django Site Skins appears required now, and there are no other apps. # Move the bugs link from the resources menu in the sidebar to the top menu. # Add a link to Satchmo (maybe with a short explanation) under the resources menu in the sidebar. # Add a new blog post discussing the changes. 0 304894 6 false cF5WWE_k4r3BUGeJe5aVNr 6 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Simplify getbanjo.com pages

2010-08-24T12:06:02+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T23:33:28+01:00 When using ReST markup while creating a post, it appeared to format my paragraphs properly, but didn't do the links correctly. It left them as .._NAME: TARGET. 0 304941 7 false cF5WWE_k4r3BUGeJe5aVNr 7 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Problems with ReST markup.

2010-08-24T12:06:03+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T23:53:21+01:00 I couldn't over-ride _post_excerpt.html or view_post.html with my own templates. I had to edit the Banjo source. 0 304953 10 false cF5WWE_k4r3BUGeJe5aVNr 10 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Post look should be editable in the skin template.

2010-08-24T12:06:03+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-13T23:54:23+01:00 Banjo needs an "archive" template tag to link to old posts by date. 0 304955 11 false cF5WWE_k4r3BUGeJe5aVNr 11 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Need to view posts by date.

2010-08-24T12:06:03+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-14T00:33:50+01:00 Good instructions are here: http://k0001.wordpress.com/2007/11/15/using-recaptcha-with-python-and-django/ 0 305003 12 false cF5WWE_k4r3BUGeJe5aVNr 12 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Add support for ReCAPTCHA to the comments.

2010-08-24T12:06:06+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-14T00:36:40+01:00 I attempted to disable the comments in the admin UI, but they are still on my pages. 0 305005 13 false cF5WWE_k4r3BUGeJe5aVNr 13 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Comments are appearing even though disabled.

2010-08-24T12:06:06+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org 2009-03-16T22:18:13+01:00 When adding a post, it is possible to select an unavailable markup and then the post is displayed with no effect. if a markup plugin is unavailable then it shouldn't be shown in the drop down menu unless it is the markup used for an already existing post. Or at least a warning should be displayed. 0 307071 14 false cF5WWE_k4r3BUGeJe5aVNr 14 3 cF5WWE_k4r3BUGeJe5aVNr d82J9QFGGr3zm3ab7jnrAJ 0 New 0

Unavailable markup plugin is used with no warning

2010-08-24T12:06:43+02:00 None 0.0 0.0 cF5WWE_k4r3BUGeJe5aVNrresplinresplinRichard Esplinrichard.esplins.org