add extensions to support admonitions (#71)

Author: mingness

docs/develop.md

@@ -2,7 +2,8 @@
 
 You are now ready to develop your library. This guide will walk you through resolving dependencies, configuring the build, creating release artifacts, and testing your library in Processing.
 
-_Note: If you haven't set up your environment yet, refer to the [Getting Started guide](getting-started.md)._
+!!! Note
+    If you haven't set up your environment yet, refer to the [Getting Started guide](getting-started.md).
 
 
 ## Developing the library
@@ -37,9 +38,10 @@ were to use the `commons-math3` package from `org.apache.commons` as a dependenc
 implementation(group = "org.apache.commons", name = "commons-math3", version = "3.6.1")
 ```
 
-NOTE: Dependencies added with `implementation` will be included in the release. Dependencies
-added with `compileOnly`, such as Processing core, are available for compilation, but won't
-be included in the release.
+!!! Note
+    Dependencies added with `implementation` will be included in the release. Dependencies
+    added with `compileOnly`, such as Processing core, are available for compilation, but won't
+    be included in the release.
 
 After you add these dependencies, **refresh Gradle**, and then you will be able to access them
 in your code. Refresh Gradle by going to the Gradle menu (elephant) in your IDE
@@ -89,7 +91,8 @@ those sections for [resolving dependencies](#resolving-dependencies).
 ## Creating examples
 Examples help users understand your library’s functionality, it is recommended that you include several clear and well-commented samples sketches in the `examples` folder.
 
-_Note: The example sketch included in this template outputs the image shown on the home page._
+!!! Note
+    The example sketch included in this template outputs the image shown on the home page.
 
 ## Creating the release artifacts
 If you've already gone through the [Getting started](getting-started.md#first-steps) guide, you will have

docs/index.md

@@ -12,6 +12,8 @@ This documentation provides information on
 3. [Releasing your library](release)
 4. [Troubleshooting](troubleshooting.md)
 
+!!! note
+    This template is based on Gradle. If you are looking for the old Ant-based template, see processing/processing-library-template-ant
 
 ## References 
 Existing references for developing libraries for Processing can be found on the following Github wiki pages:
@@ -37,4 +39,4 @@ I wish to thank the developers of these repositories, who generously provided
 guidance and time. This template has been developed in collaboration with
 [@enkatsu](https://github.com/enkatsu).
 
-The example library was developed by Stig Møller Hansen ([@stixan](https://github.com/stixan)).
+The example library was developed by Stig Møller Hansen ([@stixan](https://github.com/stixan)).

docs/release.md

@@ -24,7 +24,8 @@ This template include a workflow that automatically deploys your documentaion we
 
 Any time you want to update the documentation, edit your `.md` files and `mkdocs.yml` as needed, then push your changes to `main`. This will trigger the workflow to deploy an update.
 
-_Note: You can find the workflow file at `.github/workflows/deploy_website.yml`._
+!!! Note
+    You can find the workflow file at `.github/workflows/deploy_website.yml`.
 
 ### Alternative Hosting and Static Site Generators
 If you prefer not to use the built-in workflow with GitHub Pages and Material for MkDocs, you are free to use another static site generator or hosting service. Note that it’s important that the site remains online, as it serves as a reference for users of your library. 
@@ -41,7 +42,8 @@ Releasing your library on GitHub allows users to access known-working versions o
 
 This will trigger the GitHub workflow (`.github/workflows/release.yml`), which automatically create release artifacts—`*.txt`, `*.zip`, `*.pdex` files—and add them to the release.
 
-_Note: By default, GitHub will also include compressed versions of your source code (e.g., `Source code (zip)` and `Source code (tar.gz)`)._
+!!! Note
+    By default, GitHub will also include compressed versions of your source code (e.g., `Source code (zip)` and `Source code (tar.gz)`).
 
 For more details on releases, see GitHub’s [official guide on releasing projects](https://docs.github.com/en/repositories/releasing-projects-on-github).
 

mkdocs.yml

@@ -14,6 +14,10 @@ theme:
     - navigation.top
     - navigation.footer
 
+markdown_extensions:
+  - admonition
+  - pymdownx.details
+  - pymdownx.superfences
 
 copyright: MIT Licence.