<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Django-Ninja on CS 347</title>
    <link>/tags/django-ninja/</link>
    <description>Recent content in Django-Ninja on CS 347</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="/tags/django-ninja/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Django Ninja Quickstart</title>
      <link>/activities/django-ninja-quickstart/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/activities/django-ninja-quickstart/</guid>
      <description>&lt;p&gt;In three short pages you&amp;rsquo;ll build a small &lt;strong&gt;chat API&lt;/strong&gt; for the chat rooms in your locallibrary: people can browse rooms, filter and paginate them, read a room&amp;rsquo;s messages, sign in, and post a message that shows up live in the chat page. Along the way you&amp;rsquo;ll see most of what makes Django Ninja pleasant to use: type hints that validate input, schemas generated from your models, interactive docs, auth, and routers.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Django Ninja Tutorial</title>
      <link>/activities/django-ninja-tutorial/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/activities/django-ninja-tutorial/</guid>
      <description>&lt;p&gt;This tutorial builds one realistic API from start to finish: &lt;strong&gt;TaskFlow&lt;/strong&gt;, a task tracker for teams. Users sign up, create projects, invite members with roles, and track tasks with assignees, labels, statuses, due dates, comments and file attachments. Each part adds a feature to the same codebase and shows the Django Ninja tools that make it work.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-youll-build&#34;&gt;What you&amp;rsquo;ll build&lt;/h2&gt;&#xA;&lt;p&gt;By the end of Part 8, TaskFlow has these endpoints:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
