From 440e0575dafed664ac03b9ea5c1c7b189000b6b5 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Thu, 24 Jun 2010 23:52:08 +0000 Subject: [PATCH] Importing NanoBlogger post "SiteCorePy" --- posts/SiteCorePy.mdwn | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 posts/SiteCorePy.mdwn diff --git a/posts/SiteCorePy.mdwn b/posts/SiteCorePy.mdwn new file mode 100644 index 0000000..aaf9f71 --- /dev/null +++ b/posts/SiteCorePy.mdwn @@ -0,0 +1,27 @@ +[[!meta title="SiteCorePy"]] +[[!meta date="2010-06-24 19:52:08"]] +As the Physics webmaster, I'm in charge of transitioning most of the +static department content into SiteCore, as the powers that be get +wise to the ways of version control. Unfortunately, I'm not the +biggest fan of SiteCore. Major gripes include: + +* Poorly conceived versioning. Some things are versioned, some things + aren't. No tools (that I've found yet) for analyzing history except + on a per-page scope. Also, can only commit changes at the page + level, which makes a single "I added alt tags to all my images" + commit impossible. +* Browser-only interface. That's right, no scriptable API short of + driving a browser through a script. This one is so huge, I'm not + really sure what else to say. Surely people occasionaly want to do + something that the designers hadn't planned for, like, oh, importing + data from a preexisting database. + +Anyhow, to overcome the major limitation, I'm [driving my browser +through a +script](http://www.physics.drexel.edu/~wking/code/git/git.php?p=sitecorepy.git). +Thanks to the magic of +[WebDriver/Selenium](http://code.google.com/p/selenium/wiki/GettingStarted) +for making this possible. + +[[!tag linux]] +[[!tag programming]] -- 2.26.2