First, I want to say I love djangopackages.com. I direct people to it all the time! It provides breakdowns on a variety of Django related packages. I struggle to keep up with all the new libraries folks are building or have built, but the site helps me discover them.
Similarly, our community has a lot of published knowledge on the web. If we consider DjangoCon talks alone, there’s hundreds of videos out there. I would benefit immensely from having a categorized collection of those videos. Mix in all the blogs, podcasts, release notes and gists, we’d have a mighty library of knowledge nuggets.
Enter Django Cairn. The passive trail guide for a Djangonaut’s journey.
My goal is to create a site to direct Djangonauts to that knowledge. The site won’t host the content. Instead, it’ll be an index for information everywhere else on the web. It will exist as a facilitator to existing sites and blogs.
Ideally the content will have existing categorical tags, but I suspect some additional curation will be beneficial.
I feel like an easy thing to start with is all the past DjangoCon talks and tutorials. The previous years’ conference sites are still up which should make it easy enough to track down the content. The next area would be identifying folks and organizations that publish blogs that have RSS feeds or similar. Other areas that would be great to include:
- SaaS and PaaS blog posts.
- DevRel Twitch streams.
- Particularly helpful Stack Overflow questions and answers.
I believe this can be successful in our community for these reasons:
- It provides a research center to compliment discovery via the Django Newsletter.
- It encourages Django specific content creators by providing another marketing channel.
- The purpose is simple, catalog existing content into a single repository.
These are some of the difficulties I anticipate:
- Finding and adding new content sources.
- Content being out of date.
- What threshold does the content need to meet?
- If there is curation or subjective opinions included, what is considered fair?
The next steps:
- Collect initial static content links, titles and descriptions.
- Categorize content.
- Determine UX and UI.
- Determine data model.
- Implement views and templates.
- Research RSS ingestion solution.
- Research content review solution.
<draw rest of owl>
Interested in contributing? Make your way to the repo django-cairn.