Last modified by Stefano Maffulli on 2023/02/17 01:52
- Manage
- Copy
- Actions
- Export
- Print Preview
- Viewers
- Source
- Children
- Content
- Attachments (1)
- History
- Information
- Likes
Export
Choose the export format from the list below:
$services.rendering.render($uix.execute(), 'html/5.0')
$services.rendering.render($uix.execute(), 'html/5.0')
$services.rendering.render($uix.execute(), 'html/5.0')
- Office Formats (3)
-
Export as Open Document Text (ODT) format using the Office Server
-
Export as Portable Document Format (PDF) using the Web Browser
-
Export as Rich Text Format (RTF) using the Office Server
-
- Other Formats (1)
-
Export as HyperText Markup Language (HTML)
-
Export as
Select the pages to export:
- Legend:
- Created Page
- Modified Extension Page
- Clean Extension Page
Joseph - first, I think that this looks great. I have only two questions/comments:
1) Should we be thinking a bit about content storage/access/discovery/tagging options? That is, if the course is going to be distributed and highly modular, I am guessing that we will end of with variants (derivative fit-for-context educational content/designs) and will need to be able to easily access, version and such.
2) I am wondering if there was a rationale for adopting the CC-by-sa licence rather than the CC-by licence.
Cheers!!!
RE: storage/access/discovery/tagging options
Yes, this wiki is developmental and may or may not be optimal.
RE: CC-by-sa licence rather than CC-by
The -sa seemed more appropriate initially for what this is, but once we have few more on the WG this should be discussed, including OSI Board preference. The current dual licensing with GNU-FDL is mirrored in the CC-by-sa.