Versionning selector

[Thomas-lhuillier]

Hello,

Any idea how a versioning selector could be implemented in Stylemark ?
I was thinking about something like on symfony docs.

Anyway, very good project. Keep up the good work.

[mpetrovich]

That’s a great question and a challenging one. In your mind, what would the ideal workflow be in terms of creating new versions?

[Thomas-lhuillier]

Maybe we could have a new parameter defined in the header block like this :

---
name: component name
category: category name
version: 1.0
---

Then we could rely on this to create a version selector, and hide/reveal pages from the navigation bar.

This seems like a 'simple' approach, but it forces us to have the docs for all versions in the same place.

[mpetrovich]

What should the workflow be for updating to a new version, say 2.0 in this example?

[Thomas-lhuillier]

For the case of dedicated markdown files it seems manageable to add new files for each version.
But for docs inside source code I don't know :/ duplicating comment blocks wouldn't be suited.

[Thomas-lhuillier]

You were originally asking me about "ideal" workflow. I would say ideal workflow for versioning would be to use git branches/tags to handle multiple versions.
Teams/individuals often maintain multiple git branches and/or tags to handle versions in their original projects.
Finding a solution that rely on this (or in which we could plug git branches) would be perfect.