Simplify the "feature"

[Paul Everitt]

If you login to kdiab as admin:admin and go here:

  http://kdiab.sixfeetup.com/offices/nyc/

...the middle column represents "the voice of the organization". In this case, OSI. The top of that column is the "feature", meaning some story they'd like to appear on all office home pages.

I implemented this half-correctly. It's on an edit screen, done as a simple blob of HTML. However, I *stupidly* put this on the edit form for *all* offices. Thus, when it is time to update the feature, we have to visit all offices.

I'd like to move it to /offices and that edit form. That gets more complicated, though, because that edit form is shared for all office communities and regular communities.

Any suggestions, and can I get help on the fix? Some ideas:

1) If you change it on one office, it wakes up all the others and changes it. Perhaps with a knob underneath asking if you want to do this.

2) Make a new view, just for this, and put it on /offices then add to the actions menu.

3) Put it on the edit form for /offices

[Shane Hathaway (shane-hathawaymix)]

Done in revision 2934. I created an edit form just for IIntranets (which is provided by /offices) and moved the 'feature' attribute to the IIntranets object.