I used tabs to show different examples of YAML files, as suggested in #184. It looks great for an initial interactive approach.
I like the tabs over the dropdown because it gives the user a clear idea there are more than Sphinx and MkDocs tools supported, which is a good marketing strategy, in my opinion.
It also adds an "Others" option that's more generic and shows how to use build.commands in a generic way: install dependencies, build, copy assets under $READTHDOCS_OUTPUT directory.
I used tabs to show different examples of YAML files, as suggested in #184. It looks great for an initial interactive approach.
I like the tabs over the dropdown because it gives the user a clear idea there are more than Sphinx and MkDocs tools supported, which is a good marketing strategy, in my opinion.
It also adds an "Others" option that's more generic and shows how to use
build.commands
in a generic way: install dependencies, build, copy assets under$READTHDOCS_OUTPUT
directory.