Personal website https://benkurtovic.com/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2011-06-23-oh-look-a-blog.md 2.0 KiB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. ---
  2. layout: post
  3. title: Oh Look, A Blog!
  4. description: Just kinda playing with the idea of my own site right now.
  5. ---
  6. Hello there.
  7. As you can probably guess, I don't do web development often (or at all,
  8. really). My experience lies almost completely in scripting languages like
  9. Python, a little C++ and Java, some PHP, and a handful of other things, but I
  10. tend to stick with Python almost entirely (it's just so awesome!). Designing
  11. actual webpages (aside from coding the logic behind them – that's another
  12. story) is kinda foreign to me.
  13. I'm hoping to come up with a decent HTML/CSS design here over time, and
  14. eventually use the code in the rewrite of my
  15. [Toolserver](http://toolserver.org/~earwig) site. That desperately needs to be
  16. updated. Half of the "tools" don't even work!
  17. Either way, the Toolserver site rewrite (which will eventually be a GitHub
  18. repo) will go hand-in-hand with the EarwigBot rewrite that has been underway
  19. since April. I'm thinking that there will be a main repository –
  20. something like `earwig/toolserver-public` – that will essentially be
  21. everything inside the `public_html` folder. That will contain docs about
  22. EarwigBot and my various (new) tools, the main `index.(html|php)` file, and the
  23. CSS/image crud. Individual tools, which consist of code and web UI, will be
  24. their own repos (think `earwig/toolserver-copyvio-intersect`) which will be git
  25. submodules in the main `toolserver-public` repo. I think this could work.
  26. Right now, I have to finish up EarwigBot's `feature/config-rewrite` branch,
  27. merge that into develop, and get the live version of EarwigBot's config files
  28. updated. Once that's settled, the bot's backbone is essentially complete
  29. (finally!) The only remaining tasks are to start working on the actual wiki API
  30. interface, and when that's done, the bot tasks themselves. Easily a summer of
  31. work, but when it's complete, EarwigBot should be mostly finished, and up to at
  32. least version 1.0!
  33. So... questions? Comments? H8 mail? [Lay it on me!](mailto:ben.kurtovic@verizon.net)
  34. :—earwig