Posted by RobLoach on July 9, 2008 at 4:58pm
What features should be part of DrupalBin when DrupalBin.com goes to Drupal 6?
- Post code segments (Drupal 5, Drupal 6, Drupal 7)
- OpenID
- Replace reCAPTCHA with Mollom
- Comments
What features should be part of DrupalBin when DrupalBin.com goes to Drupal 6?
Comments
The CAPTCH appears also when
The CAPTCH appears also when I'm logged in which is annoying, other then that - I find it very intuitive. Good job! :)
Stuff
Answers
More stuff
I'm just going to spit stuff out here and think aloud
Urls - i think we just code a small menu callback taht calls back to node_add and has a little alter that prepopulates it
Push and pull api - can also go in the module.
Comments - i don't think nodecomment would work, why not just make them full-on nodes and theme it so it looks cool.
Another thing that I though of that might be kind of hard: drupalbin.com/cvs/contributions/modules/views/views.module: shows the views module code in CVS, except highlighted. Then you can hit the fix link and make a local version.
Also, generating a unidiff between versions that everyone can see.
In fact, why don't we show a tree of fixes in the sidebar next to the node! this would be very very hard but very very awesome. If we stored the parent in a hidden nodereference, then we do some sort of fancy query and sort it, except it couldn't be a nodereference if it was to pull from CVS. If someone wants this then i can set up a chipin :-)
Then you check the checkboxes for two versions and hit the "show diff" button, which shows you a unidiff and also lets you download it.
Also on a different train of thought
Social and non-social pastebins - make it very clear what the benefits of an account are, make it easy and motivating to get one, and make it so you can have private pastes when you have an account - and make a list of YOUR pastes somewhere.
Make it easily filterable by tags, etc.
Oh. And make it look good (not garland).