#!/usr/bin/env python
# coding: utf-8

# # Markdown Cells

# Text can be added to IPython Notebooks using Markdown cells.  Markdown is a popular markup language that is a superset of HTML. Its specification can be found here:
# 
# <http://daringfireball.net/projects/markdown/>

# ## Markdown basics

# You can make text *italic* or **bold**.

# You can build nested itemized or enumerated lists:
# 
# * One
#     - Sublist
#         - This
#   - Sublist
#         - That
#         - The other thing
# * Two
#   - Sublist
# * Three
#   - Sublist
# 
# Now another list:
# 
# 1. Here we go
#     1. Sublist
#     2. Sublist
# 2. There we go
# 3. Now this

# You can add horizontal rules:
# 
# ---

# Here is a blockquote:
# 
# > Beautiful is better than ugly.
# > Explicit is better than implicit.
# > Simple is better than complex.
# > Complex is better than complicated.
# > Flat is better than nested.
# > Sparse is better than dense.
# > Readability counts.
# > Special cases aren't special enough to break the rules.
# > Although practicality beats purity.
# > Errors should never pass silently.
# > Unless explicitly silenced.
# > In the face of ambiguity, refuse the temptation to guess.
# > There should be one-- and preferably only one --obvious way to do it.
# > Although that way may not be obvious at first unless you're Dutch.
# > Now is better than never.
# > Although never is often better than *right* now.
# > If the implementation is hard to explain, it's a bad idea.
# > If the implementation is easy to explain, it may be a good idea.
# > Namespaces are one honking great idea -- let's do more of those!

# And shorthand for links:
# 
# [IPython's website](http://ipython.org)

# ## Headings

# If you want, you can add headings using Markdown's syntax:
# 
# # Heading 1
# # Heading 2
# ## Heading 2.1
# ## Heading 2.2

# **BUT most of the time you should use the Notebook's Heading Cells to organize your Notebook content**, as they provide meaningful structure that can be interpreted by other tools, not just large bold fonts.

# ## Embedded code

# You can embed code meant for illustration instead of execution in Python:
# 
#     def f(x):
#         """a docstring"""
#         return x**2
# 
# or other languages:
# 
#     if (i=0; i<n; i++) {
#       printf("hello %d\n", i);
#       x += 4;
#     }

# ## LaTeX equations

# Courtesy of MathJax, you can include mathematical expressions both inline: 
# $e^{i\pi} + 1 = 0$  and displayed:
# 
# $$e^x=\sum_{i=0}^\infty \frac{1}{i!}x^i$$

# ## Github flavored markdown (GFM)

# The Notebook webapp support Github flavored markdown meaning that you can use triple backticks for code blocks 
# <pre>
# ```python
# print "Hello World"
# ```
# 
# ```javascript
# console.log("Hello World")
# ```
# </pre>
# 
# Gives 
# ```python
# print "Hello World"
# ```
# 
# ```javascript
# console.log("Hello World")
# ```
# 
# And a table like this : 
# 
# <pre>
# | This | is   |
# |------|------|
# |   a  | table| 
# </pre>
# 
# A nice Html Table
# 
# | This | is   |
# |------|------|
# |   a  | table| 

# ## General HTML

# Because Markdown is a superset of HTML you can even add things like HTML tables:
# 
# <table>
# <tr>
# <th>Header 1</th>
# <th>Header 2</th>
# </tr>
# <tr>
# <td>row 1, cell 1</td>
# <td>row 1, cell 2</td>
# </tr>
# <tr>
# <td>row 2, cell 1</td>
# <td>row 2, cell 2</td>
# </tr>
# </table>

# ## Local files

# If you have local files in your Notebook directory, you can refer to these files in Markdown cells directly:
# 
#     [subdirectory/]<filename>
# 
# For example, in the images folder, we have the Python logo:
# 
#     <img src="../images/python_logo.svg" />
# 
# <img src="../images/python_logo.svg" />
# 
# and a video with the HTML5 video tag:
# 
#     <video controls src="images/animation.m4v" />
# 
# <video controls src="images/animation.m4v" />
# 
# These do not embed the data into the notebook file, and require that the files exist when you are viewing the notebook.

# ### Security of local files

# Note that this means that the IPython notebook server also acts as a generic file server
# for files inside the same tree as your notebooks.  Access is not granted outside the
# notebook folder so you have strict control over what files are visible, but for this
# reason it is highly recommended that you do not run the notebook server with a notebook
# directory at a high level in your filesystem (e.g. your home directory).
# 
# When you run the notebook in a password-protected manner, local file access is restricted
# to authenticated users unless read-only views are active.