Community help wikis per release

[Adam Sommer]

Thanks Phil,


Forgot to mention one more thing - could you replace the embedded CSS
> with just a new class name, please? Then, we can patch the wiki CSS with
> the appropriate CSS for the new class, thus keeping all of the style
> information in one file.
>
>
I've adjusted the macro file to check for the current release code names and
if it doesn't match it will print the macro usage statement.  From my tests
I wasn't able to add any html or other objectionable strings.

I agree there will be a small maintenance burden using this macro, because
for each release the if elif statement will have to be updated.  I can't
think of a way around this, unless there's a way to dynamically get a list
of current releases from somewhere else?

Also, from my tests changes to the macro file were visible when the page was
resaved or refreshed.

I've also extracted the style info into a separate CSS file.  I wasn't sure
of the naming scheme, so the class names should probably  be changed to
match the site scheme if there is one.

Thanks again.

-- 
Party On,
Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-doc/attachments/20071021/77b7af1d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ReleaseVersion.py
Type: text/x-python
Size: 1418 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-doc/attachments/20071021/77b7af1d/attachment.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ReleaseVersion.css
Type: text/css
Size: 486 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-doc/attachments/20071021/77b7af1d/attachment.css>