to do list - march

"To do list" for JoeJiko.com

Updated as goals are completed or thought of.

3/10 - mostly homepage modifications

  • featured people sections/system

  • integrated questions RSS on homepage

  • music playlist for march by the 30th

  • larger social icons

  • migrate current custom CMS to MODx CMS

  • contact form

  • randomly generated feedback popups

  • shrink attention message


If you have anything to suggest, leave a comment or tweet at me :)

to do list - march

"To do list" for JoeJiko.com

Updated as goals are completed or thought of.

3/10 - mostly homepage modifications

  • featured people sections/system

  • integrated questions RSS on homepage

  • music playlist for march by the 30th

  • larger social icons

  • migrate current custom CMS to MODx CMS

  • contact form

  • randomly generated feedback popups

  • shrink attention message


If you have anything to suggest, leave a comment or tweet at me :)

JoeJiko.com priority update list for week of 7/17

Primary objectives

  • find and install an ajax/php, database driven poll system

  • integrate facebook or twitter into photos system

  • install & configure YOURLS for site hosted short urls

  • add profiles section of site (quick linking to my social profiles)

  • rearrange homepage to include photos


Secondary objectives

  • slightly different favicon for blog, photos, and ask sections of the site

  • enlarge primary social icons (facebook, twitter) on the homepage and add Google profile link

  • remove www from blog site by default

  • rethink and rewrite "about" sections


Ongoing

  • update blog theme to reflect overall look & feel of JoeJiko.com

  • allow login with google and facebook

    • develop system for logged in users to upload photos to the gallery (such as fan art and signs)



  • sketch mockup for "joe jiko friends" and "joe jiko fans"


Theoretical/Distant future

  • integrate gallery with blog
    -post to wordpress when new photos are uploaded


That should be enough for now. I'll revisit my priorities next friday the 22nd. TGIF!

JoeJiko.com priority update list for week of 7/17

Primary objectives

  • find and install an ajax/php, database driven poll system

  • integrate facebook or twitter into photos system

  • install & configure YOURLS for site hosted short urls

  • add profiles section of site (quick linking to my social profiles)

  • rearrange homepage to include photos


Secondary objectives

  • slightly different favicon for blog, photos, and ask sections of the site

  • enlarge primary social icons (facebook, twitter) on the homepage and add Google profile link

  • remove www from blog site by default

  • rethink and rewrite "about" sections


Ongoing

  • update blog theme to reflect overall look & feel of JoeJiko.com

  • allow login with google and facebook


    • develop system for logged in users to upload photos to the gallery (such as fan art and signs)


  • sketch mockup for "joe jiko friends" and "joe jiko fans"


Theoretical/Distant future

  • integrate gallery with blog
    -post to wordpress when new photos are uploaded


That should be enough for now. I'll revisit my priorities next friday the 22nd. TGIF!

Setting up the photo gallery today!

Working with WideImage today to create an image/media management system inside of my application's framework.

Do any of you have suggestions for the best way to organize a database schema to reference images in a file system?

My current approach is to run sha1_filename on the image to generate a filename, then store the image to the FS in an image folder path above the root.

I'm creating two sub folders to house the images based on the sha1_filename, for example:

83d8281665383fa968f34a91e7539b947d3a59d1.jpg is stored as
IMAGES_ROOT/83/d8/83d8281665383fa968f34a91e7539b947d3a59d1.jpg

My current reference table SQL looks something like this:

CREATE  TABLE IF NOT EXISTS `images` (
`id` INT(20) NOT NULL COMMENT 'image id' ,
`filename` VARCHAR(255) NOT NULL COMMENT 'relative path to file on FS' ,
`size` INT(8) NULL COMMENT 'file size' ,
`width` INT(5) NULL ,
`height` INT(5) NULL ,
`metadata` TEXT NULL COMMENT 'image meta' ,
`mime_type` VARCHAR(45) NOT NULL COMMENT 'mime type\n' ,
`caption` TEXT NULL COMMENT 'image caption' ,
`uploaded_by` INT(5) NULL ,
`created` DATETIME NOT NULL ,
`modified` DATETIME NULL ,
`live` TINYINT(1) NULL DEFAULT 1 COMMENT 'publicly visible?' ,
`deleted` TINYINT(1) NULL DEFAULT 0 COMMENT 'shown in listings' ,
PRIMARY KEY (`id`) )
ENGINE = InnoDB

