confusion between mardown and pillar

[demarey]

When publishing a web site, files are visited and objects representing them are created.
When visiting a .md file, a FOPillarPage is created.
When visiting a .pillar file, a FOFileObject is created.
I do not see any FOMicrodownPage or FOMarkdownPage. Did I miss something?

[noha]

Foliage is from a time where the reading of microdown was in its infancy and the reading produced a pillar model.
Somehow this has changed without knowing why. Steph always says pillar is dead but I don't get what the document model behind reading microdown should be. Microdown itself? If we can clarify this I think a renaming will be necessary

[Ducasse]

Step by step is the answer. When I do not have much time, I favor step by step solutions. But I go from one step to the next one and deliver. Because I delivered.

• When I started microdown we converted the resulting md trees to pillar trees so that I could reuse the pillar format visitors.
• Then in a second step with time and effort I rewrote some of the pillar AST visitors on top of the Microdown AST.
  In the process I cleaned and simplified some logic such as the one of extended nodes.

Now we are missing

• to put in production the HTML microdown exporters,
• migrate the book tester from Pillar to microdown,
• migrate the templatedExporter (which was never used in Pillar but is really promising because we can template any node).

Then the pillar compilation chain of Pillar was extended to be able to manage .pillar doc with their respective visitors and .md with their respective visitors. This supports the automatic migration of full books from one format to the other ones.
The objective is to fade .pillar format. The architecture supports this because it is modular: the Pillar compilation chain does not rely on pillar trees (as it was in the first generation).

The goal is to be able to use Pillar without .pillar files.
This is why I ported most of the books from Pillar to Microdown (and this is not a small task).
I will continue to migrate the left ones. Today I migrated the voyage book.

So christophe I do not know foliage but probably that we should define a visitor on top of microdown trees.
May be the templatedExporter of microdown would make sense there because we can mustache any element (I should continue to migrate the pillar equivalent) else I imagine that there is a visitor on top of pillar trees that should be converted to a microdown visitor and the conversion from Microdown tree to Pillar tree should be stopped.

So I hope that this is clear.
My next step beside book migration is the integration of the PR of kasper on the new inline parser.