Ambiguous meaning of "Source" in the documentation

[gallandarakhneorg]

When opening the SARL documentation on www.sarl.io, we can see the "Spec" and "Source" tabs.

The meaning of "Source" may be ambiguous because the visitor may consider that it contains the source code of the tutorial example. She/he may be disappointed to obtain the code of the documentation specification (e.g. oral comment by @gbasso).

Is it possible to change the skin of the SARL documentation to avoid this problem?

[srodriguez]

That is actually generated by Jnario which we use to ensure the examples are tested.
AFAIK you can't change that via a Jnario config. We could however change it in the site generation in the same way we add the site's navbar.

I think it is interesting to be able to see the "Doc's spec and source".

What do you suggest, change tab's text or remove the second tab?

[gallandarakhneorg]

I think that removing the tabs is safe: the "Source" tab is interesting for the SARL's developers only, and the spec-source's syntax may difficult to understand for the others and not very useful.
In think that only the first tab ("Spec") will be really used by the SARL users.

[gallandarakhneorg]

The pull request sebastianbenz/Jnario#121 is providing source code patches that permits to hide the tabs from the Jnario Maven plugin's configuration.

[gallandarakhneorg]

@srodriguez seems to change the CSS for removing these tabs. That's great!