I have made an exporter which can convert the existing help into microdown format.
As this is a one time thing, it is not clear this code should be permanently in the image. The tool is therefore included here as a file-in, which overwrites some parts of the existing help system.

HelpSystem-Core.st.zip

The api of Microdown has changed a lot since this code was last touched. NewTools-DocumentationReader has a lot of failing tests. I will look at this today.

Kasper I'm fixing several points:

• I added a dev branch and we should do PR on this branch so that after once this is ok we can merge into master (= into pharo).
• We should not use Smalltalk ui icons but self iconNamed:

I'm trying to fix the class comments but I cannot.

• how do we decide to internalize the file? because I do not get when I decide it.

• I have no idea what is openOnCustomHelp: aDescription there is no comment and no sender.

• openPharoRepo just breaks on me.

• open
  "Open a HelpBrowser on the internalized docs."
  

  ^ self error: 'We need to define a default starting point'

I have no idea what is a default starting point and how to do it so the error does not help the user at all.

• the following raises a DNU:

openBrowser
	<script>
	StHelpBrowserPresenter openTopic: self githubTopics 

after I press reset, it is working.
Before I was using StHelpBrowser open ....

The cache in StTopicFromGithubBuilder class is not initialized, causing githubTopicsFrom: to fail.

I believe StHelpBrowserPresenter actually does two things:

• composes directories and md-files into a topic structure
• presents a topic structure where the leafs are microdown

I believe it would be beneficial to split this into two classes according to those two roles.

In addition, StHelpBrowserPresenter caches previous files using the memory file system. I believe the caching is necessary - in particular for the StGithubDocFolderBuilder (PR #7) which is rather slow.

Rather than caching files, StHelpBrowserPresenter could cache the topic tree, independent of how it was obtained.

The text field of the help browser do not wrap long lines.

I will investigate.

@Ducasse Perhaps the MicrodownPresenter stuff should move here, the presenter solves the issues, makes it all look nicer, and it makes sense to use "DocumentationReader" as a platform for more advanced support for showing microdown documents.

If this is the case I will make a PR that moves it here, and make sure the examples run.