I did some digging, and the macro they used in the Sakai site is not
available in our Jira Studio. However I was able to create a new macro
that we can use for a similar effect, called "Expand". To use it,
surround the content with the {expand} macro like this:
{expand:title=Heading of a Big Section}
Here is the hidden content that is revealed when they click on the title
{expand}
However, if we're moving the docs to Drupal, it would be different
functionality. If you do want to restructure to a one page format, let
me know and I'll find out how.
Also, as far as the copying and pasting pains, once it's moved into the
Drupal site, an entire set of release docs can be cloned for future
releases. It's just the initial copying and pasting from wiki to Drupal
that we need to deal with.
Greg, if you can get the release docs in the wiki ready for import this
week, I have a student that can do the copy/paste either Wednesday or
Friday this week.
Michelle
On 2/13/12 9:38 AM, Greg Logan wrote:
On 12-02-13 11:25 AM, Michelle Ziegmann wrote:
And unfortunately it also doesn't resolve the laborious copy and paste
process involved in creating a new set of release docs. If it were me
that had to individually copy and paste all of those pages that are
included in each set of release docs (I count 29 pages per release!), I
would strongly consider restructuring the release document template to
be contained all in one page, similar to how Sakai does it (see
https://confluence.sakaiproject.org/display/DOC/Sakai+CLE+2.8+release+notes).
I like this format, is this something that comes with Confluence or did
Sakai built it themselves?
G
Michelle
On 2/13/12 9:04 AM, Tobias Wunden wrote:
Greg,
this sounds like a great idea! Out of interest, does anybody remember
the reasoning behind the original creation of the two separate wikis?
Tobias
On 13.02.2012, at 17:54, Greg Logan<[email protected]> wrote:
We discussed this at Oxford but it should probably also be brought up on
list. I #propose moving our release docs (the contents of the MHDOC
wiki) onto the main Opencast website. This would remove the confusion
of having two wikis and the accidental and random links between them.
Creating release docs would then be a matter of trimming the trunk docs
and copying them (process tbd) into the main page.
Thoughts, comments? This would take effect for the 1.3 release.
G
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
--
Michelle Ziegmann
Electronic Communications Specialist
Educational Technology Services
University of California Berkeley
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
