feat: Add software_tags to content types

Adds software_tags field to archetypes and content. This allows associating events and blog posts with specific software pages, enabling the creation of related events/content listings on software pages. Includes Spyx tag for relevant content.

Author: neural-loop

archetypes/hacking-hours.md

@@ -1,31 +1,27 @@
 ---
-title: "Workshop: {{ replace .Name "-" " " | title }}" # Workshop Title: Clear & concise (50-60 chars). Include speaker/topic if possible for SEO.
+title: "Hacking Hours: {{ replace .Name "-" " " | title }}" # Hacking Hours Title: Clear & concise (50-60 chars). Include speaker/topic if possible for SEO.
 author:
   - "Speaker Name or Slug" # Match with a contributor profile title/slug. Add more authors if needed.
-date: {{ .Date }} # Date of the workshop (YYYY-MM-DD).
+date: {{ .Date }} # Date of the hacking hours (YYYY-MM-DD).
 start_time: "18:00" # Event start time (24-hour format HH:MM).
 end_time: "19:30"   # Event end time (24-hour format HH:MM).
 time_zone: "CET"    # Timezone (e.g., CET, CEST, EST, PST).
-# Meta Description (SEO): 120-160 characters.
-# This is crucial for search results! It's your "ad copy."
-# - Briefly state what the workshop is about.
-# - Mention key topics or speakers.
-# - Highlight the value/benefit for attendees.
-# - Include relevant keywords naturally.
-description: "Join us for an insightful workshop on [Topic] by [Speaker Name]. Discover [Key Takeaway 1] and explore [Key Takeaway 2] in neuromorphic computing."
+description: "Join us for an insightful hacking hours on [Topic] by [Speaker Name]. Discover [Key Takeaway 1] and explore [Key Takeaway 2] in neuromorphic computing."
 upcoming: true # Set to 'true' for future events. Change to 'false' after the event.
 video: ""      # After the event, add the YouTube video ID (e.g., "dQw4w9WgXcQ").
-image: "workshop-banner.png" # Main banner image (1200x630px ideal for sharing). Place in this workshop's folder.
-speaker_photo: "speaker-photo.jpg" # Speaker's photo. Place in this workshop's folder.
-type: "hacking-hours" # IMPORTANT: Do not change this line for hacking hour events.
-# For Student Talks, set type: "student-talks"
-speaker_bio: "A brief biography of the speaker. Highlight their expertise relevant to the workshop topic."
-# Optional: Add links to slides, code, or notebooks if available after the workshop.
-# Place these files in this workshop's folder and link them:
+image: "hacking-hours-banner.png" # Main banner image (1200x630px ideal for sharing). Place in this hacking hours's folder.
+speaker_photo: "speaker-photo.jpg" # Speaker's photo. Place in this hacking hours's folder.
+type: "hacking-hours" # IMPORTANT: Do not change this line for hacking hours events.
+speaker_bio: "A brief biography of the speaker. Highlight their expertise relevant to the hacking hours topic."
+# Optional: Add the file name (slug) of any software pages this event is related to.
+# e.g., ["spyx", "snntorch"]
+software_tags: []
+# Optional: Add links to slides, code, or notebooks if available after the hacking hours.
+# Place these files in this hacking hours's folder and link them:
 # speaker_slides: "slides.pdf"
 # speaker_code: "https://github.com/example/repo" # External link
 # speaker_notebook: "my-notebook.ipynb" # Place in folder
 ---
 
-Detailed workshop abstract or information goes here.
+Detailed hacking hours abstract or information goes here.
 Explain what attendees will learn, the agenda, and any prerequisites.

archetypes/student-talks.md

@@ -1,31 +1,27 @@
 ---
-title: "Workshop: {{ replace .Name "-" " " | title }}" # Workshop Title: Clear & concise (50-60 chars). Include speaker/topic if possible for SEO.
+title: "Student Talk: {{ replace .Name "-" " " | title }}" # Student Talk Title: Clear & concise (50-60 chars). Include speaker/topic if possible for SEO.
 author:
   - "Speaker Name or Slug" # Match with a contributor profile title/slug. Add more authors if needed.
