testtheme 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: fb727dfcf6d9399f640eeedcafb3b380397e8852
+  data.tar.gz: 618d1ee5865ade38f1def4697445d33cc7d91d13
+SHA512:
+  metadata.gz: ee63de4b080ffaec924615d0053b213d5fe58350d3a74275d02dc718f410b08967dd79463eac1abff1045381141485c903a908e0a63c9c7b5e24fcea22e21511
+  data.tar.gz: 136fcef94910900489e12d804528f61ced5635229916c813259e4cd4c1442432695af3edaed770d62c5e3e9dcc0d9e15f2a5dd477ed5e39a2cd2b029f4c2f07e

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Lisa Carey
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,107 @@
+# testtheme
+
+(Lisa experiments with Jekyll themes...)
+
+Welcome to your new Jekyll theme! In this directory, you'll find the files you need to be able to package up your theme into a gem. Put your layouts in `_layouts`, your includes in `_includes` and your sass in `_sass`. To experiment with this code, add some sample content and run `bundle exec jekyll serve` – this directory is setup just like a Jekyll site!
+
+
+## Installation
+
+Add this line to your Jekyll site's `Gemfile`:
+
+```ruby
+gem "testtheme"
+```
+
+And add this line to your Jekyll site's `_config.yml`:
+
+```yaml
+theme: testtheme
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install testtheme
+
+## Usage
+
+You can make a few simple updates, add your docs, and have a site up and running, or you can make more extensive customizations.
+
+As with all gem-based Jekyll themes, the theme's layouts,  base styles, and include files like footers are stored in the theme-gem, hidden from your immediate view, though you can override any theme file by creating a file of the same name in your project. You can learn more about gem-based themes in the Jekyll [Themes](http://jekyllrb.com/docs/themes/) guide, including how to find, open, and override theme files.
+
+### Layouts
+
+The theme provides some basic layouts for you to use. Specify the appropriate layout in each new content file's Jekyll frontmatter to get the right headers, footers, navs, and so on:
+
+* `docs`: This is probably the most common layout you'll use, designed for all kinds of docs. Use with the `markdown` type for default styling for Markdown docs pages.
+```
+---
+layout: docs
+type: markdown
+---
+```
+
+* `faq`: Use for FAQs.
+* `landing`: Use for landing pages.
+* `blog`: Use for your main blog page.
+* `post`: Use for blog posts.
+* `community`: Use for your community page.
+* `about`: Use for your "about" page.
+
+#### Types
+
+The `type` value lets you further specify the styling you want to be used for a particular layout. If you're creating regular doc pages in Markdown, use the `markdown` type.
+
+
+### Images
+
+Add images, including your project logo in `/assets/img/`. Save your project logo as `/assets/img/logo.png`.
+
+### Style
+
+You can update site colors directly in `/assets/css/styles.scss`.
+
+For any other style updates, you'll need to override the relevant CSS in the theme styles (included in styles.scss): you can override any CSS rule in styles.scss, as indicated. To see what rules you'll need to override for particular style changes, see the files in the theme's `_sass` directory.
+
+### Navigation
+
+Nav bars for docs are autogenerated based on your file structure. So, for example, if you have docs in your_site_home/docs/tasks/foo and your_site_home/docs/tasks/bar, you'll get a Tasks left nav within Docs with two items, Foo and Bar.  Each doc should have a `title`, an `overview`, and an `order` value in its frontmatter for populating the nav bars and other autogenerated content:
+
+```
+---
+title: Overview
+overview: Provides a conceptual overview of Foo when used with Bar.
+                
+order: 0
+
+layout: docs
+type: markdown
+---
+```
+
+Docs will appear in the relevant nav in order of their `order` value.
+
+### Other material
+
+Use the `_config.yml` file to specify your project name, search engine, links to your Github project, and more - this information is used to populate your site's landing page, headers, and footers.
+
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/LisaFC/testtheme. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## Development
+
+To set up your environment to develop this theme, run `bundle install`.
+
+Your theme is setup just like a normal Jekyll site! To test your theme, run `bundle exec jekyll serve` and open your browser at `http://localhost:4000`. This starts a Jekyll server using your theme. Add pages, documents, data, etc. like normal to test your theme's contents. As you make modifications to your theme and to your content, your site will regenerate and you should see the changes in the browser after a refresh, just like normal.
+
+When your theme is released, only the files in `_layouts`, `_includes`, and `_sass` tracked with Git will be released.
+
+## License
+
+The theme is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/README.md~

