conditional paragraph visibility based on selected language

[slatedocs]

conditional paragraph visibility based on selected language

[bootstraponline]

Possible implementation:

diff --git a/source/javascripts/app/lang.js b/source/javascripts/app/lang.js
index 7f1bcdb..e5170ca 100644
--- a/source/javascripts/app/lang.js
+++ b/source/javascripts/app/lang.js
@@ -21,13 +21,14 @@ under the License.

   function activateLanguage(language) {
     if (!language) return;
-
     $("#lang-selector a").removeClass('active');
     $("#lang-selector a[data-language-name='" + language + "']").addClass('active');
     for (var i=0; i < languages.length; i++) {
       $(".highlight." + languages[i]).hide();
+      $(".desc." + languages[i]).hide();
     }
     $(".highlight." + language).show();
+    $(".desc." + language).show();
   }

   function setupLanguages(l) {

[bootstraponline]

I added this for the tutorial I'm working on. If there's a better way, I'd be interested to know.

• appium-boneyard/tutorial@a481824
• appium@a55146f
• middleman/middleman#1278

[bootstraponline]

Updated implementation to use simple tags. I had to modify the CSS a bit because slate wasn't happy that the content existed inside a span.

[lord]

Hmm, I can take a closer look at this this week. I think if we make everything have the same class, that would be faster, since it means jQuery doesn't have to search over the entire page twice.

[lord]

In a similar way to the suggestion by @bootstraponline, we've ended up implementing a lang-specific class, which you can use like this:

<p class="lang-specific ruby shell">
only show for ruby and shell languages
</p>

To use this feature, you need to write HTML instead of markdown, but we expect that this will be a rare-enough feature that this is an okay compromise.