<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Frameworks on Humberto Rocha</title><link>https://humberto.io/tags/frameworks/</link><description>Recent content in Frameworks on Humberto Rocha</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 20 Nov 2022 12:52:46 -0500</lastBuildDate><atom:link href="https://humberto.io/tags/frameworks/index.xml" rel="self" type="application/rss+xml"/><item><title>Publishing at GitHub Pages with Pelican and Travis-CI</title><link>https://humberto.io/blog/publishing-at-github-pages-with-pelican-and-travis-ci/</link><pubDate>Thu, 05 May 2016 00:00:00 +0000</pubDate><guid>https://humberto.io/blog/publishing-at-github-pages-with-pelican-and-travis-ci/</guid><description>&lt;p&gt;&lt;strong&gt;First published at&lt;/strong&gt;: &lt;a href="http://df.python.org.br/blog/github-pages-com-pelican-e-travis-ci"&gt;df.python.org.br/blog/github-pages-com-pelican-e-travis-ci&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m making this post to help everyone who want to create their first website at &lt;a href="http://pages.github.com"&gt;GitHub Pages&lt;/a&gt; using &lt;a href="http://blog.getpelican.com"&gt;Pelican&lt;/a&gt; to create the pages and &lt;a href="https://travis-ci.org"&gt;Travis-CI&lt;/a&gt; to automate the task of static page generation and publishing.&lt;/p&gt;
&lt;p&gt;This guide assumes that the reader have an account at &lt;a href="http://github.com"&gt;GitHub&lt;/a&gt; and Travis-CI and have familiarity with the Python environment. The version of Pelican used at this post was 3.6.&lt;/p&gt;
&lt;aside class="tip info"&gt;
 The images have a little of Portuguese due to the original language publication
&lt;/aside&gt;

&lt;h2 id="github-pages"&gt;GitHub Pages&lt;/h2&gt;
&lt;p&gt;GitHub Pages is a feature of GitHub that enables its users to host static content (html, css, js and images) and publish on a &lt;strong&gt;github.io&lt;/strong&gt; subdomain or even to assign it to a custom domain.&lt;/p&gt;</description></item><item><title>Django Generic ManyToMany Relations</title><link>https://humberto.io/blog/django-generic-manytomany-relations/</link><pubDate>Fri, 29 Apr 2016 00:00:00 +0000</pubDate><guid>https://humberto.io/blog/django-generic-manytomany-relations/</guid><description>&lt;p&gt;Django&amp;rsquo;s official documentation nicely covers its generic relationship functionality when you have to make an &lt;strong&gt;OneToMany&lt;/strong&gt; (one-to-many or &lt;strong&gt;1:N&lt;/strong&gt;) relation, but when you need to implement a generic &lt;strong&gt;ManyToMany&lt;/strong&gt; (many-to-many or &lt;strong&gt;N:N&lt;/strong&gt;) relation, there is not much documentation about it.&lt;/p&gt;
&lt;p&gt;I recently had to implement an &lt;strong&gt;N:N&lt;/strong&gt; with a generic side, and discovered a library called &lt;a href="http://django-gm2m.readthedocs.io/en/stable/index.html"&gt;django-gm2m&lt;/a&gt; that was very useful to me in this task, and I will describe here giving tips on how to make this implementation and how to avoid possible headaches.&lt;/p&gt;</description></item><item><title>Static Websites with Lektor</title><link>https://humberto.io/blog/static-websites-with-lektor/</link><pubDate>Sat, 23 Apr 2016 00:00:00 +0000</pubDate><guid>https://humberto.io/blog/static-websites-with-lektor/</guid><description>&lt;p&gt;Theres about 4 years that I try to start a blog and during that time I created some for the community but never my own.&lt;/p&gt;
&lt;p&gt;Using publishing tools like WordPress the problem was the difficulty of customizing it and the amount of tooling that I would never use, plus it&amp;rsquo;s not &lt;strong&gt;Python&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Then I discovered &lt;a href="https://pages.github.com"&gt;GitHub Pages&lt;/a&gt;, and at the same time &lt;a href="http://blog.getpelican.com"&gt;Pelican&lt;/a&gt; by indication of &lt;a href="http://mindbending.org/pt"&gt;Magnun Leno&lt;/a&gt; and I started to do a lot things with it.&lt;/p&gt;</description></item></channel></rss>