@@ -0,0 +1,111 @@
+# testtheme
+<<<<<<< HEAD
+
+Welcome to your new Jekyll theme! In this directory, you'll find the files you need to be able to package up your theme into a gem. Put your layouts in `_layouts`, your includes in `_includes` and your sass in `_sass`. To experiment with this code, add some sample content and run `bundle exec jekyll serve` – this directory is setup just like a Jekyll site!
+
+Lisa experiments with BIG THEMES, like some sort of turn of the century novelist.
+
+## Installation
+
+Add this line to your Jekyll site's `Gemfile`:
+
+```ruby
+gem "testtheme"
+```
+
+And add this line to your Jekyll site's `_config.yml`:
+
+```yaml
+theme: testtheme
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install testtheme
+
+## Usage
+
+You can make a few simple updates, add your docs, and have a site up and running, or you can make more extensive customizations.
+
+As with all gem-based Jekyll themes, the theme's layouts,  base styles, and include files like footers are stored in the theme-gem, hidden from your immediate view, though you can override any theme file by creating a file of the same name in your project. You can learn more about gem-based themes in the Jekyll [Themes](http://jekyllrb.com/docs/themes/) guide, including how to find, open, and override theme files.
+
+### Layouts
+
+The theme provides some basic layouts for you to use. Specify the appropriate layout in each new content file's Jekyll frontmatter to get the right headers, footers, navs, and so on:
+
+* `docs`: This is probably the most common layout you'll use, designed for all kinds of docs. Use with the `markdown` type for default styling for Markdown docs pages.
+```
+---
+layout: docs
+type: markdown
+---
+```
+
+* `faq`: Use for FAQs.
+* `landing`: Use for landing pages.
+* `blog`: Use for your main blog page.
+* `post`: Use for blog posts.
+* `community`: Use for your community page.
+* `about`: Use for your "about" page.
+
+#### Types
+
+The `type` value lets you further specify the styling you want to be used for a particular layout. If you're creating regular doc pages in Markdown, use the `markdown` type.
+
+
+### Images
+
+Add images, including your project logo in `/assets/img/`. Save your project logo as `/assets/img/logo.png`.
+
+### Style
+
+You can update site colors directly in `/assets/css/styles.scss`.
+
+For any other style updates, you'll need to override the relevant CSS in the theme styles (included in styles.scss): you can override any CSS rule in styles.scss, as indicated. To see what rules you'll need to override for particular style changes, see the files in the theme's `_sass` directory.
+
+### Navigation
+
+Nav bars for docs are autogenerated based on your file structure. So, for example, if you have docs in your_site_home/docs/tasks/foo and your_site_home/docs/tasks/bar, you'll get a Tasks left nav within Docs with two items, Foo and Bar.  Each doc should have a `title`, an `overview`, and an `order` value in its frontmatter for populating the nav bars and other autogenerated content:
+
+```
+---
+title: Overview
+overview: Provides a conceptual overview of Foo when used with Bar.
+                
+order: 0
+
+layout: docs
+type: markdown
+---
+```
+
+Docs will appear in the relevant nav in order of their `order` value.
+
+### Other material
+
+Use the `_config.yml` file to specify your project name, search engine, links to your Github project, and more - this information is used to populate your site's landing page, headers, and footers.
+
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/LisaFC/testtheme. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## Development
+
+To set up your environment to develop this theme, run `bundle install`.
+
+Your theme is setup just like a normal Jekyll site! To test your theme, run `bundle exec jekyll serve` and open your browser at `http://localhost:4000`. This starts a Jekyll server using your theme. Add pages, documents, data, etc. like normal to test your theme's contents. As you make modifications to your theme and to your content, your site will regenerate and you should see the changes in the browser after a refresh, just like normal.
+
+When your theme is released, only the files in `_layouts`, `_includes`, and `_sass` tracked with Git will be released.
+
+## License
+
+The theme is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+=======
+Lisa tests Jekyll themes for fun and not-profit
+>>>>>>> 7ac9c0113c9eef0911e2da76721b9e1a5ee2e16e

data/_includes/contribute-links.html

@@ -0,0 +1,11 @@
+<div class="contribute-links pull-right">
+	<a href="https://github.com/istio/istio.github.io/edit/master/{{page.path}}" data-toggle="tooltip" data-placement="left" title="Edit this page on GitHub">
+		<i class="fa fa-lg fa-pencil"></i>
+	</a>
+</div>
+
+<script>
+	$(document).ready(function() {
+		$('[data-toggle="tooltip"]').tooltip()
+	});
+</script>

data/_includes/doc-side-nav.html

