Tutorials

A Grok-Centric Explanation of Adaptation

Adaptation is a central concept in the Zope 3 Component Architecture. This explanation approaches it from a Grok perspective.

Adder: an adding machine sample application

The most basic Grok app that is still of some use: an adding machine with tape.

Contribute to the Grok Documentation

Guidelines, policies and help for how you can contribute to the Grok documentation effort.

Installing and setting up Grok under mod_wsgi using Repoze

Repoze allows Grok to run behind any WSGI server. This tutorial will show how to install Grok behind the Apache web server and mod_wsgi using Repoze on a brand new Linux virtual server.

Introduction to zc.buildout

Jim Fulton's tutorial for using buildout, originally given at DZUG 2007

Macros with Grok

Macros are a way to define a chunk of presentation in one template, and share it in others. Changes to the macro are immediately reflected in all of the places, that share it.

Making a website that uses layers to enable a mobile enabled version of the site

As an example application we're going to develop a very simple site that uses macros and then later add a layer dedicated for mobile phone browsing without having to put in "if" statements in your templates to accommodate for the differences you'll want to apply.

Navigating To Transient Objects Tutorial

Thanks to the magic of this database, your web apps can create Python objects that are automatically saved to disk and are available every time your application runs. In particular, every grok.Model and grok.Container object you generate can be written safely to your application's Data.fs file. But sometimes you need to create objects that do not persist in the ZODB, wonderful though it is.

Permissions Tutorial

Zope 3 and Grok come with authorization capabilities out of the box. While a vanilla Zope 3 application protects all content by default and performs authorization checks on the content objects themselves, Grok allows access to everything unless you explicitly restrict it. The authorization checks here are done based on the Views used to access (display/manipulate) the content.