Useful bits of Drupal doc + site building init

Warning: contents are entirely stream of conscious/notes.

The best practices guide for Drupal has a lot of very important points to consider, but for my own technical edification, I'm focusing on just a few aspects. Handy list of core modules to become familiar with if not fully memorize, just so I grasp the breadth of Drupal functionality a little better. Right now I only know a few nooks and crannies! I'd love to do a big long workshop just to be taught, start to finish, how to build a basic site.

Read this next: Using test sites has some good starting points for setting up test environments, multiple servers, the sorts of things I need to be doing below (keeping test sites sych'd. synced? argh). I'll have a local install, then push to a test server (how to keep it private while being up with the same db/etc as my live site?), then from test to live. So the only problem is that my local dev env will be somewhat different from production. Forthcoming: post on Dreamhost's setup in relation to Drupal's needs. I've only posted my placeholder site up there with FTP and plain HTML files! No idea about dbs.

Ok, so. (don't even ask about that link, I don't know.) I want to actually develop my website. I want to do this with Drupal. Obviously.

Erm, or I could update my drush setup, instead. Went for a git repo this time, for my own sanity, but now apparently it needs something called Composer, too (Almost typed "composter." Guess where my mind is). I think it might be working now, hoping I don't really need to update all those php settings again. It's a wonder anything works, given how many configuration files I need to keep track of...

-Problem the first: Which version of Drupal? Do I go with D7 and have the benefit of contrib modules, established practices, lots of support? Or do I go with D8, which I'm at least as familiar with, probably more so, and get ahead of the curve and become more adept with what's to come? Keeping in mind that D8 actually incorporates bunches of modules that used to be in contrib, probably covering most of my immediate needs, but also keeping in mind that some things might still be broken, regular updates will be necessary, and the whole thing could break at any minute?

In my experience, breaking things is the best way I learn how systems work. Even though I know I'll have to rebuild bunches of times to compensate for my own learning and updates to core while it's in development, that will help solidify any new things I learn along the way. Too often I find myself figuring something out once, but then I don't run into the same situation again in my tiny bubble, so I forget it. Database setup, for instance. I need to get my head wrapped around how the DB works.

-Databases and test sites: Keeping local and test sites synchronized... using drush.
What is stored in the db? How does Drupal use its db? how is it accessed? Can I easily switch dbs? What would that be useful for? How do I move the live db back to stage and dev sites for testing? download a backup and connect? is there a faster way to get it re-connected, too? (drush!) Looks like I definitely don't want to use the same database for more than one instance of the site or I'll risk contaminating it with screwed up code. Probably reading the drush instructions for drush sql-sync will clear a bunch of this up.

What's a session variable, exactly? cookies?

Acquia cloud does this very nicely on its own with the drag and drop setup. Do I need a paid subscription to push to production? can I host my site somewhere that isn't Acquia and still use Acquia cloud? How much time should I spend playing with Dev Desktop?

What do I do on the backend v. the frontend? what will I use the CMS interface for, just content creation? Adding modules? Theming (this is a knowledge void for me right now)? Develop on a test, test the new thing, then install on the live site? What do I do frontend and what backend and then push? how much pulling should I do? I need to separate my creation phases (site building/dev and site maintenance/content updates)...

[TODOs are bold]

How My Time Vanishes

t's not that I'm unaware there are other things I should be doing, it's just that I'd rather be doing something with immediate, tangible results. Presumably this has been part of the appeal of manual labor for this generation that feels stuck and, well, flail-y. So instead of working toward long-term goals, I often find myself taking solace in some small projects around the house and yard.

You're familiar by now with my gardening tribulations, and some of my more notable baking incidents. I also sew, knit, crochet, and macrame, not to mention bind custom books, rewire light fixtures, weave beadwork, and probably a bunch of other stuff I'm forgetting right now. Sometime last year (!) I picked up a pile of various twines from the hardware store to make a few more plant hangers with. After staring at my old project-to-do list for all that time I finally got fed up with myself and have started crossing things off. (First to be crossed-off was the dress I bought at the vintage shop and modified to fit and bit a little more modern (ruffles had to go)).

The next easiest project was the following collection of macrame plant hangers. When my apartments in Vermont and Arlandria lacked window ledges or sufficient sunlight, I started hanging plants in front of every decent sun-source I could. Phototropic, indeed. Some of these are from years ago when I made my first batch. The more recent ones are more awesome, I think. They're labelled on mouseover...

	Next on my macrame list is a hammock. Anyone have a pattern for a two person cotton twine hammock? I only have a single person sized pattern, not confident about load-bearing capabilities if I double it...

ps. Don't question the table I used to lay these out. It was fast. ish.

One Week Website

ow, in all fairness, this was a very optimistic concept on my part. I can put together a decent looking personal website in a week, no problem. Getting through the entire process I've outlined below, blogging and documenting each step, including research, references, background, backend, comparison shopping, self-analysis and content transfer? Not so easy.

The idea, however, in documenting the entire process is that I, and anyone else who cares to poke around, can review my notes and see the progress I've made and the time/effort I put in to doing a relatively thorough job. Thoroughness might actually be a fault of mine. I have a need to understand everything about a topic, to understand how the wheel works before I drive the car, etc. I can't just install WordPress (WP) and go with it, I need to understand how the backend works, how my data and files are structured, how I can query that database, and why that form is the right choice for me.

This means my initial process is slower than would be ideal, but I think the payoff in the long run will be greater. I have learned to let some things slide for the time being, marking them to revisit later when I have enough background to understand them better.

First, I need to figure out how to track this list. Do I want to Gitify (version track) it? repost at the end of each sub-post? certainly link back to the original list with each execution of a list item. It seems like a version-tracked version I can update and reference would be best... without having to republish every time I make a change. So I'll have to embed the list (published github page) itself:

ps. Yes, this looks ghastly. I need to publish and then iterate. I hear this is a thing you do.
pps. I see the embed doesn't work in Google Reader. Will have to figure that out, too.

Technical Testing Tribulations

ay back in November I finally staked my claim on a corner of the internet by registering and hosting a website under my name. I had stalled for almost a full year, thinking there was too much I would want to research before pinning down a registrar/host. Turns out that was the easy part (once I realised I didn't need a slew of dedicated servers in the former Soviet Bloc).

After choosing DreamHost at the recommendation of a friend and a popular website (Lifehacker, who recently re-affirmed DreamHost's dominance), all I had to do was learn how to code an entire website. And not just any website, one that would display a photographic portfolio dynamically and interactively and [buzzword] and [so on]. Ok, so I haven't quite gotten to that part yet, but the site exists and is a decent placeholder.

The holdup is that I'm the sort of person who can't just throw up something pre-fabricated and call it a day, I have to learn how to code the entire thing myself, learn databases and cascading stylesheets, from scratch. Maybe once I've done that I could take an easier route, but without understanding the background it seems too much like cheating. Besides, most of the point was giving myself opportunity to learn, given that my photos probably aren't going to start flying off the shelves (there are some up, but they, too, are placeholders).

So in the meantime I've just been using the web export feature in Adobe Lightroom (a god-send for those of us who like cataloging, integration with other applications and services and powerful but simple tools). The problem I'm leading up to is that I'd like to stop hosting the photos I use in blog posts on Picasa and move them all over to a dedicated storage folder on my website. Heck, someday I should move this blog there, too.

The problem is that to use a photo in a post, I need to have a link to the .jpg file that will never change, or at least use a relative link to just "/kitten.jpg" rather than "http:// blah/folderA/section56/kitten.jpg" and so on. So that's one solution. But I also need the photo to link to a gallery view on my website, so that the clicker can browse through other photos from my blog, and also use spiffy navigation controls to browse by keyword or just mosey back through other parts of my portfolio.

I'm not going to list how much of that I have no idea how to accomplish, because it's too overwhelming. But, I've written an entire blogpost about it now, so that will hopefully motivate me.

Oh, and the reason there are random photos of pie here is because they're hosted on my website, just... not very sophisticatedly.

Photo post: What happens when I get bored on Sunday afternoon

• I weed. I weed books, I weed clothes, I weed my life. The result is usually a bag of little-used odds and ends that winds up in my parents' house until I see fit to sort through it all (sorry about that). More to the point, weeding also results in realising that 75% of my jackets are corduroy.

• I clean and dust maniacally, including inside things, which leads back to #1, there. This week my small collection of [also little-used] makeup fell victim to my boredom. And then so did my face. Disclaimer: the most makeup I ever wear is mascara, and I have no clue what I'm doing otherwise. 

• I ponder crafty things. Aside from the long list of half-finished projects and box o' mending I've been avoiding (despite having hauled my sewing machine over here) I recently acquired some little green wool balls. There was a big tub of multi-coloured wool balls at Eastern Market a while back when I went with Wortklauberlein, and I fished out some in my favourite colour. Anyone have ideas as to what I should do with them? I was thinking poms for something scarf-like. There are 10.

Baking is exhausting

Well. I'd been meaning to make a chocolate cake of some variety for a couple weeks, and today I finally got around to it. This recipe came out of the copy of Martha Stewart's Entertaining (also see this old blog post), which I received in the mail Friday (thanks to that B&N Groupon the other day). I'm saving the actual reading of Entertaining for a time when I can sit and peruse leisurely, but I nabbed this cake recipe for now.

Chocolate almond cake comes from one of the wedding menus (for ~50 guests, as opposed to the 100 and 200 guest menus. Dear God.) at the back of the book. The original recipe actually involves making the full size, multi layer, stacked wedding style cake, and uses both this recipe and an orange almond cake alternately for the layers (with copious amounts of decorative frosting, of course). I just halved the recipe and made a basic two layer cake, instead. Some of the chocolate I'd been intending to use disappeared, and I ran out of eggs, so the chocolate glaze (which I nabbed from my Williams Sonoma book.. and quartered!) is a bit sparse. 

Anyway, the recipe specifies that you shouldn't overcook the cake, because it should be extra moist in the middle. I may have overcooked a little bit, but it's so hard to tell how done the cake is before it cools... Still, it's quite tasty. The meringue gets folded in last and provides that nice fluffiness. I just stuffed some blackberry preserves that happened to be in the fridge between the layers, but I'd rather have used raspberry, and had a fluffier frosting on top. My resident critic tells me he doesn't like buttercream frosting, but I've never tried it at home. It's likely to be a lot better than the grocery store stuff, in any case.

Meanwhile, you may notice that my accompanying photos are a little nicer than usual. I've been getting back into my photography habit lately, and have been working with a DSLR for the last month. The internal debate over what camera I actually want and whether I can justify buying it has gotten quite raucous, but someday soon...

After reading Photocritic's post about prime lenses I was eager to try one... and then I realised how silly that was. Of course, all cameras used to have "prime lenses." This zoom stuff is really quite recent (a prime is simply a lens that has a fixed focal length, eg, no zoom). So, these photos are indeedy sharper than the average bear, and more excitingly, were shot at f1.4 in my dark little kitchen at night. So HA.


And you may also notice the watermark on these images. I've actually gone and sprung for Adobe Lightroom, which has made my life a good deal easier with its editing, cataloging, web design, export... everything. I have a little project in the works...


Annnd recipe:

Wherein I wish I had better colour correction capabilities

A couple of weeks ago Marlboro VT had its annual town rummage sale. The first day, everything is for sale by donation. The second day, everything is free. There are two parts to the sale: the clothing and accessories, and housewares, which covers pretty much any random piece of junk you want to get rid of. So there I was, walking into the housewares section, located in the Town House (where Town Meetings are held each year), and lying plaintively on a table near the door was an open case with an old typewriter sitting in it.

Hello, the typewriter seemed to say. I'm old, and beat up, I could use some help, maybe a little love and a new ribbon. Just take me home, please? Don't leave me here...




Well. I browsed the rest of housewares for a while, and was leaving again when I felt its lonely little self reach out to me. Oh, all right, I said to myself, and bundled the thing up and brought it home with me. A girl and her Remington Rem-riter, a Remington Rem-riter and its girl. hm. I felt hugely guilty stripping the paint off of its casings, but I'm pretty pleased with the results. It also took a while.



The process included: dismantling the casing, unscrewing the carriage/ruler assembly, stripping the paint using a green stripper and a lot of patience, doing a coat of rustoleum primer, then a coat of copper spray paint, then some acrylic topcoat, dusting, wiping and oiling the insides, figuring out which pieces went where in what order (my notes were uniquely unhelpful), and finally, the test run. It still needs new ribbon, but it's damn shiny and happy looking now.














Somewhat ironically, or anachronistically, I don't have a printer, which leaves me without blank sheets of paper for my typewriter...