@@ -0,0 +1,62 @@
+<ul class="doc-side-nav">
+
+	{% assign components = page.path | downcase | split: '/' %}
+	{% assign section = components[1] %}
+	{% assign foundSection = false %}
+
+	{% assign docs = site.docs %}
+	{% for d in docs %}
+		{% assign components = d.path | downcase | split: '/' %}
+		{% if components[1] == section %}
+			{% if components[2] == 'index.md' %}
+	            {% assign foundSection = true %}
+				<li><h5 class='doc-side-nav-title'>{{d.title}}</h5></li>
+			{% endif %}
+		{% endif %}
+	{% endfor %}
+
+	{% if foundSection == true %}
+	<script type="text/javascript">
+        var docs = [];
+        {% for d in docs %}
+	        {% assign components = d.path | downcase | split: '/' %}
+			{% if components[1] == section %}
+		        docs.push({path: [
+		        {% for comp in components %}
+        			{% if forloop.index > 2 %}
+        				"{{ comp }}",
+        			{% endif %}
+        		{% endfor %}
+				{% assign order = d.order %}
+				{% if d.order == nil %}
+				{% assign order = 9999 %}
+				{% endif %}
+        		], url: "{{d.url}}", title: "{{d.title}}", order: {{order}}, overview: "{{d.overview}}"});
+			{% endif %}
+        {% endfor %}
+
+		genNavBarTree(docs)
+	</script>
+	{% endif %}
+</ul>
+
+<style>
+    .tree li { padding-left: 20px; }
+    .tree-toggle {
+        cursor: pointer;
+		margin-left: -1em;
+    }
+</style>
+
+<script type="text/javascript">
+(function($) {
+	$(document).ready(function() {
+		/* toggle category tree */
+		$(document).on('click', '.tree-toggle', function () {
+			$(this).children('i.fa').toggleClass('fa-caret-right');
+			$(this).children('i.fa').toggleClass('fa-caret-down');
+			$(this).parent().children('ul.tree').toggle(200);
+		});
+	});
+}(jQuery));
+</script>

data/_includes/doc-top-nav.html

@@ -0,0 +1,17 @@
+<div class="container">
+	<div class="row">
+		<div class="col-md-11 nofloat center-block" style="margin-top: 3px;">
+			<ul class="col-sm-10 nav nav-tabs">
+				{% assign cats = site.docs | where:"index","true" | sort:"order" %}
+				{% for cat in cats %}
+					{% assign cat_path  = cat.url | downcase | split: '/' %}
+					{% assign page_path = page.url | downcase | split: '/' %}
+					{% assign cat_name = cat.title | default: "EMPTY" %}
+					{% if cat_name != "EMPTY" %}
+					<li role="presentation" {% if cat_path[2] == page_path[2] %}class='active'{% endif %}><a href="{{home}}{{ cat.url }}">{{ cat_name }}</a></li>
+					{% endif %}
+				{% endfor %}
+			</ul>
+		</div>
+	</div>
+</div>

data/_includes/figure.html

@@ -0,0 +1,22 @@
+{% if include.max-width %}
+{% assign max-width = include.max-width %}
+{% else %}
+{% assign max-width = "75%" %}
+{% endif %}
+
+{% if include.title %}
+{% assign title = include.title %}
+{% else %}
+{% assign title = include.alt %}
+{% endif %}
+
+{% if include.caption %}
+{% assign caption = include.caption %}
+{% else %}
+{% assign caption = title %}
+{% endif %}
+
+<figure style="text-align: center; margin-top:20px; margin-bottom:20px;">
+    <img src="{{include.file}}" style="max-width: {{max-width}};" title="{{title}}" alt="{{include.alt}}"/>
+    <figcaption style="margin-top:10px;">{{caption}}</figcaption>
+</figure>

data/_includes/footer.html

