[
  {
      "model": "auth.group",
      "pk": 1,
      "fields": {
          "name": "Django-Wiki",
          "permissions": [
              25,
              26,
              27,
              28,
              5,
              6,
              7,
              8,
              1,
              2,
              3,
              4,
              9,
              10,
              11,
              12,
              13,
              14,
              15,
              16,
              41,
              42,
              43,
              44,
              33,
              34,
              35,
              36,
              37,
              38,
              39,
              40,
              45,
              46,
              47,
              48,
              17,
              18,
              19,
              20,
              21,
              22,
              23,
              24,
              29,
              30,
              31,
              32,
              49,
              54,
              50,
              51,
              55,
              53,
              52,
              56,
              57,
              58,
              59,
              60,
              61,
              62,
              63,
              64,
              65,
              66,
              67,
              68,
              69,
              70,
              71,
              72,
              73,
              74,
              75,
              76,
              77,
              78,
              79,
              80,
              81,
              82,
              83,
              84,
              85,
              86,
              87,
              96,
              97,
              98,
              99,
              100,
              101,
              102,
              103,
              88,
              89,
              90,
              91,
              92,
              93,
              94,
              95,
              104,
              105,
              106,
              107
          ]
      }
  },
  {
      "model": "auth.user",
      "pk": 1,
      "fields": {
          "password": "",
          "last_login": "2023-01-31T22:26:17Z",
          "is_superuser": true,
          "username": "djangowiki",
          "first_name": "Django",
          "last_name": "Wiki",
          "email": "admin@django-wiki.org",
          "is_staff": true,
          "is_active": true,
          "date_joined": "2023-01-31T22:25:55Z",
          "groups": [1],
          "user_permissions": []
      }
  },
  {
      "model": "auth.user",
      "pk": 2,
      "fields": {
          "password": "pbkdf2_sha256$390000$1qTkKmWW2h6zE8lKTDtwYo$2WlKlalmK5iNBa+KZzfDo+hFZWoBhSECf8MtM7BseQQ=",
          "last_login": "2023-01-31T22:29:59Z",
          "is_superuser": true,
          "username": "admin",
          "first_name": "Public",
          "last_name": "Test",
          "email": "test@django-wiki.org",
          "is_staff": true,
          "is_active": true,
          "date_joined": "2023-01-31T22:18:24Z",
          "groups": [1],
          "user_permissions": []
      }
  },
  {
      "model": "sites.site",
      "pk": 1,
      "fields": {
          "domain": "demo.django-wiki.org",
          "name": "Django Wiki"
      }
  },
  {
      "model": "django_nyt.notificationtype",
      "pk": "article_edit",
      "fields": {
          "label": null,
          "content_type": 13
      }
  },
  {
      "model": "django_nyt.settings",
      "pk": 1,
      "fields": {
          "user": 1,
          "interval": 0,
          "is_default": true,
          "created": "2023-01-31T22:18:24Z",
          "modified": "2023-01-31T22:18:24Z"
      }
  },
  {
      "model": "django_nyt.settings",
      "pk": 2,
      "fields": {
          "user": 2,
          "interval": 0,
          "is_default": true,
          "created": "2023-01-31T22:18:24Z",
          "modified": "2023-01-31T22:18:24Z"
      }
  },
  {
      "model": "django_nyt.subscription",
      "pk": 1,
      "fields": {
          "settings": 1,
          "notification_type": "article_edit",
          "object_id": "1",
          "send_emails": true,
          "latest": null,
          "created": "2023-01-31T22:18:24Z",
          "modified": "2023-01-31T22:18:24Z",
          "last_sent": null
      }
  },
  {
      "model": "thumbnail.kvstore",
      "pk": "sorl-thumbnail||image||0b374997f63ceb3dc5f426802eaa10f3",
      "fields": {
          "value": "{\"name\": \"wiki/images/1/a1b5813b5f934663a502c727230c700b/djangowikilogo.png\", \"storage\": \"django.core.files.storage.FileSystemStorage\", \"size\": [200, 200]}"
      }
  },
  {
      "model": "thumbnail.kvstore",
      "pk": "sorl-thumbnail||image||5dd2fc0933543ce905dd6be33c7be4c4",
      "fields": {
          "value": "{\"name\": \"cache/a9/12/a91201346f79fbe35e41c0006d97e6d4.jpg\", \"storage\": \"django.core.files.storage.FileSystemStorage\", \"size\": [50, 50]}"
      }
  },
  {
      "model": "thumbnail.kvstore",
      "pk": "sorl-thumbnail||thumbnails||0b374997f63ceb3dc5f426802eaa10f3",
      "fields": {
          "value": "[\"5dd2fc0933543ce905dd6be33c7be4c4\"]"
      }
  },
  {
      "model": "wiki.article",
      "pk": 1,
      "fields": {
          "current_revision": 1,
          "created": "2023-01-31T22:22:16.761Z",
          "modified": "2023-01-31T22:39:37.418Z",
          "owner": 1,
          "group": 1,
          "group_read": true,
          "group_write": true,
          "other_read": true,
          "other_write": false
      }
  },
  {
      "model": "wiki.article",
      "pk": 2,
      "fields": {
          "current_revision": 2,
          "created": "2023-01-31T22:37:06.461Z",
          "modified": "2023-01-31T22:38:40.663Z",
          "owner": null,
          "group": null,
          "group_read": true,
          "group_write": true,
          "other_read": true,
          "other_write": false
      }
  },
  {
      "model": "wiki.articleforobject",
      "pk": 1,
      "fields": {
          "article": 1,
          "content_type": 21,
          "object_id": 1,
          "is_mptt": true
      }
  },
  {
      "model": "wiki.articleforobject",
      "pk": 2,
      "fields": {
          "article": 2,
          "content_type": 21,
          "object_id": 2,
          "is_mptt": true
      }
  },
  {
      "model": "wiki.articlerevision",
      "pk": 1,
      "fields": {
          "revision_number": 1,
          "user_message": "Root Article",
          "automatic_log": "Article locked for editing",
          "ip_address": null,
          "user": 1,
          "modified": "2023-01-31T22:39:37.419Z",
          "created": "2023-01-31T22:24:07.716Z",
          "previous_revision": null,
          "deleted": false,
          "locked": true,
          "article": 1,
          "content": "[image:1 align:right]\r\n    This could be the logo\r\n\r\n_**Welcome to the django-wiki test site!**_\r\n\r\nTo test the wiki, please create new articles below this article or edit existing ones.\r\n\r\nOther resources:\r\n\r\n- [Visit the project on Github](https://github.com/benjaoming/django-wiki/)\r\n- [Google group for support](https://groups.google.com/forum/#!forum/django-wiki)\r\n\r\n# Markdown: Syntax\r\n\r\n[TOC]\r\n\r\n### Philosophy\r\n\r\nMarkdown is intended to be as easy-to-read and easy-to-write as is feasible.\r\n\r\nReadability, however, is emphasized above all else. A Markdown-formatted\r\ndocument should be publishable as-is, as plain text, without looking\r\nlike it's been marked up with tags or formatting instructions. While\r\nMarkdown's syntax has been influenced by several existing text-to-HTML\r\nfilters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4],\r\n[Grutatext] [5], and [EtText] [6] -- the single biggest source of\r\ninspiration for Markdown's syntax is the format of plain text email.\r\n\r\nEditing\r\n\r\n  [1]: http://docutils.sourceforge.net/mirror/setext.html\r\n  [2]: http://www.aaronsw.com/2002/atx/\r\n  [3]: http://textism.com/tools/textile/\r\n  [4]: http://docutils.sourceforge.net/rst.html\r\n  [5]: http://www.triptico.com/software/grutatxt.html\r\n  [6]: http://ettext.taint.org/doc/\r\n\r\nTo this end, Markdown's syntax is comprised entirely of punctuation\r\ncharacters, which punctuation characters have been carefully chosen so\r\nas to look like what they mean. E.g., asterisks around a word actually\r\nlook like \\*emphasis\\*. Markdown lists look like, well, lists. Even\r\nblockquotes look like quoted passages of text, assuming you've ever\r\nused email.\r\n\r\n### Automatic Escaping for Special Characters\r\n\r\nIn HTML, there are two characters that demand special treatment: `<`\r\nand `&`. Left angle brackets are used to start tags; ampersands are\r\nused to denote HTML entities. If you want to use them as literal\r\ncharacters, you must escape them as entities, e.g. `&lt;`, and\r\n`&amp;`.\r\n\r\nAmpersands in particular are bedeviling for web writers. If you want to\r\nwrite about 'AT&T', you need to write '`AT&amp;T`'. You even need to\r\nescape ampersands within URLs. Thus, if you want to link to:\r\n\r\n    http://images.google.com/images?num=30&q=larry+bird\r\n\r\nyou need to encode the URL as:\r\n\r\n    http://images.google.com/images?num=30&amp;q=larry+bird\r\n\r\nin your anchor tag `href` attribute. Needless to say, this is easy to\r\nforget, and is probably the single most common source of HTML validation\r\nerrors in otherwise well-marked-up web sites.\r\n\r\nMarkdown allows you to use these characters naturally, taking care of\r\nall the necessary escaping for you. If you use an ampersand as part of\r\nan HTML entity, it remains unchanged; otherwise it will be translated\r\ninto `&amp;`.\r\n\r\nSo, if you want to include a copyright symbol in your article, you can write:\r\n\r\n    &copy;\r\n\r\nand Markdown will leave it alone. But if you write:\r\n\r\n    AT&T\r\n\r\nMarkdown will translate it to:\r\n\r\n    AT&amp;T\r\n\r\nSimilarly, because Markdown supports [inline HTML](#html), if you use\r\nangle brackets as delimiters for HTML tags, Markdown will treat them as\r\nsuch. But if you write:\r\n\r\n    4 < 5\r\n\r\nMarkdown will translate it to:\r\n\r\n    4 &lt; 5\r\n\r\nHowever, inside Markdown code spans and blocks, angle brackets and\r\nampersands are *always* encoded automatically. This makes it easy to use\r\nMarkdown to write about HTML code. (As opposed to raw HTML, which is a\r\nterrible format for writing about HTML syntax, because every single `<`\r\nand `&` in your example code needs to be escaped.)\r\n\r\n\r\n* * *\r\n\r\n\r\n## Block Elements\r\n\r\n### Paragraphs and Line Breaks\r\n\r\nA paragraph is simply one or more consecutive lines of text, separated\r\nby one or more blank lines. (A blank line is any line that looks like a\r\nblank line -- a line containing nothing but spaces or tabs is considered\r\nblank.) Normal paragraphs should not be indented with spaces or tabs.\r\n\r\nThe implication of the \"one or more consecutive lines of text\" rule is\r\nthat Markdown supports \"hard-wrapped\" text paragraphs. This differs\r\nsignificantly from most other text-to-HTML formatters (including Movable\r\nType's \"Convert Line Breaks\" option) which translate every line break\r\ncharacter in a paragraph into a `<br />` tag.\r\n\r\nWhen you *do* want to insert a `<br />` break tag using Markdown, you\r\nend a line with two or more spaces, then type return.\r\n\r\nYes, this takes a tad more effort to create a `<br />`, but a simplistic\r\n\"every line break is a `<br />`\" rule wouldn't work for Markdown.\r\nMarkdown's email-style [blockquoting][bq] and multi-paragraph [list items][l]\r\nwork best -- and look better -- when you format them with hard breaks.\r\n\r\n  [bq]: #blockquote\r\n  [l]:  #list\r\n\r\n### Headers\r\n\r\nMarkdown supports two styles of headers, [Setext] [1] and [atx] [2].\r\n\r\nSetext-style headers are \"underlined\" using equal signs (for first-level\r\nheaders) and dashes (for second-level headers). For example:\r\n\r\n    This is an H1\r\n    =============\r\n\r\n    This is an H2\r\n    -------------\r\n\r\n    This is an H3\r\n    _____________\r\n\r\nAny number of underlining `=`'s or `-`'s will work.\r\n\r\nAtx-style headers use 1-6 hash characters at the start of the line,\r\ncorresponding to header levels 1-6. For example:\r\n\r\n    # This is an H1\r\n\r\n    ## This is an H2\r\n\r\n    ###### This is an H6\r\n\r\nOptionally, you may \"close\" atx-style headers. This is purely\r\ncosmetic -- you can use this if you think it looks better. The\r\nclosing hashes don't even need to match the number of hashes\r\nused to open the header. (The number of opening hashes\r\ndetermines the header level.) :\r\n\r\n    # This is an H1 #\r\n\r\n    ## This is an H2 ##\r\n\r\n    ### This is an H3 ######\r\n\r\n\r\n### Blockquotes\r\n\r\nMarkdown uses email-style `>` characters for blockquoting. If you're\r\nfamiliar with quoting passages of text in an email message, then you\r\nknow how to create a blockquote in Markdown. It looks best if you hard\r\nwrap the text and put a `>` before every line:\r\n\r\n    > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\r\n    > consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\r\n    > Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\r\n    > \r\n    > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\r\n    > id sem consectetuer libero luctus adipiscing.\r\n\r\nMarkdown allows you to be lazy and only put the `>` before the first\r\nline of a hard-wrapped paragraph:\r\n\r\n    > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,\r\n    consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.\r\n    Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.\r\n\r\n    > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse\r\n    id sem consectetuer libero luctus adipiscing.\r\n\r\nBlockquotes can be nested (i.e. a blockquote-in-a-blockquote) by\r\nadding additional levels of `>`:\r\n\r\n    > This is the first level of quoting.\r\n    >\r\n    > > This is nested blockquote.\r\n    >\r\n    > Back to the first level.\r\n\r\nBlockquotes can contain other Markdown elements, including headers, lists,\r\nand code blocks:\r\n\r\n\t> ## This is a header.\r\n\t> \r\n\t> 1.   This is the first list item.\r\n\t> 2.   This is the second list item.\r\n\t> \r\n\t> Here's some example code:\r\n\t> \r\n\t>     return shell_exec(\"echo $input | $markdown_script\");\r\n\r\nAny decent text editor should make email-style quoting easy. For\r\nexample, with BBEdit, you can make a selection and choose Increase\r\nQuote Level from the Text menu.\r\n\r\n\r\n### Lists\r\n\r\nMarkdown supports ordered (numbered) and unordered (bulleted) lists.\r\n\r\nUnordered lists use asterisks, pluses, and hyphens -- interchangably\r\n-- as list markers:\r\n\r\n    *   Red\r\n    *   Green\r\n    *   Blue\r\n\r\nis equivalent to:\r\n\r\n    +   Red\r\n    +   Green\r\n    +   Blue\r\n\r\nand:\r\n\r\n    -   Red\r\n    -   Green\r\n    -   Blue\r\n\r\nOrdered lists use numbers followed by periods:\r\n\r\n    1.  Bird\r\n    2.  McHale\r\n    3.  Parish\r\n\r\nIt's important to note that the actual numbers you use to mark the\r\nlist have no effect on the HTML output Markdown produces. The HTML\r\nMarkdown produces from the above list is:\r\n\r\n    <ol>\r\n    <li>Bird</li>\r\n    <li>McHale</li>\r\n    <li>Parish</li>\r\n    </ol>\r\n\r\nIf you instead wrote the list in Markdown like this:\r\n\r\n    1.  Bird\r\n    1.  McHale\r\n    1.  Parish\r\n\r\nor even:\r\n\r\n    3. Bird\r\n    1. McHale\r\n    8. Parish\r\n\r\nyou'd get the exact same HTML output. The point is, if you want to,\r\nyou can use ordinal numbers in your ordered Markdown lists, so that\r\nthe numbers in your source match the numbers in your published HTML.\r\nBut if you want to be lazy, you don't have to.\r\n\r\nIf you do use lazy list numbering, however, you should still start the\r\nlist with the number 1. At some point in the future, Markdown may support\r\nstarting ordered lists at an arbitrary number.\r\n\r\nList markers typically start at the left margin, but may be indented by\r\nup to three spaces. List markers must be followed by one or more spaces\r\nor a tab.\r\n\r\nTo make lists look nice, you can wrap items with hanging indents:\r\n\r\n    *   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\r\n        Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\r\n        viverra nec, fringilla in, laoreet vitae, risus.\r\n    *   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\r\n        Suspendisse id sem consectetuer libero luctus adipiscing.\r\n\r\nBut if you want to be lazy, you don't have to:\r\n\r\n    *   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.\r\n    Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,\r\n    viverra nec, fringilla in, laoreet vitae, risus.\r\n    *   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.\r\n    Suspendisse id sem consectetuer libero luctus adipiscing.\r\n\r\nIf list items are separated by blank lines, Markdown will wrap the\r\nitems in `<p>` tags in the HTML output. For example, this input:\r\n\r\n    *   Bird\r\n    *   Magic\r\n\r\nwill turn into:\r\n\r\n    <ul>\r\n    <li>Bird</li>\r\n    <li>Magic</li>\r\n    </ul>\r\n\r\nBut this:\r\n\r\n    *   Bird\r\n\r\n    *   Magic\r\n\r\nwill turn into:\r\n\r\n    <ul>\r\n    <li><p>Bird</p></li>\r\n    <li><p>Magic</p></li>\r\n    </ul>\r\n\r\nList items may consist of multiple paragraphs. Each subsequent\r\nparagraph in a list item must be indented by either 4 spaces\r\nor one tab:\r\n\r\n    1.  This is a list item with two paragraphs. Lorem ipsum dolor\r\n        sit amet, consectetuer adipiscing elit. Aliquam hendrerit\r\n        mi posuere lectus.\r\n\r\n        Vestibulum enim wisi, viverra nec, fringilla in, laoreet\r\n        vitae, risus. Donec sit amet nisl. Aliquam semper ipsum\r\n        sit amet velit.\r\n\r\n    2.  Suspendisse id sem consectetuer libero luctus adipiscing.\r\n\r\nIt looks nice if you indent every line of the subsequent\r\nparagraphs, but here again, Markdown will allow you to be\r\nlazy:\r\n\r\n    *   This is a list item with two paragraphs.\r\n\r\n        This is the second paragraph in the list item. You're\r\n    only required to indent the first line. Lorem ipsum dolor\r\n    sit amet, consectetuer adipiscing elit.\r\n\r\n    *   Another item in the same list.\r\n\r\nTo put a blockquote within a list item, the blockquote's `>`\r\ndelimiters need to be indented:\r\n\r\n    *   A list item with a blockquote:\r\n\r\n        > This is a blockquote\r\n        > inside a list item.\r\n\r\nTo put a code block within a list item, the code block needs\r\nto be indented *twice* -- 8 spaces or two tabs:\r\n\r\n    *   A list item with a code block:\r\n\r\n            <code goes here>\r\n\r\n\r\nIt's worth noting that it's possible to trigger an ordered list by\r\naccident, by writing something like this:\r\n\r\n    1986. What a great season.\r\n\r\nIn other words, a *number-period-space* sequence at the beginning of a\r\nline. To avoid this, you can backslash-escape the period:\r\n\r\n    1986\\. What a great season.\r\n\r\n\r\n\r\n### Code Blocks\r\n\r\nPre-formatted code blocks are used for writing about programming or\r\nmarkup source code. Rather than forming normal paragraphs, the lines\r\nof a code block are interpreted literally. Markdown wraps a code block\r\nin both `<pre>` and `<code>` tags.\r\n\r\nTo produce a code block in Markdown, simply indent every line of the\r\nblock by at least 4 spaces or 1 tab. For example, given this input:\r\n\r\n    This is a normal paragraph:\r\n\r\n        This is a code block.\r\n\r\nMarkdown will generate:\r\n\r\n    <p>This is a normal paragraph:</p>\r\n\r\n    <pre><code>This is a code block.\r\n    </code></pre>\r\n\r\nOne level of indentation -- 4 spaces or 1 tab -- is removed from each\r\nline of the code block. For example, this:\r\n\r\n    Here is an example of AppleScript:\r\n\r\n        tell application \"Foo\"\r\n            beep\r\n        end tell\r\n\r\nwill turn into:\r\n\r\n    <p>Here is an example of AppleScript:</p>\r\n\r\n    <pre><code>tell application \"Foo\"\r\n        beep\r\n    end tell\r\n    </code></pre>\r\n\r\nA code block continues until it reaches a line that is not indented\r\n(or the end of the article).\r\n\r\nWithin a code block, ampersands (`&`) and angle brackets (`<` and `>`)\r\nare automatically converted into HTML entities. This makes it very\r\neasy to include example HTML source code using Markdown -- just paste\r\nit and indent it, and Markdown will handle the hassle of encoding the\r\nampersands and angle brackets. For example, this:\r\n\r\n        <div class=\"footer\">\r\n            &copy; 2004 Foo Corporation\r\n        </div>\r\n\r\nwill turn into:\r\n\r\n    <pre><code>&lt;div class=\"footer\"&gt;\r\n        &amp;copy; 2004 Foo Corporation\r\n    &lt;/div&gt;\r\n    </code></pre>\r\n\r\nRegular Markdown syntax is not processed within code blocks. E.g.,\r\nasterisks are just literal asterisks within a code block. This means\r\nit's also easy to use Markdown to write about Markdown's own syntax.\r\n\r\n\r\n\r\n### Horizontal Rules\r\n\r\nYou can produce a horizontal rule tag (`<hr />`) by placing three or\r\nmore hyphens, asterisks, or underscores on a line by themselves. If you\r\nwish, you may use spaces between the hyphens or asterisks. Each of the\r\nfollowing lines will produce a horizontal rule:\r\n\r\n    * * *\r\n\r\n    ***\r\n\r\n    *****\r\n\r\n    - - -\r\n\r\n    ---------------------------------------\r\n\r\n\r\n## Span Elements\r\n\r\n### Links\r\n\r\nMarkdown supports two style of links: *inline* and *reference*.\r\n\r\nIn both styles, the link text is delimited by [square brackets].\r\n\r\nTo create an inline link, use a set of regular parentheses immediately\r\nafter the link text's closing square bracket. Inside the parentheses,\r\nput the URL where you want the link to point, along with an *optional*\r\ntitle for the link, surrounded in quotes. For example:\r\n\r\n    This is [an example](http://example.com/ \"Title\") inline link.\r\n\r\n    [This link](http://example.net/) has no title attribute.\r\n\r\nWill produce:\r\n\r\n    <p>This is <a href=\"http://example.com/\" title=\"Title\">\r\n    an example</a> inline link.</p>\r\n\r\n    <p><a href=\"http://example.net/\">This link</a> has no\r\n    title attribute.</p>\r\n\r\nIf you're referring to a local resource on the same server, you can\r\nuse relative paths:\r\n\r\n    See my [About](/about/) page for details.   \r\n\r\nReference-style links use a second set of square brackets, inside\r\nwhich you place a label of your choosing to identify the link:\r\n\r\n    This is [an example][id] reference-style link.\r\n\r\nYou can optionally use a space to separate the sets of brackets:\r\n\r\n    This is [an example] [id] reference-style link.\r\n\r\nThen, anywhere in the document, you define your link label like this,\r\non a line by itself:\r\n\r\n    [id]: http://example.com/  \"Optional Title Here\"\r\n\r\nThat is:\r\n\r\n*   Square brackets containing the link identifier (optionally\r\n    indented from the left margin using up to three spaces);\r\n*   followed by a colon;\r\n*   followed by one or more spaces (or tabs);\r\n*   followed by the URL for the link;\r\n*   optionally followed by a title attribute for the link, enclosed\r\n    in double or single quotes, or enclosed in parentheses.\r\n\r\nThe following three link definitions are equivalent:\r\n\r\n\t[foo]: http://example.com/  \"Optional Title Here\"\r\n\t[foo]: http://example.com/  'Optional Title Here'\r\n\t[foo]: http://example.com/  (Optional Title Here)\r\n\r\n**Note:** There is a known bug in Markdown.pl 1.0.1 which prevents\r\nsingle quotes from being used to delimit link titles.\r\n\r\nThe link URL may, optionally, be surrounded by angle brackets:\r\n\r\n    [id]: <http://example.com/>  \"Optional Title Here\"\r\n\r\nYou can put the title attribute on the next line and use extra spaces\r\nor tabs for padding, which tends to look better with longer URLs:\r\n\r\n    [id]: http://example.com/longish/path/to/resource/here\r\n        \"Optional Title Here\"\r\n\r\nLink definitions are only used for creating links during Markdown\r\nprocessing, and are stripped from your document in the HTML output.\r\n\r\nLink definition names may consist of letters, numbers, spaces, and\r\npunctuation -- but they are *not* case sensitive. E.g. these two\r\nlinks:\r\n\r\n\t[link text][a]\r\n\t[link text][A]\r\n\r\nare equivalent.\r\n\r\nThe *implicit link name* shortcut allows you to omit the name of the\r\nlink, in which case the link text itself is used as the name.\r\nJust use an empty set of square brackets -- e.g., to link the word\r\n\"Google\" to the google.com web site, you could simply write:\r\n\r\n\t[Google][]\r\n\r\nAnd then define the link:\r\n\r\n\t[Google]: http://google.com/\r\n\r\nBecause link names may contain spaces, this shortcut even works for\r\nmultiple words in the link text:\r\n\r\n\tVisit [Daring Fireball][] for more information.\r\n\r\nAnd then define the link:\r\n\t\r\n\t[Daring Fireball]: http://daringfireball.net/\r\n\r\nLink definitions can be placed anywhere in your Markdown document. I\r\ntend to put them immediately after each paragraph in which they're\r\nused, but if you want, you can put them all at the end of your\r\ndocument, sort of like footnotes.\r\n\r\nHere's an example of reference links in action:\r\n\r\n    I get 10 times more traffic from [Google] [1] than from\r\n    [Yahoo] [2] or [MSN] [3].\r\n\r\n      [1]: http://google.com/        \"Google\"\r\n      [2]: http://search.yahoo.com/  \"Yahoo Search\"\r\n      [3]: http://search.msn.com/    \"MSN Search\"\r\n\r\nUsing the implicit link name shortcut, you could instead write:\r\n\r\n    I get 10 times more traffic from [Google][] than from\r\n    [Yahoo][] or [MSN][].\r\n\r\n      [google]: http://google.com/        \"Google\"\r\n      [yahoo]:  http://search.yahoo.com/  \"Yahoo Search\"\r\n      [msn]:    http://search.msn.com/    \"MSN Search\"\r\n\r\nBoth of the above examples will produce the following HTML output:\r\n\r\n    <p>I get 10 times more traffic from <a href=\"http://google.com/\"\r\n    title=\"Google\">Google</a> than from\r\n    <a href=\"http://search.yahoo.com/\" title=\"Yahoo Search\">Yahoo</a>\r\n    or <a href=\"http://search.msn.com/\" title=\"MSN Search\">MSN</a>.</p>\r\n\r\nFor comparison, here is the same paragraph written using\r\nMarkdown's inline link style:\r\n\r\n    I get 10 times more traffic from [Google](http://google.com/ \"Google\")\r\n    than from [Yahoo](http://search.yahoo.com/ \"Yahoo Search\") or\r\n    [MSN](http://search.msn.com/ \"MSN Search\").\r\n\r\nThe point of reference-style links is not that they're easier to\r\nwrite. The point is that with reference-style links, your document\r\nsource is vastly more readable. Compare the above examples: using\r\nreference-style links, the paragraph itself is only 81 characters\r\nlong; with inline-style links, it's 176 characters; and as raw HTML,\r\nit's 234 characters. In the raw HTML, there's more markup than there\r\nis text.\r\n\r\nWith Markdown's reference-style links, a source document much more\r\nclosely resembles the final output, as rendered in a browser. By\r\nallowing you to move the markup-related metadata out of the paragraph,\r\nyou can add links without interrupting the narrative flow of your\r\nprose.\r\n\r\n### Emphasis\r\n\r\nMarkdown treats asterisks (`*`) and underscores (`_`) as indicators of\r\nemphasis. Text wrapped with one `*` or `_` will be wrapped with an\r\nHTML `<em>` tag; double `*`'s or `_`'s will be wrapped with an HTML\r\n`<strong>` tag. E.g., this input:\r\n\r\n    *single asterisks*\r\n\r\n    _single underscores_\r\n\r\n    **double asterisks**\r\n\r\n    __double underscores__\r\n\r\nwill produce:\r\n\r\n    <em>single asterisks</em>\r\n\r\n    <em>single underscores</em>\r\n\r\n    <strong>double asterisks</strong>\r\n\r\n    <strong>double underscores</strong>\r\n\r\nYou can use whichever style you prefer; the lone restriction is that\r\nthe same character must be used to open and close an emphasis span.\r\n\r\nEmphasis can be used in the middle of a word:\r\n\r\n    un*frigging*believable\r\n\r\nBut if you surround an `*` or `_` with spaces, it'll be treated as a\r\nliteral asterisk or underscore.\r\n\r\nTo produce a literal asterisk or underscore at a position where it\r\nwould otherwise be used as an emphasis delimiter, you can backslash\r\nescape it:\r\n\r\n    \\*this text is surrounded by literal asterisks\\*\r\n\r\n\r\n### Code\r\n\r\nTo indicate a span of code, wrap it with backtick quotes (`` ` ``).\r\nUnlike a pre-formatted code block, a code span indicates code within a\r\nnormal paragraph. For example:\r\n\r\n    Use the `printf()` function.\r\n\r\nwill produce:\r\n\r\n    <p>Use the <code>printf()</code> function.</p>\r\n\r\nTo include a literal backtick character within a code span, you can use\r\nmultiple backticks as the opening and closing delimiters:\r\n\r\n    ``There is a literal backtick (`) here.``\r\n\r\nwhich will produce this:\r\n\r\n    <p><code>There is a literal backtick (`) here.</code></p>\r\n\r\nThe backtick delimiters surrounding a code span may include spaces --\r\none after the opening, one before the closing. This allows you to place\r\nliteral backtick characters at the beginning or end of a code span:\r\n\r\n\tA single backtick in a code span: `` ` ``\r\n\t\r\n\tA backtick-delimited string in a code span: `` `foo` ``\r\n\r\nwill produce:\r\n\r\n\t<p>A single backtick in a code span: <code>`</code></p>\r\n\t\r\n\t<p>A backtick-delimited string in a code span: <code>`foo`</code></p>\r\n\r\nWith a code span, ampersands and angle brackets are encoded as HTML\r\nentities automatically, which makes it easy to include example HTML\r\ntags. Markdown will turn this:\r\n\r\n    Please don't use any `<blink>` tags.\r\n\r\ninto:\r\n\r\n    <p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>\r\n\r\nYou can write this:\r\n\r\n    `&#8212;` is the decimal-encoded equivalent of `&mdash;`.\r\n\r\nto produce:\r\n\r\n    <p><code>&amp;#8212;</code> is the decimal-encoded\r\n    equivalent of <code>&amp;mdash;</code>.</p>\r\n\r\n\r\n### Images\r\n\r\nAdmittedly, it's fairly difficult to devise a \"natural\" syntax for\r\nplacing images into a plain text document format.\r\n\r\nMarkdown uses an image syntax that is intended to resemble the syntax\r\nfor links, allowing for two styles: *inline* and *reference*.\r\n\r\nInline image syntax looks like this:\r\n\r\n    ![Alt text](/path/to/img.jpg)\r\n\r\n    ![Alt text](/path/to/img.jpg \"Optional title\")\r\n\r\nThat is:\r\n\r\n*   An exclamation mark: `!`;\r\n*   followed by a set of square brackets, containing the `alt`\r\n    attribute text for the image;\r\n*   followed by a set of parentheses, containing the URL or path to\r\n    the image, and an optional `title` attribute enclosed in double\r\n    or single quotes.\r\n\r\nReference-style image syntax looks like this:\r\n\r\n    ![Alt text][id]\r\n\r\nWhere \"id\" is the name of a defined image reference. Image references\r\nare defined using syntax identical to link references:\r\n\r\n    [id]: url/to/image  \"Optional title attribute\"\r\n\r\nAs of this writing, Markdown has no syntax for specifying the\r\ndimensions of an image; if this is important to you, you can simply\r\nuse regular HTML `<img>` tags.\r\n\r\n\r\n## Miscellaneous\r\n\r\n### Automatic Links\r\n\r\nMarkdown supports a shortcut style for creating \"automatic\" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:\r\n\r\n    <http://example.com/>\r\n    \r\nMarkdown will turn this into:\r\n\r\n    <a href=\"http://example.com/\">http://example.com/</a>\r\n\r\nAutomatic links for email addresses work similarly, except that\r\nMarkdown will also perform a bit of randomized decimal and hex\r\nentity-encoding to help obscure your address from address-harvesting\r\nspambots. For example, Markdown will turn this:\r\n\r\n    <address@example.com>\r\n\r\ninto something like this:\r\n\r\n    <a href=\"&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;\r\n    &#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;\r\n    &#109;\">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;\r\n    &#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>\r\n\r\nwhich will render in a browser as a clickable link to \"address@example.com\".\r\n\r\n(This sort of entity-encoding trick will indeed fool many, if not\r\nmost, address-harvesting bots, but it definitely won't fool all of\r\nthem. It's better than nothing, but an address published in this way\r\nwill probably eventually start receiving spam.)\r\n\r\n\r\n\r\n### Backslash Escapes\r\n\r\nMarkdown allows you to use backslash escapes to generate literal\r\ncharacters which would otherwise have special meaning in Markdown's\r\nformatting syntax. For example, if you wanted to surround a word\r\nwith literal asterisks (instead of an HTML `<em>` tag), you can use\r\nbackslashes before the asterisks, like this:\r\n\r\n    \\*literal asterisks\\*\r\n\r\nMarkdown provides backslash escapes for the following characters:\r\n\r\n    \\   backslash\r\n    `   backtick\r\n    *   asterisk\r\n    _   underscore\r\n    {}  curly braces\r\n    []  square brackets\r\n    ()  parentheses\r\n    #   hash mark\r\n\t+\tplus sign\r\n\t-\tminus sign (hyphen)\r\n    .   dot\r\n    !   exclamation mark",
          "title": "Welcome To Django Wiki"
      }
  },
  {
      "model": "wiki.articlerevision",
      "pk": 2,
      "fields": {
          "revision_number": 1,
          "user_message": "Added dummy test Article",
          "automatic_log": "",
          "ip_address": null,
          "user": 1,
          "modified": "2023-01-31T22:37:06.465Z",
          "created": "2023-01-31T22:37:06.465Z",
          "previous_revision": null,
          "deleted": false,
          "locked": false,
          "article": 2,
          "content": "Hi, if you're trying to edit, or add a new wiki page. Please use this article for your tests.",
          "title": "Use this space"
      }
  },
  {
      "model": "wiki.articleplugin",
      "pk": 1,
      "fields": {
          "article": 1,
          "deleted": false,
          "created": "2023-01-31T22:24:13.920Z"
      }
  },
  {
      "model": "wiki.articleplugin",
      "pk": 2,
      "fields": {
          "article": 1,
          "deleted": false,
          "created": "2023-02-01T20:48:20.294Z"
      }
  },
  {
      "model": "wiki.urlpath",
      "pk": 1,
      "fields": {
          "article": 1,
          "slug": null,
          "site": 1,
          "parent": null,
          "moved_to": null,
          "lft": 1,
          "rght": 4,
          "tree_id": 1,
          "level": 0
      }
  },
  {
      "model": "wiki.urlpath",
      "pk": 2,
      "fields": {
          "article": 2,
          "slug": "use-this-space",
          "site": 1,
          "parent": 1,
          "moved_to": null,
          "lft": 2,
          "rght": 3,
          "tree_id": 1,
          "level": 1
      }
  },
  {
    "model": "wiki.revisionplugin",
    "pk": 1,
    "fields": {
        "current_revision": 1
    }
  },
  {
      "model": "wiki.revisionpluginrevision",
      "pk": 1,
      "fields": {
          "revision_number": 0,
          "user_message": "",
          "automatic_log": "",
          "ip_address": null,
          "user": 1,
          "modified": "2023-02-01T20:48:20.299Z",
          "created": "2023-02-01T20:48:20.299Z",
          "previous_revision": null,
          "deleted": false,
          "locked": false,
          "plugin": 1
      }
  },
  {
      "model": "wiki_notifications.articlesubscription",
      "pk": 1,
      "fields": {
          "subscription": 1
      }
  },
  {
    "model": "wiki_images.image",
    "pk": 1,
    "fields": {}
  },
  {
    "model": "wiki_images.imagerevision",
    "pk": 1,
    "fields": {
        "image": "wiki/images/1/a1b5813b5f934663a502c727230c700b/djangowikilogo.png",
        "width": 200,
        "height": 200
    }
  }
]