Eventually I'm going to add tags and  categories, but that can also be done later.

Thoughts?

 

Update 2/26
I ended up using  PHP Image Workshop instead.

Why? It's got a better website and um.. the code is newer.

Right now the photo gallery isn't finished, but it's up if you're interested.



 

I've uploaded over 500 photos. Enjoy!

Setting up the photo gallery today!

Working with WideImage today to create an image/media management system inside of my application's framework.

Do any of you have suggestions for the best way to organize a database schema to reference images in a file system?

My current approach is to run sha1_filename on the image to generate a filename, then store the image to the FS in an image folder path above the root.

I'm creating two sub folders to house the images based on the sha1_filename, for example:

83d8281665383fa968f34a91e7539b947d3a59d1.jpg is stored as
IMAGES_ROOT/83/d8/83d8281665383fa968f34a91e7539b947d3a59d1.jpg

My current reference table SQL looks something like this:

CREATE  TABLE IF NOT EXISTS `images` (
`id` INT(20) NOT NULL COMMENT 'image id' ,
`filename` VARCHAR(255) NOT NULL COMMENT 'relative path to file on FS' ,
`size` INT(8) NULL COMMENT 'file size' ,
`width` INT(5) NULL ,
`height` INT(5) NULL ,
`metadata` TEXT NULL COMMENT 'image meta' ,
`mime_type` VARCHAR(45) NOT NULL COMMENT 'mime type\n' ,
`caption` TEXT NULL COMMENT 'image caption' ,
`uploaded_by` INT(5) NULL ,
`created` DATETIME NOT NULL ,
`modified` DATETIME NULL ,
`live` TINYINT(1) NULL DEFAULT 1 COMMENT 'publicly visible?' ,
`deleted` TINYINT(1) NULL DEFAULT 0 COMMENT 'shown in listings' ,
PRIMARY KEY (`id`) )
ENGINE = InnoDB

Eventually I'm going to add tags and catagories, but that can also be done later.

Thoughts?

Setting up the photo gallery today!

Working with WideImage today to create an image/media management system inside of my application's framework.

Do any of you have suggestions for the best way to organize a database schema to reference images in a file system?

My current approach is to run sha1_filename on the image to generate a filename, then store the image to the FS in an image folder path above the root.

I'm creating two sub folders to house the images based on the sha1_filename, for example:

83d8281665383fa968f34a91e7539b947d3a59d1.jpg is stored as
IMAGES_ROOT/83/d8/83d8281665383fa968f34a91e7539b947d3a59d1.jpg

My current reference table SQL looks something like this:

CREATE  TABLE IF NOT EXISTS `images` (
`id` INT(20) NOT NULL COMMENT 'image id' ,
`filename` VARCHAR(255) NOT NULL COMMENT 'relative path to file on FS' ,
`size` INT(8) NULL COMMENT 'file size' ,
`width` INT(5) NULL ,
`height` INT(5) NULL ,
`metadata` TEXT NULL COMMENT 'image meta' ,
`mime_type` VARCHAR(45) NOT NULL COMMENT 'mime type\n' ,
`caption` TEXT NULL COMMENT 'image caption' ,
`uploaded_by` INT(5) NULL ,
`created` DATETIME NOT NULL ,
`modified` DATETIME NULL ,
`live` TINYINT(1) NULL DEFAULT 1 COMMENT 'publicly visible?' ,
`deleted` TINYINT(1) NULL DEFAULT 0 COMMENT 'shown in listings' ,
PRIMARY KEY (`id`) )
ENGINE = InnoDB

Eventually I'm going to add tags and  categories, but that can also be done later.

Thoughts?