Replies: 2 comments 2 replies
-
|
We have versioning as a goal, although it will be while until we can implement. A very simple way of archiving copies of your content would be to create the folders The when you have another version of the content you want to version, make a Name the folders whatever you want. The above |
Beta Was this translation helpful? Give feedback.
-
|
Is there any trick to make retype do a sort of chroot to the version dir, so I could just copy the content of the old build and get everything as it was? |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure I 100% understand your request, but maybe passing an Something like: Is that what you mean? That would also mean copying the entire contents of your project into the Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
That's also good to know for the build step. Thank you. What I meant was: using the full build from an old version and copy it in Not sure that would be possible (probably not), but handling a base tag might solve the problem without reimplementing everything. |
Beta Was this translation helpful? Give feedback.
-
When used for documentation, it would be nice to have some way to link to old versions of the doc.
Currently github pages does not allow multiple version of the same doc, and that sucks, but retype could bypass that restriction e.g. including the old version(s) in the build.
Ideally, the config could include the possibility to build from an array of tags present in the repo, and there could be a component that shows a popup menu jumping to the old versions.
Beta Was this translation helpful? Give feedback.
All reactions