@@ -0,0 +1,51 @@
+<footer>
+    <div class="container">
+        <div class="row">
+            <div class="col-md-2"></div>
+            <div class="col-md-3 col-sm-4 col-xs-12 center-block">
+                <ul class="toggle">
+                    <p class="header">Docs</p>
+                    <li><a href="{{home}}/docs/">Welcome</a></li>
+		            <li><a href="{{home}}/docs/concepts">Concepts</a></li>
+                    <li><a href="{{home}}/docs/tasks">Tasks</a></li>
+                    <li><a href="{{home}}/docs/samples">Samples</a></li>
+                    <li><a href="{{home}}/docs/reference">Reference</a></li>
+                </ul>
+            </div>
+
+            <hr class="footer-sections" />
+
+            <div class="col-md-3 col-sm-4 col-xs-12 center-block">
+                <ul class="toggle">
+                    <p class="header">Resources</p>
+                    <li><a href="{{home}}/faq">Frequently Asked Questions</a></li>
+                    <li><a href="{{home}}/troubleshooting">Troubleshooting Guide</a></li>
+                    <li><a href="{{home}}/bugs">Report a Bug</a></li>
+                    <li><a href="https://github.com/istio/istio.github.io/issues/new?title=Issue with {{page.path}}">Report a Doc Issue</a></li>
+                    <li><a href="https://github.com/istio/istio.github.io/edit/master/{{page.path}}">Edit This Page on GitHub</a></li>
+                </ul>
+            </div>
+
+            <hr class="footer-sections" />
+
+            <div class="col-md-3 col-sm-4 col-xs-12 center-block">
+                <ul class="toggle">
+                    <p class="header">Community</p>
+                    <li><a href="{{site.stackoverflow_link}}" target="_blank"><span class="stack-overflow">Stack Overflow</span></a></li>
+                    <li><a href="{{site.user_mailing_lin}}" target="_blank"><span class="group">User</span></a> | <a href="{{site.dev_mailing_link}}" target="_blank">Dev Mailing Lists</a></li>
+                    <li><a href="{{site.slack_link}}" target="_blank"><span class="slack">Slack</span></a></li>
+                    <li><a href="{{site.github_link}}" target="_blank"><span class="github">GitHub</span></a></li>
+                </ul>
+            </div>
+
+            <div class="col-md-1"></div>
+        </div>
+
+        <div class="row">
+            <p class="description small text-center">
+                {{site.copyright_notice}}<br>
+                This site was built on {{site.time | date_to_string | split: ' ' | join: '-'}}
+            </p>
+        </div>
+    </div>
+</footer>

data/_includes/footer.html~

@@ -0,0 +1,52 @@
+<footer>
+    <div class="container">
+        <div class="row">
+            <div class="col-md-2"></div>
+            <div class="col-md-3 col-sm-4 col-xs-12 center-block">
+                <ul class="toggle">
+                    <p class="header">Docs</p>
+                    <li><a href="{{home}}/docs/">Welcome</a></li>
+		            <li><a href="{{home}}/docs/concepts">Concepts</a></li>
+                    <li><a href="{{home}}/docs/tasks">Tasks</a></li>
+                    <li><a href="{{home}}/docs/samples">Samples</a></li>
+                    <li><a href="{{home}}/docs/reference">Reference</a></li>
+                </ul>
+            </div>
+
+            <hr class="footer-sections" />
+
+            <div class="col-md-3 col-sm-4 col-xs-12 center-block">
+                <ul class="toggle">
+                    <p class="header">Resources</p>
+                    <li><a href="{{home}}/faq">Frequently Asked Questions</a></li>
+                    <li><a href="{{home}}/troubleshooting">Troubleshooting Guide</a></li>
+                    <li><a href="{{home}}/bugs">Report a Bug</a></li>
+                    <li><a href="https://github.com/istio/istio.github.io/issues/new?title=Issue with {{page.path}}">Report a Doc Issue</a></li>
+                    <li><a href="https://github.com/istio/istio.github.io/edit/master/{{page.path}}">Edit This Page on GitHub</a></li>
+                </ul>
+            </div>
+
+            <hr class="footer-sections" />
+
+            <div class="col-md-3 col-sm-4 col-xs-12 center-block">
+                <ul class="toggle">
+                    <p class="header">Community</p>
+                    <li><a href="{{site.stackoverflow_link}}" target="_blank"><span class="stack-overflow">Stack Overflow</span></a></li>
+                    <li><a href="{{site.user_mailing_lin}}" target="_blank"><span class="group">User</span></a> | <a href="{{site.dev_mailing_link}}" target="_blank">Dev Mailing Lists</a></li>
+                    <li><a href="{{site.slack_link}}" target="_blank"><span class="slack">Slack</span></a></li>
+                    <li><a href="{{site.github_link}}" target="_blank"><span class="github">GitHub</span></a></li>
+                </ul>
+            </div>
+
+            <div class="col-md-1"></div>
+        </div>
+
+        <div class="row">
+            <p class="description small text-center">
+                Copyright &copy; 2017 Istio Authors<br>
+                Istio Version 0.1<br>
+                This site was built on {{site.time | date_to_string | split: ' ' | join: '-'}}
+            </p>
+        </div>
+    </div>
+</footer>