[
https://issues.apache.org/jira/browse/JSPWIKI-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132775#comment-18132775
]
Arturo Bernal commented on JSPWIKI-1316:
----------------------------------------
Update after the discussion on
[[email protected]|mailto:[email protected]] on 26 and 27 October.
Jerry Andrews agreed that some import capability would be good, and suggested
that it should be an extension point for plugins, with one good reference
implementation, and not a fixed set of implementations. That fits this issue
better than the list of formats above, so the proposal is changed to this:
define a small interface for importers and exporters, ship one reference
importer (a Markdown directory tree is the simplest), and let other sources
such as MediaWiki and Confluence be added as plugins.
> Add tools to import pages from other wikis and to export the wiki
> -----------------------------------------------------------------
>
> Key: JSPWIKI-1316
> URL: https://issues.apache.org/jira/browse/JSPWIKI-1316
> Project: JSPWiki
> Issue Type: New Feature
> Reporter: Arturo Bernal
> Priority: Major
>
> This is a proposal for discussion, not an implementation. A common reason not
> to adopt a wiki is the cost of moving the existing content in, and of getting
> it out again.
>
> What exists today: I did not find an import tool, or a way to export pages to
> formats such as static HTML, PDF or Markdown, among the plugins in
> jspwiki-main or in the other modules of the repository. The page providers
> keep pages as text files in the default configuration, so content can be
> copied by hand, but nothing converts it. The search for existing issues on
> import, export and migration found no open ticket for this.
>
> Proposal, import: a command line or admin page tool that reads a Markdown
> directory tree, and a MediaWiki or Confluence export, and creates pages and
> attachments, converting the markup to the configured syntax and keeping page
> names, links and history where the source has them. Proposal, export: a way
> to export a page, a set of pages or the whole wiki as static HTML or as a
> Markdown tree, which also helps backup and migration away. Open questions:
> which sources matter most, whether this belongs in jspwiki-main or in a
> separate module, and whether an existing converter library with an Apache
> compatible licence can be used instead of writing parsers.
>
> To be discussed on [[email protected]|mailto:[email protected]]
> before any code is written.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
