Move links out of navbar and into sidebar / other docs. (#620)

# References and relevant issues

Closes #615. Follow up of #610. Remake of #617 because I got confused
with the commit history and merging

# Description

I think the navbar is a bit too cluttered due to the 'More' section
being propagated to the sidebar in smaller width screens (and generally
being finnicky)

1. Moves 3 lower-value (I still love them) links out of the navbar:
blog, zulip chat, and workshop template
2. Moves blog to homepage sidebar (confirms there is a link to blog in
community)
3. Moves workshop template link to Workshops page in Usage, also adds a
link to Contributing index
4. Removes zulip link in favor of presence in homepage sidebar and
presence in footer. If we want to keep this in header we should move the
footer link up to the header in theme
5. Adds troubleshooting link to homepage sidebar (**check** that this is
internally referenced correctly, I can't do
https://napari.org/troubleshooting.html/ like I can for other internal
refs, it 404s)

Author: TimMonko

docs/_templates/sidebar-link-items.html

@@ -7,13 +7,19 @@
             <li class="toctree-l1">
                 <a class="reference external" href="https://napari.zulipchat.com/">Community chat</a>
             </li>
+            <li class="toctree-l1">
+                <a class="reference internal" href="troubleshooting.html">Troubleshooting</a>
+            </li>
             <li class="toctree-l1">
                 {% if version == "dev" %}
                 <a class="reference internal" href="{{ 'release/index.html' }}">Release notes</a>
                 {% else %}
                 <a class="reference internal" href="{{ 'release/release_' + version.replace('.', '_') + '.html' }}">Latest release notes</a>
                 {% endif %}
             </li>
+            <li class="toctree-l1">
+                <a class="reference external" href="https://napari.org/island-dispatch">Blog</a>
+            </li>
         </ul>
     </div>
 </nav>

docs/conf.py

@@ -107,9 +107,6 @@
 html_theme_options = {
     "external_links": [
         {"name": "napari hub", "url": "https://napari-hub.org"},
-        {"name": "Island Dispatch", "url": "https://napari.org/island-dispatch"},
-        {"name": "Community chat", "url": "https://napari.zulipchat.com"},
-        {"name": "workshop template", "url": "https://napari.org/napari-workshop-template"},
     ],
     "github_url": "https://github.com/napari/napari",
     "navbar_start": ["navbar-logo", "navbar-project"],

docs/developers/index.md

@@ -7,9 +7,10 @@ to napari.
 napari has a [Code of Conduct](napari-coc) that should be honored by everyone who participates in the `napari` community.
 
 - [](contact): how to contact us.
-- [](roadmaps): convey the general direction for napari development and possible
-  work plans.
-- **Contributor guides**: resources on for contributors:
+- [](roadmaps): convey the general direction for napari development and possible work plans
+- [napari Workshop](https://napari.org/napari-workshop-template/home.html): create and deploy your own napari workshop materials
+
+- **Contributor guides**: resources for contributors:
   - [Contributing guide](napari-contributing)
     - [Development installation](dev-installation)
     - [Testing](napari-testing)

docs/further-resources/napari-workshops.md

@@ -9,7 +9,7 @@ You can find more videos of talks, tutorials and demos on the
 
 ```{admonition} Got a workshop?
 If you are looking to create your own workshop, you can use the
-[napari workshop template](https://github.com/napari/napari-workshop-template)
+[napari workshop template](https://napari.org/napari-workshop-template/)
 as a starting point.
 
 If you have organized a napari workshop and would like to see it featured here