Great work! Gabor and Addi<br><br>Looks like there are special permissions for those features, mission, etc. pages. I'm not seeing and "edit" link when I'm on those pages.<br><br>I'm pretty sure I'm on the docs team. But is there a "super docs team" permission or some such that you need to work on those pages.<br>
<br>Shai<br><br><div class="gmail_quote">On Wed, Oct 29, 2008 at 6:57 PM, Addison Berry <span dir="ltr"><<a href="mailto:drupal@rocktreesky.com">drupal@rocktreesky.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just an FYI, this was still on Full HTML format due to whack HTML. I<br>
cleaned it up, stripping all of the junk out and making it suitable<br>
for the Doc team format, so it is now cleaner and accessible to doc<br>
team. It does indeed need more cleanup though.<br>
<br>
- Addi<br>
<div><div></div><div class="Wj3C7c"><br>
On Oct 29, 2008, at 6:37 PM, Gábor Hojtsy wrote:<br>
<br>
> Hey,<br>
><br>
> Up until earlier yesterday, the <a href="http://drupal.org/features" target="_blank">http://drupal.org/features</a> page was<br>
> managed by an obscure and old module called feature, which is used by<br>
> less the 30 sites reporting back:<br>
> <a href="http://drupal.org/project/usage/feature" target="_blank">http://drupal.org/project/usage/feature</a> The permissions for editing<br>
> this page were limited, so you could not get there, and even if you<br>
> could, the module restricted you to its custom categories support (no,<br>
> not taxonomy), and feature items in categories, which could only have<br>
> some textual intro, an image link and a read more link. All managed in<br>
> custom code stored in custom tables. Not totally flexible. This data<br>
> was all used to generate what looks like very dated markup such as<br>
><br>
> <div style="font-size: 120%; font-weight: bold; margin-bottom:<br>
> 15px;"><p>General features</p></div><br>
><br>
> for a header and<br>
><br>
> <i>Collaborative Book</i> - Our unique collaborative book feature<br>
> lets you setup a "book" and then authorize other individuals to<br>
> contribute content.<div align="right"><a href="node/284">detailed<br>
> information</a>&nbsp;<br>
><br>
> for explanation. Ouch. It also linked to Drupal 4.3 screenshots as<br>
> showcase. Due to the permissions and architecture limitations, this<br>
> was deadly outdated. It also did not support versioning of the feature<br>
> list, only supported plain text input in feature descriptions, no<br>
> formatting whatsoever, etc.<br>
><br>
> So what happened yesterday, is that this module was finally retired<br>
> from<br>
> <a href="http://drupal.org" target="_blank">drupal.org</a>, and its generated page was moved into the node which made<br>
> it possible to have it in the handbook, but magically did not contain<br>
> any text before. Now the content is up for the doc team, and you<br>
> should be able to run with it and update / spice it up, clean out old<br>
> markup, etc. Please do!<br>
><br>
> Gábor<br>
> --<br>
> Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
> List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
<br>
--<br>
Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
</div></div></blockquote></div><br>