3 ms·

Both have the same answer: Yahoo Store. It was written in an era when browsers had about 3 fonts, so when sites wanted to to do anything interesting with typog

by pg 16y ago

Both have the same answer: Yahoo Store. It was written in an era when browsers had about 3 fonts, so when sites wanted to to do anything interesting with typography the text had to be rendered as images. One day I'll move my site, but there's a bit of activation energy involved, because I'll have to write another site builder first.

pygy_ 16y ago
Unless you want to build it from scratch, it's a matter of a two or three dozen lines of glue code between libraries. I've recently built a custom, light CMS for a friend based on * PHP * Smarty for the templates [1] * a few YAML files for the DB [2] * Markdown and Smartypants for the text markup. One file per blog post. [3][4] * Some .htaccess magic to create clean URLs Sprinkle some CSS on top and you've got a new site :-). I didn't implement any search facility, but I guess there are several libraries that cover that functionality as well. See [5], [6] and for Common Lisp equivalents. I couldn't find a mature YAML parser but JSON is of course a decent alternative. There's [7], but the project is on hold and not documented at all. I guess the biggest hurdle would be the translation of the Yahoo Store posts into Markdown. Note that Markdown supports embedded HTML, which should make things easier. - 1. http://www.smarty.net/ http://www.smarty.net/ 2. http://code.google.com/p/spyc/ http://code.google.com/p/spyc/ 3. http://michelf.com/projects/php-markdown/extra/ http://michelf.com/projects/php-markdown/extra/ 4. http://michelf.com/projects/php-smartypants/ http://michelf.com/projects/php-smartypants/ - 5. http://common-lisp.net/project/cl-markdown/ http://common-lisp.net/project/cl-markdown/ 6. http://common-lisp.net/project/cl-json/ http://common-lisp.net/project/cl-json/ 7. http://github.com/tychoish/cl_yaml http://github.com/tychoish/cl_yaml
cool-RR 16y ago
It's funny that you don't simply hire someone to do this.
- ericd 16y ago
  Hiring and managing people for a project is a good amount of work in itself.

by pg 16y ago

pygy_ 16y ago

Unless you want to build it from scratch, it's a matter of a two or three dozen lines of glue code between libraries. I've recently built a custom, light CMS for a friend based on * PHP * Smarty for the templates [1] * a few YAML files for the DB [2] * Markdown and Smartypants for the text markup. One file per blog post. [3][4] * Some .htaccess magic to create clean URLs Sprinkle some CSS on top and you've got a new site :-). I didn't implement any search facility, but I guess there are several libraries that cover that functionality as well. See [5], [6] and for Common Lisp equivalents. I couldn't find a mature YAML parser but JSON is of course a decent alternative. There's [7], but the project is on hold and not documented at all. I guess the biggest hurdle would be the translation of the Yahoo Store posts into Markdown. Note that Markdown supports embedded HTML, which should make things easier. - 1. http://www.smarty.net/ http://www.smarty.net/ 2. http://code.google.com/p/spyc/ http://code.google.com/p/spyc/ 3. http://michelf.com/projects/php-markdown/extra/ http://michelf.com/projects/php-markdown/extra/ 4. http://michelf.com/projects/php-smartypants/ http://michelf.com/projects/php-smartypants/ - 5. http://common-lisp.net/project/cl-markdown/ http://common-lisp.net/project/cl-markdown/ 6. http://common-lisp.net/project/cl-json/ http://common-lisp.net/project/cl-json/ 7. http://github.com/tychoish/cl_yaml http://github.com/tychoish/cl_yaml

cool-RR 16y ago

It's funny that you don't simply hire someone to do this.

ericd 16y ago
Hiring and managing people for a project is a good amount of work in itself.