-date: {{ .Date }} # Date of the workshop (YYYY-MM-DD).
+date: {{ .Date }} # Date of the student talk (YYYY-MM-DD).
 start_time: "18:00" # Event start time (24-hour format HH:MM).
 end_time: "19:30"   # Event end time (24-hour format HH:MM).
 time_zone: "CET"    # Timezone (e.g., CET, CEST, EST, PST).
-# Meta Description (SEO): 120-160 characters.
-# This is crucial for search results! It's your "ad copy."
-# - Briefly state what the workshop is about.
-# - Mention key topics or speakers.
-# - Highlight the value/benefit for attendees.
-# - Include relevant keywords naturally.
-description: "Join us for an insightful workshop on [Topic] by [Speaker Name]. Discover [Key Takeaway 1] and explore [Key Takeaway 2] in neuromorphic computing."
+description: "Join us for an insightful student talk on [Topic] by [Speaker Name]. Discover [Key Takeaway 1] and explore [Key Takeaway 2] in neuromorphic computing."
 upcoming: true # Set to 'true' for future events. Change to 'false' after the event.
 video: ""      # After the event, add the YouTube video ID (e.g., "dQw4w9WgXcQ").
-image: "workshop-banner.png" # Main banner image (1200x630px ideal for sharing). Place in this workshop's folder.
-speaker_photo: "speaker-photo.jpg" # Speaker's photo. Place in this workshop's folder.
+image: "student-talk-banner.png" # Main banner image (1200x630px ideal for sharing). Place in this student talk's folder.
+speaker_photo: "speaker-photo.jpg" # Speaker's photo. Place in this student talk's folder.
 type: "student-talks" # IMPORTANT: Do not change this line for student talk events.
-# For Hacking Hours, set type: "hacking-hours"
-speaker_bio: "A brief biography of the speaker. Highlight their expertise relevant to the workshop topic."
-# Optional: Add links to slides, code, or notebooks if available after the workshop.
-# Place these files in this workshop's folder and link them:
+speaker_bio: "A brief biography of the speaker. Highlight their expertise relevant to the student talk topic."
+# Optional: Add the file name (slug) of any software pages this event is related to.
+# e.g., ["spyx", "snntorch"]
+software_tags: []
+# Optional: Add links to slides, code, or notebooks if available after the student talk.
+# Place these files in this student talk's folder and link them:
 # speaker_slides: "slides.pdf"
 # speaker_code: "https://github.com/example/repo" # External link
 # speaker_notebook: "my-notebook.ipynb" # Place in folder
 ---
 
-Detailed workshop abstract or information goes here.
+Detailed student talk abstract or information goes here.
 Explain what attendees will learn, the agenda, and any prerequisites.

archetypes/workshops.md

@@ -6,21 +6,16 @@ date: {{ .Date }} # Date of the workshop (YYYY-MM-DD).
 start_time: "18:00" # Event start time (24-hour format HH:MM).
 end_time: "19:30"   # Event end time (24-hour format HH:MM).
 time_zone: "CET"    # Timezone (e.g., CET, CEST, EST, PST).
-# Meta Description (SEO): 120-160 characters.
-# This is crucial for search results! It's your "ad copy."
-# - Briefly state what the workshop is about.
-# - Mention key topics or speakers.
-# - Highlight the value/benefit for attendees.
-# - Include relevant keywords naturally.
 description: "Join us for an insightful workshop on [Topic] by [Speaker Name]. Discover [Key Takeaway 1] and explore [Key Takeaway 2] in neuromorphic computing."
 upcoming: true # Set to 'true' for future events. Change to 'false' after the event.
 video: ""      # After the event, add the YouTube video ID (e.g., "dQw4w9WgXcQ").
 image: "workshop-banner.png" # Main banner image (1200x630px ideal for sharing). Place in this workshop's folder.
 speaker_photo: "speaker-photo.jpg" # Speaker's photo. Place in this workshop's folder.
 type: "workshops" # IMPORTANT: Do not change this line for workshop events.
-# For Student Talks, set type: "student-talks"
-# For Hacking Hours, set type: "hacking-hours"
 speaker_bio: "A brief biography of the speaker. Highlight their expertise relevant to the workshop topic."
+# Optional: Add the file name (slug) of any software pages this event is related to.
+# e.g., ["spyx", "snntorch"]
+software_tags: []
 # Optional: Add links to slides, code, or notebooks if available after the workshop.
 # Place these files in this workshop's folder and link them:
 # speaker_slides: "slides.pdf"

content/blog/spiking-neural-network-framework-benchmarking/index.md

@@ -12,6 +12,7 @@ author:
 - "Jens E. Pedersen"
 image: neurons-race.png
 tags: ["snn", "framework", "library", "pytorch", "JAX"]
+software_tags: ["spyx"]
 show_author_bios: true
 ---
 
@@ -40,7 +41,7 @@ Striking a balance between flexibility/extensibility and efficiency from compila
 
 The second figure shows the maximum memory usage during forward and backward pass for the same networks. The compiled Norse model comes out on top, which is interesting because it is being built in pure Python.
 This is most likely due to compiler techinques such as kernel fusion, where subsequent PyTorch layers are fused into single operations to avoid device bottleneck and to leverage the single instruction, multiple data (SIMD) architectures of GPUs.
-The memory usage benchmarks were collected using PyTorch's [max_memory_allocated()](https://pytorch.org/docs/stable/generated/torch.cuda.max_memory_allocated.html) function, unfortunately JAX does not have a similar function so for now Spyx is not included in the memory benchmark.
+The memory usage benchmarks were collected using PyTorch's [max_memory_allocated()](https://pytorch.org/docs/stable/generated/torch.cuda.max_memory_allocated.html) function, unfortunately JAX does not have a similar function so for now [Spyx](/neuromorphic-computing/software/snn-frameworks/spyx/) is not included in the memory benchmark.
 
 ## Summary
 The ideal library will often depend on a multitude of factors, such as accessible documentation, usability of the API or pre-trained models. Generally speaking, PyTorch offers good support when custom neuron models (that have additional states, recurrence) are to be explored. For larger networks, it will likely pay off to rely on CUDA-accelerated existing implementations, or ensure your model is compatible with the recent compilation techniques to leverage the backend-specific JIT optimizations. The development of Spyx offers an interesting new framework as it enables the flexible neuron definitions of PyTorch frameworks while also enabling the speed of libraries which utilize custom CUDA backends. One more note on the accuracy of gradient computation: In order to speed up computation, some frameworks will approximate this calculation over time. Networks will still manage to *learn* in most cases, but EXODUS, correcting an approximation in SLAYER and therefore calculating gradients that are equivalent to BPTT, showed that it can make a substantial difference in certain experiments. So while speed is extremely important, other factors such as memory consumption and quality of gradient calculation matter as well. 

content/neuromorphic-computing/software/hacking-hours/kade-heckel-jax-pallas-optimization/index.md

@@ -14,6 +14,7 @@ speaker_photo: "images/speakers/kade-heckel-placeholder.png" # Placeholder, plea
 image: "kade-heckel-jax-pallas-optimization.jpg" # Placeholder, please create
 type: "hacking-hours"
 speaker_bio: "Kade Heckel is a researcher and developer focusing on high-performance computing for neural networks, with expertise in JAX and related optimization tools like Pallas. He is the creator of Spyx, a JAX-based spiking neural network library."
+software_tags: ["spyx"]
 ---
 
 In this Hacking Hour, Kade Heckel, creator of the JAX-based spiking neural network (SNN) library "Spyx," joins host Jens E. Pedersen. They explore techniques for optimizing SNN code for GPUs and TPUs using JAX and the Pallas library, covering practical approaches to accelerate neuromorphic and machine learning computations.
@@ -92,7 +93,7 @@ In this Hacking Hour, Kade Heckel, creator of the JAX-based spiking neural netwo
 *   JAX's automatic fusion matched Pallas performance for simple element-wise functions.
 *   Pallas is particularly useful for TPUs, structured sparsity, and custom data loading.
 *   Calling JAX functions with custom VJPs inside Pallas kernels is problematic.
-*   Optimizing SNNs for TPUs with JAX/Pallas is a promising, largely unexplored area.
+*   Optimizing SNNs for TPUs using Pallas is a key future direction.
 
 ## Conclusion
 

content/workshops/spyx-hackathon-speeding-up-neuromorphic-computing/index.md

@@ -7,6 +7,7 @@ start_time: 18:00
 end_time: 20:00
 video: gKNegntASLI
 speaker_photo: speaker.jpeg
+software_tags: ["spyx"]
 speaker_bio: "Kade studied Computer Science and Computer Engineering at the U.S. Naval Academy. Studying in the UK as a Marshall Scholar, Kade completed an MSc in A.I. and Adaptive Systems with distinction from the University of Sussex and is currently pursuing an MPhil in Machine Learning and Machine Intelligence at the University of Cambridge. His dissertation at Sussex focused on comparing surrogate gradient and large scale neuroevolutionary algorithms for optimizing spiking neural networks."
 speaker_code: https://github.com/kmheckel/spyx
 time_zone: CEST

layouts/neuromorphic-software/single.html

@@ -3,15 +3,27 @@
   <section class="section pt-6">
     <div class="container">
       <div class="row lg:gx-8 lg:items-stretch">
-        {{/* Main Content Column */}}
         <div class="lg:col-8">
           <article class="content mb-10">
             {{ .Content }}
           </article>
-          
+
+          {{ $softwareSlug := .File.Dir | path.Base }}
+          {{ $relatedContent := slice }}
+          {{ range site.RegularPages }}
+            {{ $contentPage := . }}
+            {{ with .Params.software_tags }}
+              {{ if in . $softwareSlug }}
+                {{ $relatedContent = $relatedContent | append $contentPage }}
+              {{ end }}
+            {{ end }}
+          {{ end }}
+          {{ $relatedContent = sort $relatedContent "Date" "desc" }}
+          {{ partial "software/related-events.html" $relatedContent }}
+
           {{ partial "components/content-contribute-cta.html" (dict
             "icon" "solid code"
-            "title" "Help Improve this <span class=\"gradient-text\">Software Guide</span>"
+            "title" "Help Improve this <span class='gradient-text'>Software Guide</span>"
             "description" "Our software guide is maintained by the community. If you have updates, see an error, or want to suggest a new tool, please let us know by opening an issue on our GitHub repository."
             "link" "https://github.com/open-neuromorphic/open-neuromorphic.github.io/issues/new/choose"
             "link_text" "Suggest an Edit on GitHub"
@@ -21,8 +33,7 @@
              {{ partial "components/share-cta.html" . }}
           </div>
         </div>
-        
-        {{/* Sidebar Column */}}
+
         <aside class="lg:col-4">
           <div class="pb-4">
             {{ partial "components/og-preview.html" . }}
@@ -32,22 +43,6 @@
           </div>
         </aside>
       </div>
-
-      {{/* Related Posts Section (Optional, but good to keep) */}}
-      {{ $related := where site.RegularPages "Section" "blog" | intersect (where site.RegularPages ".Title" "!=" .Title) | union (site.RegularPages.Related . ) }}
-      {{ $related = $related | shuffle | first 3 }}
-      {{ with $related }}
-      <div class="section pb-0 mt-12">
-        <h2 class="h3 mb-6 text-center">Related Blog Posts</h2>
-        <div class="row">
-          {{ range . }}
-            <div class="lg:col-4">
-              {{ partial "components/blog-card" . }}
-            </div>
-          {{ end }}
-        </div>
-      </div>
-      {{ end }}
     </div>
   </section>
 {{ end }}