my domain
So a very jank prototype of my future website is now hosted on my domain: goatface.org. If you just start entering random page numbers, you can find some funny crap I forgot was there, but if you start at the about page and start paging through (try turning the pages) you can see some of the actual physics content I was working on and generally what pages will look like. [Editor's note: Page turning is not meant to be intuitive, but it's a log book and it was a feature I wanted. The point of page turning will remain on the homepage and/or about page indefinitely. There will be normal linking style within so page-turning navigation is not at all required, but can be fun. There will also be a cover that is only accessible by turning page 1 back, but I didn't decide if I'm designing the image myself or scanning the cover of one of my blank log books and gimping it (more likely).]
If you don't manage to wade through like 10 pages of physics, you can check out my prototype for all images. That base polaroid is probably the only thing on the site I didn't either create myself or greatly modify. At some point there will be a credits page, since I think I have all the links and stuff still. My shell scripting engine needs a little more work for how to incorporate that nicely.
Coffee stains will be randomized. I have a lot of them I made in gimp, but I didn't implement a randomizer. Likely it will be a static random, as with real log books. That meaning, when the page is generated, it will get a fixed one (not random on reload). Of course, it might be random on website compile, meaning when I make a global update, stains may migrate.
Yes, it also has a bad ass goat favicon. Please note!
Opinions other than 'fix these broken links' or 'put more shit I might care about' are welcome.
The biggest problem right now is that the page length is fixed. You can notice that, say, the homepage, is as long as another page with content. This is log-book style. But actually, I didn't figure out a way to make it scale correctly based on the table structure of the rule lines, and even if it was possible, I'm not sure about it.
That leads me to the largest unknown right now, which is how much I go blog style or how much I keep it log book style. Something like "tags" could be somewhat useful perhaps, but more importantly is the question of comments. I find comments myself rather simple, but not necessarily any easier than email, especially if I have to log on to some blog site to comment. So I'm thinking against implementing comments. of course if I decided to, I have to figure out how to deal with the non-scaling page length. As far as blogging goes, I mean, I guess if I wanted a normal blog, I'd be running b2evolution and not like my own homebrew.
Thoughts?
Also, the page looks lame in firefox, and looks much nicer in Chromium or Safari in terms of colors and fonts. Not sure why this is. As far a I know, the basic system should work in Linux, Mac, and Windows on IE, Firefox, Opera, and Chromium. It doesn't work perfectly in Konqueror, but that's because of their shitty code, and it's not my fault they won't do partial percent tables for scaling sizes. It's not quite up to par for lynx, but it's not bad. And I didn't run W3C on it yet, but just from what I know, it should be reasonably close.
Also, don't tell me about spam bots on my email address. That's javascript generated, which bots rarely run. In other words, you can look at my nice source code before making complaints like that. Code generated by a competent person and not a machine tends to look nice, you know.
If you don't manage to wade through like 10 pages of physics, you can check out my prototype for all images. That base polaroid is probably the only thing on the site I didn't either create myself or greatly modify. At some point there will be a credits page, since I think I have all the links and stuff still. My shell scripting engine needs a little more work for how to incorporate that nicely.
Coffee stains will be randomized. I have a lot of them I made in gimp, but I didn't implement a randomizer. Likely it will be a static random, as with real log books. That meaning, when the page is generated, it will get a fixed one (not random on reload). Of course, it might be random on website compile, meaning when I make a global update, stains may migrate.
Yes, it also has a bad ass goat favicon. Please note!
Opinions other than 'fix these broken links' or 'put more shit I might care about' are welcome.
The biggest problem right now is that the page length is fixed. You can notice that, say, the homepage, is as long as another page with content. This is log-book style. But actually, I didn't figure out a way to make it scale correctly based on the table structure of the rule lines, and even if it was possible, I'm not sure about it.
That leads me to the largest unknown right now, which is how much I go blog style or how much I keep it log book style. Something like "tags" could be somewhat useful perhaps, but more importantly is the question of comments. I find comments myself rather simple, but not necessarily any easier than email, especially if I have to log on to some blog site to comment. So I'm thinking against implementing comments. of course if I decided to, I have to figure out how to deal with the non-scaling page length. As far as blogging goes, I mean, I guess if I wanted a normal blog, I'd be running b2evolution and not like my own homebrew.
Thoughts?
Also, the page looks lame in firefox, and looks much nicer in Chromium or Safari in terms of colors and fonts. Not sure why this is. As far a I know, the basic system should work in Linux, Mac, and Windows on IE, Firefox, Opera, and Chromium. It doesn't work perfectly in Konqueror, but that's because of their shitty code, and it's not my fault they won't do partial percent tables for scaling sizes. It's not quite up to par for lynx, but it's not bad. And I didn't run W3C on it yet, but just from what I know, it should be reasonably close.
Also, don't tell me about spam bots on my email address. That's javascript generated, which bots rarely run. In other words, you can look at my nice source code before making complaints like that. Code generated by a competent person and not a machine tends to look nice, you know.