:-)

We should have a page up at http://www.lostdecadegames.com/lostcast/ that lists out all of our podcast episodes.

Depends on either #10 or #27.

Something like a sword covered in ivy or something that looks medievaly or whatever.

We should create a data structure for podcast in _config.yml which is used to generate the lostcast.xml file. (As opposed to adding new items directly to lostcast.xml)

We'll need the following fields:

• Title
• Subtitle
• Summary
• URL
• Publish Date
• Duration

Dive in to Jekyll categories. Here's what we'd like to have:

• Posts contain N categories. (Add categories YAML to each post)
• Category specific landing pages. For example, a page which lists all posts in a "tutorial" category.

I found that GH Pages supports rewriting /name to /name.html. Because of this we don't have to place our subpages in folders as index.html.

I think we should change the following files:

• /contact/index.html -> contact.html
• /support/index.html -> support.html
• /games/index.html -> games.html
• /onslaught_arena/index.html -> onslaught_arena.html

What do you think @richtaur?

:-)

Include related posts data in site.related_posts on the post page.

Described here: https://github.com/mojombo/jekyll/wiki/Template-Data

We check email regularly and nobody uses the UserVoice thing anyway. Should also shut down the UserVoice account.

Code looks like ass on our new site. Dunno what it should look like exactly but it needs syntax HL!

The more we write, the more we'll need it.

I think we can have a cleaner LESS/CSS solution. Here's the plan:

• Keep LESS files in _less
• Add an additional all.less file which is simply includes the rest of the LESS files via @import
• Using less.app auto compile all.less into media/css/all.css which is then included in _layouts/default.html

Advantages:

• Keeps usage of less.app to a minimum
• Removes duplicate CSS caused by using @import "common"; at the top of each of our LESS files

Will try to prototype this soon-ish.

Seems to work well in testing, let's bring it to production. Mostly just needs a nice presentation somewhere on the post template.

Would be nice just to have in a post like author: geoff then pull in the various author's settings (name, gravatar, twitter, etc.) from an include file.

What's up now?

http://www.lostdecadegames.com/games/

The simple list is pretty lame. We should have entries for each game with the following:

• Name of game (linked to specific game landing page, e.g. http://www.lostdecadegames.com/onslaught_arena/)
• Screenshot or logo
• Summary text
• Direct links to the game/app in various forms (web, CWS, iTunes, Android, etc)

Ideally we can store the games data in _config.yml and render that similar to how the Contact Us page is handled.

Google depracted the font we were using (Open Sans Condensed 400) so now we need to pick something new. (The Open Sans Condensed Book 300 looks like shit.)

We'll embed this font locally just like Prociono.

The "Lost Decade Games" title text looks pretty lame ATM.

Intermittendly there are CSS rendering bugs with the site. See image below:

http://i.imgur.com/A62eg.png

YEAAAAAAH BABY! Let's put some text around it!!

Need some styling of inline code tags. For example, function names enclosed in backticks using markdown.

Good call on mentioning the MIT license in the README. On that note we should probably put LICENSE files into our repos just for good measure?

I'm thinking:

• Quick pic/blurg about us
• Our games listed out more concisely, e.g.
• Lava Sword play now
• Onslaught! android * ipad
• Onslaught! Arena play now
  etc.

Not sure if it should go above or below the Onslaught! stuff.

Compile the LESS to CSS before pushing so people with JS disabled (damn them!) can still have styles, and to avoid weirdness like when the JS loads before the CSS.

Seems to be a GitHub Pages issue, we've filed a ticket with them.

Google decided to deprecate one of our fonts (OpenSans). We should host the font CSS and files locally to prevent this problem in the future.

Posterous (and us probably) switched between h1-3 a lot, should ensure those are consistently used.

Span class="quote" divs are sprinkled around, some kinda like "quote from this blog" that I don't like anymore. Remove!!

Some ideas are like dark night sky, fades to a dark night with a mountain at the bottom or something. Maybe just some moss and shit over the bottom footer plate.

We're nice guys, we love helping players of our games with issues, let's make the page reflect that.

On the post page. Lotta empty space in that area, fill it with icons to Twitter/GitHub.