{% extends "base.html" %}
{% block lang %}en{% endblock lang %}
{% block title %}Code{% endblock %}
{% block extra_head %}
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://larlet.fr/david/code/">
{% endblock %}
{% block content %}
  <h1>Open-Source Code</h1>
  <section>
      <article>
        <h2>Content Browser</h2>
        <p>
          A way to browser content on the Web without the navigation/social/comments crap in a readability way.
        </p>
        <h5>
          <a href="https://bitbucket.org/david/contentbrowser/" title="">Documentation &amp; repository</a>
        </h5>
      </article>
      <article>
        <h2>Django ROA</h2>
        <p>
          ROA (or WOA) stands for Resource (or Web) Oriented Architecture, it’s
          about Service Oriented Architecture (SOA) with web constraints. Django
          ROA allows you to access remote resources (API) using the Django ORM.
          Use Django’s ORM to model remote API resources.
        </p>
        <h5>
          <a href="https://bitbucket.org/david/django-roa/wiki/Home" title="">Documentation</a> |
          <a href="https://bitbucket.org/david/django-roa/src/" title="">Repository</a>
        </h5>
      </article>
      <article class="">
        <h2>Django storages</h2>
        <p>
          An attempt to regroup all Django storages. Firstly, it was just a home
          for an S3 one but now there are storages for FTP, MogileFS, Image and
          so on. Do not hesitate to participate and to submit your one! Note that
          I can’t test all submitted storages.
        </p>
        <h5>
          <a href="http://django-storages.readthedocs.org/en/latest/" title="">Documentation</a> |
          <a href="https://bitbucket.org/david/django-storages/src/" title="">Repository</a>
        </h5>
      </article>
      <article>
        <h2>Django OAuth+</h2>
        <p>
          Support of OAuth in Django. The whole specification is used
          as test and many projects use it in production.
          The "plus" fork uses the more robust python-oauth2 and fix some bugs.
        </p>
        <h5>
          <a href="https://bitbucket.org/david/django-oauth-plus/" title="">Documentation</a> |
          <a href="https://bitbucket.org/david/django-oauth-plus/src/" title="">Repository</a>
        </h5>
      </article>
      <article class="">
        <h2>Django invitation</h2>
        <p>
          Built on top of django-registration, it restricts registration to a
          given number of invited person per active user (strategy introduced
          by GMail to involve 2.0 users).
        </p>
        <h5>
          <a href="https://bitbucket.org/david/django-invitation/" title="">Documentation</a> |
          <a href="https://bitbucket.org/david/django-invitation/src/" title="">Repository</a>
        </h5>
      </article>
      <article>
        <h2>Django-fr</h2>
        <p>
          The website of the French community. It mainly contains
          translated documentation and useful links.
        </p>
        <h5>
          <a href="http://www.django-fr.org/" title="">Website</a> |
          <a href="https://bitbucket.org/djangofr/djangofrdoc/wiki/Home" title="">Documentation</a> |
          <a href="https://bitbucket.org/djangofr/" title="">Repository</a>
        </h5>
      </article>
    </section>
{% endblock content %}
