One is the development of a theme for our site. We've basically taken the Zen theme and using some CSS and some modification of the .tpl.php files, we have created a decent unique theme for the site. Much of the initial work can be attributed to my partner, but I managed some of the details, especially the modification of the template files. The design for our theme can from in-house, from a graphic designer who created the layout and presentation of the design using Adobe Illustrator. I have to say, .ai files are a pain to work with, glad she was able to export it to a .svg so at least I could open it and view it using Gimp.

One of the less fun things about theme development of course is checking for browser compatibility. We used the conditional commenting technique to add css just for IE (and yech! just for IE 6!). We decided against making our theme work for IE 5, and IE on the Mac is a waste of time. Safari 3 was easy to check for, since it has a Windows install, as was checking Firefox on Ubuntu. However I don't have a Mac around so testing for Safari 2 will be interesting (although necessary given Safari increasing market share).

Another development is the import of the old galleries, a sub-project I was happy my colleague handled. We had to manually find each folder (which were scattered all over the place because of the sloppiness of the old site management) and then import them using the image import module. I tried to use the nodeorder module to arrange the order of one of the galleries but the JS script they use seems to have bugs in it. I ended up having to keep the nodeorder module installed, and then manually arrange the order in the database. Bleh.

We have also started adding the old content from the original site, which has required some formatting. One of the problems we encountered here was that much of the old content is out of date, and uses very poor HTML. I've found myself editing the content quite frequently, and in many cases not importing the content at all. Moving from flat HTML files to a content management system is a tedious business.

We've also gone through and created many, many blocks, to use in our group panels, and almost as many views. We created the blocks using the admin/block/build menu because of the greater flexibility in the input format (including the ability to relatively easily use TinyMCE to create the HTML) and then all of the site blocks are located on the same menu. Our views include some specialized views of OG content (things like Og_single_post and Og_edit_table, etc...) and a few 'Views Bulk Operations', which is a terrific module. We use this so that the process of approving and managing specific site content is a lot easier. For example, in order for images to be used in a Views Slideshow on the front page, we have a form which lists all of the images. Users can toggle between 'promoted' and 'unpromoted' pictures and choose a selection of pictures to be used in the slideshow.

The vast majority of the people who will be using our site will not have publishing privileges, at least initially. The plan is to gradually allow more and more of the staff to be able to publish to the site. To this end we have developed a very simple workflow. Any time a user without the permission to 'publish directly' either creates or edits a post, the post is set to 'unpublished'. We then have a bulk operation where a user can see all of the unpublished content, and choose which of it to publish, and which of it to edit.

We have added a number of different types of content, this simplified the creation of content. Our other alternative was to use Taxonomy to separate some of the different content types (for example Elementary school news, Middle school news, and High school news) but felt this might not be totally intuitive to some users. After watching one of our teachers trying to fill in a form online for almost 20 minutes, I realized that many users do not read the form they are presented, and the taxonomy select might be easy to miss. Rather than spend time tracking down errant posts and assigning them the proper vocabulary term, we decided to go with a different content type, allowing us to use the Content Access module to fix the user permissions to their section of the school.

We are of course, using Taxonomy for managing the 'Image Galleries' on the site, and for restricting access to content. Our content is split into 'Public', 'Private' and 'Restricted'. Content which only meant to be viewed by logged in users is marked 'Private' and content only meant to be viewed by users with the administrator role is marked 'Restricted'.

Today and tomorrow we will be presenting our site, and for the first time getting feedback from some people on the current state of the website. We'll see what modifications we have to make, hopefully it won't be too onerous (like: redo the theme, or we don't like the current menu structure, redo it).

The very first task we did was to look at the information we were provided on the needs of the school in terms of menu layout and functionality. This was actually fairly easily done since we had spent the previous year working in a committee. From this, we decided on a menu structure and overall plan for our site.

Our idea is to segment the site using Organic Groups, largely because it's easy to create access control (just assign users to the groups they are allowed to view) and easy to maintain relationships between the content of the site and it's location within the site. We are also planning on using the Panels module to provide the display of the group nodes and the front page.

We plan on using the Views module to expose our site information, and using custom content types to make it easier for users to submit information for display within the correct view. We may end up using CCK to add some fields to our nodes, particularly for our Alumni users to submit user profiles and for our school bulletin items.

The site is already starting to come together a bit, which is exciting.

David

The idea is that we want to build a site which will serve as a marketing front-end for the school, and as an way to distribute information to parents and students from the school, and allow teachers to collaborate with each other and their students.

I know that Drupal can do the job. I plan on using this blog to document my process.

Today we started by setting up 2 domains for us to use, one as a back-up to the other, and installing a mirrored Drupal installation on both of them. Plan is to start with a huge bundle of modules (most of which will never be enabled) to remind ourselves of all of the features available to us through the active community at Drupal.org. We don't want to build anything from scratch that exists already.

The major difficulty with the site will be in the intended upgrades. We want to eventually have parents able to monitor their child's progress through their account on the website. So we have a lot of sensitive information that we need to protect, which means access control is going to have to be carefully checked.

Whatever, it works, cheer! I love Geogebra, I'm not ready to give it up.

Anyway, I can't for the life of me get Geogebra to work. Below is a screen-shot of what happens when it tries to run. This behaviour makes me suggest that the main applet is running, but that it is unable to find or access the other files it requires.

Java is definitely working fine, I can see Geogebra web applet files, and I can run Eclipse on Java. So far my trouble shooting steps have been to sudo chmod -R 0755 /opt/geogebra and see if it is a permissions issue. I've also tried running Geogebra as root with nother success.

Any other suggestions?

Dave

Notice anything about the three bisectors? Where do they intersect?

Please install Java 1.4 (or later) to use this page.

Please install Java 1.4 (or later) to use this page.

If you press play, you can see the steps animated one at a time.

Please install Java 1.4 (or later) to use this page.