Learn Jade: Port your Resume
A meaningful way to learn Jade is to port your resume to Jade. Start by learning the Jade basics. Use the HTML-to-Jade converter to do most of the work. Then do the interesting stuff. Use jade includes to include a single element, maybe different introductions depending on the URL. Use Jade Extends to make a whole suite of changes. You might have a short version of your resume, and a long version of your resume. The short one is quick to read, the long one has all the gory details. They both share the same layout. And of course it is easy to do multi-lingual resumes. Use JSON to bring in dynamically changing data, maybe your availability date.
To manage multiple resumes, you create a tree of folders. Each folder has its own URL. In the root folder you place your basic resume template and possibly the default introduction and job descriptions. The basic resume template imports the relevant content. The branches below that are for different markets. Maybe one for SQLAlchemy, one for Django, and one for Ember. Each market folder has a different introduction. The branches below that might be for different jobs, maybe you emphasize different parts of your work history.. When a browser accesses a folder, it uses the local content, and acquires the other content from parent folders. So when accessing the Django market folder, it acquires the basic resume template from the root folder, which imports the local Django introduction. For a particular customer, you might have a local local job description, but acquire the introduction from a parent, and acquire the resume template from the root. Once you understand acquisition, this makes it really easy to maintain a family of resumes.
Here is the list of competing products. Let me know if I missed any.
Zopache.com is my blog about Zopache, Grok, Zope, ZODB and Python. It is written in Zopache, and organized as a subject tree.
Use the expandable tree on the left to find the topic of interest to you.
Here is some additional information. You can skip it.
Here I review different options for single page web platforms.
In the zope world, there are many topics that cut across different products. Such subjects are documented in this section.
Zopache is not just a bunch of TTW objects. It is a different computational model than either Zope2, or Grok/ZTK. All three support a ZODB tree of persistent objects with child references. Grok, ZTK and Zopache also have parent references. Unlike Zope 2 TTW, Zopache TTW allows references to remote branches of the tree, making Zopache TTW into a graph database. Unlike ZTK/Grok, Zopache hides both python namespaces, and the Zope Component Architecture from beginners, making them available to advanced developers.
Zope is very interesting. Both hugely promising and hugely difficult. Grok makes it easy to use. Zopache makes it trivial to use. But it still suffers from too much complexity. In particular registering widgets was a terrible idea. More on this in the section on Forms.