Comments (5)
I think this would be a very nice feature. For Stryker4s, there's been some confusion about what config option was introduced in which version, though we've now 'solved' that by adding a since
to each config option.
I don't think it'd work out of the box with Docusaurus. It expects 1 set of docs of the whole site per version. Which works best if there's 1 project that you want to make versioned docs for. We could make some sort of script to get the docs of each Stryker repo per the last x tags, but then what version do you use for Stryker-JS if you're looking at the version Stryker4s-v0.13.0? Whatever it is the script or setup probably won't be super simple.
If we go for this, we should also follow some of the best practices mentioned on Docusaurus. Namely, the 'current' always being the latest (untagged) version of the docs, and not having too many versions per framework (5 per framework sounds reasonable to me).
from stryker-mutator.github.io.
I think it might be possible after all. Look at page: https://docusaurus.io/docs/docs-multi-instance
Docusaurus says they have multiple instances themselves. One instance is versioned. Another is not. So it might be possible to have multiple instances that are all versioned?
from stryker-mutator.github.io.
At worst we can use a 'current' and a 'vnext' instead of specific version numbers. This should cover most use cases and should be applicable to all of us.
from stryker-mutator.github.io.
I have mixed feelings about this. Sure it is nice for people that are looking for a specific version. However, I see a couple of disadvantages.
- If you're on an older version, you should probably upgrade to the latest version. Using 1 set of docs with a
since
might entice users to migrate sooner, because they would more easily spot new features. - There are a lot of reasons to update the docs besides new features or breaking changes. I think that about 80% of changes in the stryker-js docs are general documentation improvements. They are also relevant for older versions. However, I don't want to have the burden of updating the same text in a lot of documents 🤷♀️
With that being said, we can still move forward with this change as long as it is optional per Stryker framework.
from stryker-mutator.github.io.
@nicojs The biggest issue is that currently the website often has docs that are not yet valid, because we have not yet released a new stryker version. Because of this we created a long living branch for our v1 release but this has once again proven that long living branches are a mistake. We don't want to have to make this mistake in the future, and thus we need at least 2 sets of docs (current and vnext).
from stryker-mutator.github.io.
Related Issues (20)
- Stryker timeline HOT 4
- Enrich blogs with authors and labels HOT 3
- Enrich blogs with comments section.. ? HOT 3
- Use Glitch for interactive example on landing page HOT 2
- Make it easier to link to specific sections HOT 3
- Load documentation from github sources HOT 3
- Special character not rendered correctly HOT 3
- Integrating Stryker.NET in your azure pipelines post could be updated HOT 1
- Migrate website to Docusaurus HOT 6
- Support canonical urls HOT 1
- unnecessary mutation for JavaScript && operator
- Some feedback from a frontend dev HOT 3
- Running stryker only on changed code HOT 2
- Rename Stryker to StrykerJS
- Broken link HOT 1
- Dependency Dashboard
- Navigation to generic docs missing from nav bar HOT 1
- Support for vitest HOT 1
- Example that doesn't directly refer to alcohol? HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from stryker-mutator.github.io.