[sakai2-tcc] [cle-release-team] Confluence upgrade/plugin issues/documentation changes

[Matthew Jones]

Thanks Megan!

Sam and I agreed,

This theme is something applied to the top level "Space". So if you're
logged in with sufficient privileges on the Space (say documentation) you
can click "Browse->Space Admin->Themes" and change it to the documentation
themes. I only switched Documentation and QA to see what it looks like
other spaces aren't changed and they have the default theme. I guess they
have more themes we can use that I haven't looked it.

This theme combines Page Tree and Page Tree Search macros together at the
top level of that Space. It's probably possible to do it at lower levels if
the space is organized.

Thanks for offering to cleanup. Basically what it involves is this:
1) Going into Tools->View in Hierarchy and rearranging the pages so they
are in the appropriate "place"
  - Pages that shouldn't appear in the hierarchy can be "hidden" by putting
them at the same level or higher than the home. This hides them.
2) Editing each page so the headers are correct (Ideally only H1-H2 should
be used for main headers so a table of contents can be created at max 2
levels)
3) Removing the blocks in each old page that contain elements for
"wikimarkup" that contains blocks like this.

{composition-setup}
cloak.toggle.type = text
cloak.toggle.open = [+]
cloak.toggle.close = [-]
{composition-setup}


I've disabled this plugin so the pages that have this will come up with
errors in the rendering.

If we want to hide a section, add the "Expand Macro" and put the include or
content in this macro.

It actually seems pretty smooth and easy now and I think it will look
really nice afterward just based on what I've seen so far.

On Tue, Apr 10, 2012 at 12:51 PM, May, Megan Marie <mmmay at indiana.edu>wrote:

>  Hi Matt, ****
>
>    I don’t see what having the plugin buys us anymore so I think it’s ok
> to move ahead without it.  ****
>
> ** **
>
> Is the documentation theme something global?  I noticed this has already
> been applied to the QA WG space.  ****
>
> ** **
>
> FWIW, I’ve been working on the QA WG space here and there to clean it up.
> If you have changes in mind, let’s be sure to collaborate.   ****
>
> Megan ****
>
> ** **
>
> *From:* cle-release-team-bounces at collab.sakaiproject.org [mailto:
> cle-release-team-bounces at collab.sakaiproject.org] *On Behalf Of *Matthew
> Jones
> *Sent:* Tuesday, April 10, 2012 11:42 AM
> *To:* sakai2-tcc Committee; cle-release-team at collab.sakaiproject.org
> *Subject:* [cle-release-team] Confluence upgrade/plugin
> issues/documentation changes****
>
> ** **
>
> Hi all!****
>
> ** **
>
> Recently as part of a confluence upgrade, one particular plugin stopped
> working. This was because it changed from a free plugin to a commercial
> plugin. This plugin, the composition plugin [1] was mostly used by Anthony
> on pages related to Sakai documentation to create better navigation. For an
> unlimited license, the license for this was $199 a year, and originally
> Anthony had said this wouldn't be a problem and the foundation would be
> able to cover it. However I enabled the evaluation version and discovered
> that none of the pages that contained the composition plugin were manually
> upgraded (they still didn't work correctly). This seemed to be because in
> order to upgrade these pages you actually have to [2]****
>
> ** **
>
> *1) Disable the plugin*****
>
> *2) Upgrade confluence*****
>
> *3) Upgrade the plugin*****
>
> *4) Enable the plugins*****
>
> ** **
>
> We didn't do #1, and obviously we can't go back to before step #2, so
> everything becomes a either a manual conversion or find something that
> works just as good or better (since every page needs manual inspection
> anyway). While looking at other confluence pages, I saw they all had left
> navigation. This is a "documentation theme" and after enabling that and
> cleaning up the hierarchy a little, I think the documentation section
> actually looks better than it did before.****
>
> ** **
>
> https://confluence.sakaiproject.org/display/DOC/Documentation ****
>
> ** **
>
> So the questions I have are:****
>
> 1) Do others agree? Fine moving forward now without this plugin and left
> tree navigation?****
>
> 2) There is an "expand macro" (see Release Documentation->2.8 release
> notes) that I used for "What's new". Previously all sections on the main
> page were under a expand style macro. Should we still have these sections
> hidden or is one big page good?****
>
> 3) I'm thinking of also applying this for the QA section, that needs a
> little work cleaning up the page hierarchy.****
>
> ** **
>
> https://confluence.sakaiproject.org/display/QA/Home****
>
> ** **
>
> I just didn't want to put more than an hour into this if others felt
> strongly about something else.****
>
> ** **
>
> [1] http://www.customware.net/store/confluence/composition_plugin.html****
>
> [2]
> http://wiki.customware.net/repository/display/AtlassianPlugins/Upgrading+from+Conf+3.x+to+4.x+-+CustomWare+Plugins
> ****
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20120410/5c6b35ab/attachment.html