Skip to main content

More blog tuning

Now I had to do some more fixing on this blog.

Turns out the width of the column in the blog really didn't suit my content. I know people like reading narrow columns, but I like stuffing large images and tables into my posts, and given that my posts can be somewhat long, I think thin columns make single posts look too.. long.

So I started fiddling around with the template, and pretty soon managed to mess it up pretty bad. I ended up removing all background images, the blogspot-navbar, left-aligning the whole thing while making the header 100% wide, which is nice, but I still don't like the left-aligned content. So my CSS-knowledge is as crappy as ever, but hey, I'm a programmer, not a designer (which reminds me of another post I have to do soon: "The programming designer; a rare breed of which we are in dire need".

Now I'm adding some feedburner stuff. Took a wee while to find their JS snippets, they've got something called FeedFlare, which I can imagine is a JS snippet I can paste once, and then reconfigure from feedburner without having to mod my blogger template. Good idea. Check out the feeds somewhere to the right. Problem is adding the snippet in the bottom of each post, as this code is quite blackboxed in the new blogger templates.. Oh well, the normal feed thingie will do for now.

Took a little effort to remove all Blogger template's default feed stuff (I'm slowly replacing Blogger's template snippets with "manual" html).

Adding Google Analytics tag.. Worked fine.

Also fixed the ugly footer thingie.

Hard work this blogging stuff! Sort of like programming, web design and literature mixed into one sport :)

Comments

  1. This comment has been removed by a blog administrator.

    ReplyDelete
  2. Hei Thomas, Her på NTNU er det alltid nye tanker på systemfronten, og jeg lurer på (siden du nå har en enorm oversikt :) om du kan anbefale noen åpne cms systemer?

    Mvh.
    Kristin

    ReplyDelete
  3. Med åpne så går jeg utifra du mener åpen kildekode systemer.

    Som jeg har skrivi en del ganger i bloggen her mange ganger så er det umulig å anbefale et enkelt produkt før man kjenner kravene i deres situasjon.

    Hvis jeg absolutt må si noen alternativ så har min personlige favoritt lenge vært Magnolia, og for dem som heller ønsker en lett PHP løsning så har jeg hørt mye bra om WordPress.

    Se også min tidligere post om dette her.

    ReplyDelete
  4. Thomas
    Keep the good work.
    Great Blog.

    Brain Exercises

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --