inception in fence_processor_doc self documentation

README.md

@@ -4,7 +4,7 @@
 [![Package](https://img.shields.io/badge/-Package-important)](https://hex.pm/packages/fancy_fences)
 [![Documentation](https://img.shields.io/badge/-Documentation-blueviolet)](https://hexdocs.pm/fancy_fences)
 
-`FancyFences` is a markdown processor on top of [`Earmark`](https://github.com/pragdave/earmark)
+`FancyFences` is a markdown processor on top of [`EarmarkParser`](https://github.com/pragdave/earmark)
 (the default markdown processor user by [`ExDoc`](https://github.com/elixir-lang/ex_doc). You can
 use it to conditionally post-process code blocks allowing you to:
 

lib/fancy_fences/processors.ex

@@ -3,7 +3,7 @@ defmodule FancyFences.Processors do
   Common fence processors.
   """
 
-  @doc """
+  @doc ~S'''
   A fence processor for documenting fence processors usage.
 
   This can be used for documenting fence processors. It return an admonition
@@ -19,14 +19,31 @@ defmodule FancyFences.Processors do
   For example:
 
   ~~~
-  ```fence-processor-docs
+  ```fence-processor
   %{
     block: "Enum.map([1, 2, 3], fn x -> 2*x end)",
     processor: fn block -> FancyFences.Processors.inspect_code(block) end
   }
   ```
   ~~~
-  """
+
+  ```fence-processor
+  %{
+    block: """
+    %{
+       block: "1 + 1",
+       processor: fn block -> 
+         "**Code:** `"<> block <> "`"
+       end
+    }
+    """,
+    processor: fn block -> FancyFences.Processors.fence_processor_doc(block) end
+  }
+  ```
+
+  Notice that above we used `fence_processor_doc/1` to document itself, that's why
+  we have the nested admonition block.
+  '''
   def fence_processor_doc(code) do
     {result, _} = Code.eval_string(code, [], __ENV__)
     %{block: block, processor: processor} = result