Update website

docs/api/index.html

@@ -385,8 +385,8 @@ <h1>Testing if the service is available<a name="testing-if-the-service-is-availa
 <h1>Searching<a name="searching" href="#searching" class="heading-anchor">🔗</a></h1>
 <p>Call <strong>GET /search?query=YOUR_QUERY</strong> to search for notes. This end-point supports the <code>field</code> parameter which is recommended to use so that you only get the data that you need. The query syntax is as described in the main documentation: <a href="https://joplinapp.org/#searching">https://joplinapp.org/#searching</a></p>
 <p>To retrieve non-notes items, such as notebooks or tags, add a <code>type</code> parameter and set it to the required <a href="#item-type-id">item type name</a>. In that case, full text search will not be used - instead it will be a simple case-insensitive search. You can also use <code>*</code> as a wildcard. This is convenient for example to retrieve notebooks or tags by title.</p>
-<p>For example, to retrieve the notebook named &quot;recipes&quot;: <strong>GET /search?query=recipes&amp;type=folder</strong><br>
-To retrieve all the tags that start with &quot;project-&quot;: <strong>GET /search?query=project-*&amp;type=tag</strong></p>
+<p>For example, to retrieve the notebook named <code>recipes</code>: <strong>GET /search?query=recipes&amp;type=folder</strong></p>
+<p>To retrieve all the tags that start with <code>project-</code>: <strong>GET /search?query=project-*&amp;type=tag</strong></p>
 <h1>Item type IDs<a name="item-type-ids" href="#item-type-ids" class="heading-anchor">🔗</a></h1>
 <p>Item type IDs might be refered to in certain object you will retrieve from the API. This is the correspondance between name and ID:</p>
 <table>

docs/changelog/index.html

@@ -333,6 +333,17 @@
 </ul>
 </div>
 <h1>Joplin changelog<a name="joplin-changelog" href="#joplin-changelog" class="heading-anchor">🔗</a></h1>
+<h2><a href="https://github.com/laurent22/joplin/releases/tag/v1.0.179">v1.0.179</a> - 2020-01-24T22:42:41Z<a name="v1-0-179-https-github-com-laurent22-joplin-releases-tag-v1-0-179-2020-01-24t22-42-41z" href="#v1-0-179-https-github-com-laurent22-joplin-releases-tag-v1-0-179-2020-01-24t22-42-41z" class="heading-anchor">🔗</a></h2>
+<ul>
+<li>New: Added new, more secure encryption methods, so that they can be switched to at a later time</li>
+<li>Improved: Improve appearance of note Info dialog</li>
+<li>Fixed: Apply userstyle again when exporting to PDF or printing (<a href="https://github.com/laurent22/joplin/issues/2324">#2324</a>)</li>
+<li>Fixed: Fixed update message box</li>
+<li>Fixed: Fix identification of note in pdf export from main menu. (<a href="https://github.com/laurent22/joplin/issues/2323">#2323</a> by mic704b)</li>
+<li>Fixed: Undefined text was being displayed on top of notes in revision viewer (<a href="https://github.com/laurent22/joplin/issues/2352">#2352</a>)</li>
+<li>Fixed: Fixed issues with Katex and MultiMd table plugin (<a href="https://github.com/laurent22/joplin/issues/2339">#2339</a>)</li>
+<li>Fixed: Fix Linux installation script (<a href="https://github.com/laurent22/joplin/issues/2333">#2333</a> by <a href="https://github.com/carlbordum">@carlbordum</a>)</li>
+</ul>
 <h2><a href="https://github.com/laurent22/joplin/releases/tag/v1.0.178">v1.0.178</a> - 2020-01-20T19:06:45Z<a name="v1-0-178-https-github-com-laurent22-joplin-releases-tag-v1-0-178-2020-01-20t19-06-45z" href="#v1-0-178-https-github-com-laurent22-joplin-releases-tag-v1-0-178-2020-01-20t19-06-45z" class="heading-anchor">🔗</a></h2>
 <ul>
 <li>New: Add ability to search by folder or tag title</li>

docs/gsoc2020/ideas.html

@@ -355,7 +355,7 @@ <h2>2. Collaboration via Nextcloud<a name="2-collaboration-via-nextcloud" href="
 <p>Difficulty Level: High</p>
 <p>Platforms: Desktop and/or mobile (at the student's choice)</p>
 <p>Skills Required: JavaScript; React; React Native (for mobile)</p>
-<p>Potential Mentor(s): <a href="https://github.com/laurent22/">laurent22</a></p>
+<p>Potential Mentor(s): <a href="mailto:roeland.douma@nextcloud.com">Roeland Jago Douma</a>, <a href="https://github.com/laurent22/">laurent22</a></p>
 <p>More info: <a href="https://discourse.joplinapp.org/t/joplin-api-in-nextcloud-prototype/">Forum thread about Joplin Web API for Nextcloud</a></p>
 <h2>3. Hierarchical Tags<a name="3-hierarchical-tags" href="#3-hierarchical-tags" class="heading-anchor">🔗</a></h2>
 <p>One of the most asked-for feature in Joplin is support for hierarchical tags. This would allow users that heavily rely on tags to organise them into a hierarchy, as is done for the notebooks.</p>
@@ -385,7 +385,7 @@ <h2>5. Web client for Nextcloud<a name="5-web-client-for-nextcloud" href="#5-web
 <p>Expected Outcome: Viewing and editing notes and notebooks from a Nextcloud-based web client</p>
 <p>Difficulty Level: High</p>
 <p>Skills Required: PHP (for the Nextcloud app). For the front-end it can be plain HTML (no JS), or React.</p>
-<p>Potential Mentor(s): <a href="https://github.com/laurent22/">laurent22</a></p>
+<p>Potential Mentor(s): <a href="mailto:roeland.douma@nextcloud.com">Roeland Jago Douma</a>, <a href="https://github.com/laurent22/">laurent22</a></p>
 <p>More info: <a href="https://github.com/laurent22/joplin/issues/228">GitHub: Nextcloud notes integration (Web client)</a></p>
 <h2>5. OCR support<a name="5-ocr-support" href="#5-ocr-support" class="heading-anchor">🔗</a></h2>
 <p>It is possible to add support for OCR content in Joplin via the <a href="http://tesseract.projectnaptha.com/">Tesseract library</a>. A first step would be to assess the feasibility of this project by integrating the lib in the desktop app and trying to OCR an image. OCR support should be implemented as a service of the desktop app. It would extract the text from the images, and append the content as plain text to the notes.</p>