Mac web authoring for non-experts: My choices 2015.

In the beginning we wrote web pages in BBEdit and we FTPd them to a NeXT box.

Things progressed quickly. Almost two decades ago, when Microsoft FrontPage 97 was released and Macromedia created Dreamweaver, there were many powerful Windows applications for creating largely static web pages - with dynamic reflow based on HTML tables [1]. Operating systems, like Windows 95, shipped with a native web server. Netscape added Composer, fulfilling TBL’s original vision of the web as authoring environment. Non-technical users worked with server based systems, ultimately producing millions of web pages on sites like GeoCities [3].

Technology has moved in odd ways. There’s nothing quite like mass market FrontPage today, though Sharepoint Designer/Wiki came close and SeaMonkey survives. Dreamweaver is the strongest survivor of the original era, but it has evolved into a high end tool leased for $20 a month. I don’t think there’s a practical way to move Dreamweaver content to another platform, so adopting Dreamweaver is a deep commitment to the Adobe platform.

At one point I thought the Wiki would fill the vanishing mid-market niche [2], but Wiki solutions seem to have stalled out - much like WebDAV technologies. iWeb/MobileMe came and went quickly - an early sign of Apple’s decade (so far) of dysfunctional application development and fondness for destroying customer data.

Today developers hand code web sites in Coda, a programmer’s tool not so different from the BBEdit we started with. Other experts use Adobe's deep lock-in solutions, from Dreamweaver to Muse ($15/month) or open-source server-based WordPress (Less technical users some might use Blogger in a similar way).

For non-experts Weebly’s small business oriented server side authoring platform is an option, but it’s another deep data lock commitment to one vendor. Google Sites, amazingly, is still around, but focused on intranet solutions.

There are two longlived Mac desktop products both sold for $80 on the Mac App Store: RapidWeaver (presumably inspired by DreamWeaver) and Sandvox. I’ve tried both in the past, Sandvox more frequently than RapidWeaver. Neither product supports wysiwyg table authoring. RapidWeaver was last updated in January of 2014 and has three stars in the Mac App Store; it may be in maintenance mode. SandVox was last updated in April 2015 and has recently added a hosting service (revenue stream!), it has 4-5 star ratings. It’s App Store page still references iPhoto and Aperture however. Of these two I think Sandbox is more likely to make it to 2017.

It’s rarely mentioned anywhere, but TextEdit will export to well formatted HTML, and it even has table support (since 2006 at least). You can embed images and export — but only in single file “webarchive” format. As a simple page editor it’s not too bad, and it’s as standard as anything is these days, but the image limitations are a killer. (I suppose one could similarly author in Pages then view in Pages/web and export the code.)

Similarly one could author in Blogger or WordPress (example: free wordpress.com blog) wysiwyg mode, switch to HTML mode, and paste the HTML into a text editor (Coda?) for FTP upload. Or I could author in MarsEdit (as in this post) and similar export the HTML view as a file. Nisus Express and Pro both include HTML import and export; I don’t know how well their table export works and if embedded images are exported. When I last tried them years ago they weren’t a practical HTML authoring solution.

Google Docs work quite well for sharing and editing online, but they’re not useful for a root (www) web document. Very proprietary of course, but in some ways Google Docs are the closest thing we have today to the original view/edit vision of the www. I haven’t tried sharing iCloud Pages web sharing, but it seems like it would work similarly; it also can’t serve as root page of a web site.

Of the options today, what makes the most sense for me? There aren’t a lot of options on the table, so things should filter quickly with a few constraints:

• I’d like to avoid dying products.
• I want to be able to produce a reasonably pretty looking site without a lot of effort (iWeb pretty at least).
• I’d like a solution that works with Dreamhost and it’s (typical) constraints on www/domain mapping [4]. 
• I don’t want to sell my soul to Adobe. 
• I’m not a developer and web authoring isn’t my profession. 
• I really miss wysiwyg HTML tables and table based layout, but they are clearly gone. Still, I’d love basic table support.
• I’d prefer to avoid hard data lock.
• I’d like something that managed a site and updated links when I rearranged web page relationships or renamed pages.
• I’d like to avoid major malware and security issues. Static sites are very nice that way.
• Mac (or course) or Safari if server based.

Based on my review of the options, and applying my constraints, it’s easy to see that my best choice is ….  is …. Ok. Nothing survived the constraints. It’s easy to see why I’ve been struggling with this for about 15 years.

If I relax a few constraints I think my least bad options are WordPress (free) and Karelia Sandvox ($80). So I’m going to try both of those — and maybe, if only to close the long loop, Coda too.

Am I missing anything?

See also

• Vermeer/FrontPage lives in Sharepoint Wiki 6/2008
• Wiki impressions: XWiki 2/2012
• Advanced Web Refs 1998. State of the web a very long time ago.
• nVu - more good news on this FrontPage replacement 4/2005. It died years ago.
• Site Studio: FrontPage LITE for OS X 2004. Didn’t go anywhere.
• The sad state of web site authoring on OS X -- and XP 11/2005. I should have clarified that my complaint was about the mid-market niche, very much like today.
• Sandvox and the return of end-user web site authoring 1/2006. I’ve tried and rejected SandVox several times over the past 9 years.
• Content Management Systems: A Macintouch report 12/2005. 
• Google launches an AJAX web authoring and hosting application 9/2006. Google Page Creator came and went quickly, followed by Google Sites (2008) which, amazingly, is still around.
• Drupal reminds me of Google Page Creator 3/2009.  It’s still around, but the Dreamhost wiki page captures my sense of it: “WordPress … is less confusing and more stable..”. It’s not available as a “one-click install” on Dreamhost.
• iWeb doesn't do tables - and OS X HTML Editor alternatives 11/2009. 
• Components of a knowledge share solution 10/2011. Not much change since then.
• WordPress doesn't have a built-in table editor 1/2012. Still doesn’t.

- fn -

[1] I think we took the wrong road when we entirely substituted CSS for dynamic tables; no modern tool approaches the table management power of FrontPage 98. Perhaps this happened because it was insanely difficult to manage table authoring by hand, it was really a job computers did better than humans.

[2] Speaking of vanishing mid-market, remember when personal finance software was big? Intuit is trying to find a buyer for Quicken and its future looks quite bleak.

[3] The immolation of GeoCities, echoed on a smaller scale with the 2012 death of MobileMe’s iWeb based web pages, should not be forgotten.

[4] The odd handling of the www domain is, I think, a legacy of early net development. It is a pain in the butt.

Update 4/29/2016

Sandbox can be used free for up to 5 pages. I gave it a good try with a book site I’m working on. The lack of both drag-and-drop placement and tables made me give up on Sandbox. 

Of course RapidWeaver doesn’t do tables either, but I’m going to try it anyway.

It’s obvious that tables are insanely hard to implement; I wonder if CSS support made the challenge even greater. I wouldn’t mind an editor that handled CSS tables, but no tables at all reminds me of all the software functionality and value we have lost over the past 15 years (yeah, Apple Aperture, I miss you.)

Oh, and vendors, please stop trying to tell us we don’t really want tables or that HTML tables are fine. You are just insulting our intelligence. Just say something like “tables are extremely hard to do …”

H2O Wireless just redid their prepaid accounts. Might be time to abandon ship.

H2O Wireless has been a rock-bottom ultra-cheap prepaid AT&T MVNO for our kids phones. I’ve used ‘em for years Our #2 son, who never uses his phone, cost us about $40 a year ($10 minimum payment, lasts 3 months). #1 son costs us more, about $150 a year, largely because we use Find Friends to track his cycling. HIs data use on an unlocked iPhone increases costs. #3 (daughter) was costing about $20 a month in texting fees alone; we relented and put her on our AT&T mobile share plan.

Alas, our H2O days may be ending. Today I’m unable to access my H2O account. Sometime in the past 1-3 weeks H2O redid their account system for prepaid users. Each phone must have its own account, and for web access each phone must be registered with a distinct email and password. It’s no longer possible to manage multiple phones from one account. In an extra twist our phones may be orphaned — our account number was my personal AT&T mobile number, and that’s not an H2O number. Their system upgrade didn’t account for that possibility.

Well, I knew that was a risk with a bottom-feeder service. I’ll have to see if I can salvage one of the accounts — it has a fair amount of credit on it (since I had to pay $40 a year to keep #2’s account open, but he rarely used any service). I can setup redirects on one of my domains, so I'll create unique emails of the form 1111111111@domain.com, give each account the same password, and see if I can salvage one or two accounts. I think it’s time to try again (ain’t easy, carriers cheat on portability rules all the time) to port #1’s primary number to AT&T.

Update

On further inspection there’s good news and bad news. 

The bad news is that the chat service rep had no idea how H2O wireless accounts work. I actually called a second time and that chat rep was following the same incorrect script — their documentation doesn’t match the site behavior.

The good news is that in reality the system hasn’t changed that dramatically. The contact number on the account doesn’t have to be an H2O number. You add H2O numbers to the account one at a time, entering a passcode (seems to make it rather easy to steal numbers, but there you go). Since I only learned this by experimenting with a new email address I seem to have moved the numbers from my old account to the new one, with balances intake.

The really bad news is even the 800 support number people have no idea how the web site works.

Oh, and one number won’t transfer. I think I just need to port that one to AT&T and live with the other two...

12/18/2015

I now have 3 devices that use H2O. One is an iPhone belonging to #3; his pattern of phone use means he costs $40/year still. I have another H2O SIM in a voice-only emergency phone and a $100 Android phone I bought for a book project. This is what I’ve learned with their new accounting system:

1. There doesn’t seem to be “privileged” phone number, the system lets me associated an H2O number with an email address based account. This seems to be one-time procedure, once associated you can’t move number to a different account.
2. For a new number you first activate it using their standard procedure, then from your H2O account you “add a number” They send a text code, if you enter that code you get the association. It sometimes shows an error message even when it works. 
3. My latest SIM was an LTE SIM, but the standard data activation stage failed. I found a manual configuration page that worked even though H2O’s web site claims data activation requires a prepaid plan. I activated it constrained to 3G, but I found LTE works, so that was probably not necessary.

Deleting a sparsebundle: Disk Utility Erase doesn't work either. Or does it?

Years ago OS X Mountain Lion could not delete sparse bundles containing over 262,144 bands (2TB+). I don’t know if that’s still true, but when I had to remove a 1.7TB disk image today I first tried doing an Erase using Disk Utility.

Alas, this didn’t work. When I opened the image it was indeed empty. However First Aid on the volume reported it was corrupt. When I tried deleting it I got the usual OS X hang. 

So this problem is still around…

Update: on the other hand deleting the sparse bundle in Finder took 2-3 minutes rather than 12 hours. So maybe there’s something to this. 

Mac - how do I share images to Facebook?

There should be a word for AmITheLastPersonOnEarthToKnowThis?

It’s a weird feeling. 

For years I’ve been puzzled by a lack of Mac tools for uploading to Facebook. Around 2013 or so Apple’s photo applications got that ability, but both Aperture and iPhoto have been axed (I still use Aperture, though I now avoid its native Facebook integration and iTunes photo sync). So it seems we’re back to where we started from; Photos.app doesn’t seem to have a native share option.

Except I missed this: Share on Twitter, Facebook, LinkedIn, and more — probably because by the time I adopt an Apple OS update my geek sources have moved on to the next one.

From the Finder, Photos.app, and newer apps there is a context menu share sheet extension similar to iOS, and it includes Facebook sharing. You can select multiple items and you can share to Timeline or a Facebook album. You can’t create a new album, you have to do that from Facebook. There’s no synchronization/album management (was problematic for me in Aperture anyway), it’s just an uploader.

An appreciated uploader, because I’ve never gotten Facebook’s album uploader to work for me on a Mac.

In Photos.app you can’t share directly from a Shared photo stream, but you can create an album from the photo stream images an share from that. You edit your share options (Extensions) in Preferences.

Update: BEWARE - i thought I uploaded a test album as “only me” (as above) but on Facebook it was Public. Maybe I clicked the wrong target, but be careful… 

 

iTunes 12 and iOS 8.4 photo sync bug with Aperture (and iPhoto?) causes silent sync failure for my Audiobooks

Props to app.net@clarkgoble for clueing me into this bug. I’d been seeing iTunes/iPhone sync hangs with my device, but when I returned iTunes seemed to have completed. I forgot, probably because I’m tired of tracking Apple’s issues [1], that iTunes “swallows” fatal errors during device synchronization. In retrospect it wasn’t completing sync.

The clue that I had a real problem was that I couldn’t get new Audiobooks, which must be transferred by old-time iTunes sync because they’re stuck in the 00s, to show up on my iPhone. Clark’s app.net note gave me the idea to turn off photo sync. With photo sync disabled iTunes put the Audiobooks on properly.

There are two Apple issues here. One is an iTunes/iOS bug with Aperture (and probably iPhoto), the other is that iTunes hides serious failures from its users. There’s not much hope for either bug. Aperture/iPhoto have been abandoned (as best I can tell nobody uses Photos.app) and the iTunes error-handling problem is quite old.

I’m going to also disable my Aperture screen saver module to further isolate Aperture for OS problems. Now that I have a workaround for Apple’s ancient network share photo slideshow bug I’ll just export our slideshow images to a thumb drive hanging off our Time Capsule.

[1] Apple’s software engineering issues are impressive. At this point Tim Cook has full responsibility — failure of a major organizational function is always the CEO’s responsibility.

Aperture - I think the Facebook integration may be bad news.

I ran into some Aperture issues lately, and in the process of debugging I created a new instance of my @40,000 image 300GB Library.

After the rebuild one Facebook album was empty, an album that showed with the number ’84’ in its title …

It’s not the only empty Facebook album, there’ve been a few over the years. There was also this:

Yeah, that’s weird.

I think I know what happened to the “Kayak” album — I think those were the images that behaved oddly. I exported them, deleted them in Aperture, and reimported. They were never 84 though — that’s weird enough that I’m going to dig through old backups to inspect older versions of Aperture. I suspect the count is a bug of some kind.

I don’t need this kind of risk. I loved being able to export albums to Facebook, but synchronization is hard, I don’t have much faith in Apple’s software engineering at the best of times, and Aperture is a dead product. 

So I went to remove my Facebook credentials from Aperture and I got this…

3996? 25 maybe. Yeah, this thing is really buggy. Since I was working from a reconstruction of my still existing Library I went ahead and removed. Here are the before and after image counts:

Yep, no change.

Now to try rsync -avnc $SOURCE $TARGET to see if I can figure out what did or didn’t make it to the reconstructed Library.

Update:

Tonight I started using Photos.app as an adjunct to managing my iCloud shared albums. I noticed it does not have Facebook integration. Pretty strong hint there.

I’ve setup a completely separate Library for interacting with Facebook — if nothing else it can be a convenient uploader and album manager. That way there’s no risk to my core Library. I’ll have to figure out some automation for moving images between the Libraries and up to Facebook.

Update 8/13/2015

I clearly don’t know how to use rsync. My attempt just returned a list of all the files in my original Library. Diff took overnight, but returned a list of files only in the original. I opened up the Library with Finder’s ‘Show Package Contents’, navigated to the Masters (what I really care about) and then drag-dropped the folder into terminal diff -rq to get:

diff -rq /Volumes/Media/Backup/Current.aplibrary/Masters /Users/jgordon/Pictures/Current.aplibrary/Masters

This returned a list of 50 files. Which was kind of worrisome, but on inspection they were all thumbnails that I’d found and purged; under some conditions, perhaps related to buggy/dangerous Facebook synchronization, Aperture misfiles lost thumbnails as Masters.

Audiobooks not showing in iOS 8.4 iBooks? That's because they're still like Movies used to be. Also, The Great Courses.

Decades ago I talked about a personal dementia prevention solution. A dementia test application would be hidden in the OS, but about once a year it would randomly launch. Once it appeared I’d have to complete it — or a lethal shock would be administered. Fail the test — get the shock. The shock would look like an accidental short-circuit, so life insurance would pay out.

I like to think ahead.

I’m pleased to report that today we do have a dementia test, though we’re still working on the electric shock. The test, of course, is Apple’s iTunes and related iOS apps. If you can make them behave then you’re still a potentially viable worker; not yet ready for the Soylent factory.

I gotta admit, things are getting a bit worrisome. For example, today’s audiobooks adventure. It started when Emily decided to pick up some lectures from “The Great Courses” (which we once new as the “Teaching Company”, indeed that’s still the corporate name). We started listening to these about 25 years ago, playing cassette tapes while driving our Mazda 323 cross-country and spritzing ourselves with water spray (no air conditioning).

It’s been a year or so since we bought from them — these days I mostly listen to In Our Time Podcasts [1]. We got one of their 80% off flyers [2] though, and it was hard to resist tormenting the kids with automotive education. So we bought a few. The distribution is a bit complex — DVD or CD (for most lectures you really only want audio, but we did DVD for the $40 photography class) or “Windows” / “Mac” files [3] and (usually) supplemental streaming.

What they don’t mention is that many of their lectures can be purchased from iTunes for less than the CD or audio file download costs in iOS friendly Audiobook format. That’s a lot more convenient than their other options, and cheaper too. So I bought two lectures that way, a short history of London (#3 and I are visiting in October) and Daily Life in the Ancient World [4].

That’s when the dementia test showed up. It’s been years since our last audiobook purchase (viz: In Our Time) and everything has changed [7]. It took a couple of Google searches to figure out that Audiobooks were now tucked away in an obscure corner of Apple’s brutally neglected iBooks.app. Some dungeon-chained Apple product manager decided they could be considered a kind of “Collection”. [5]

Okay, but I’d purchased them and they didn’t show up. Why was that? My Movies and Music and book-book purchases show up in iCloud. Why not these audiobooks? Google found me some documentation, the same team that decided an audiobook was a kind of “Collection” introduced an obscure control as an attribute of a particular Collection called “Hide iCloud Books” (even though these aren’t, you know, Books. Do you see a trend here?)

So I turned that Off, so they wouldn’t hide. That’s a double negative I guess.

Except they still didn’t show up.

This began to remind me of the old days, when we’d have one chance to buy music or videos and everything was managed and backed up using iTunes. Yep, it’s just like that, unchanged from 2013. Download to your phone, and it stays on your phone [6]. No iCloud joy, no freedom from iTunes, you need the old beast still.

Just audiobooks mind you. And, of course, it’s not documented.

Apple must be a desperate place to work these days…

- fn -

[1] Still using Apple’s awful Podcasts.app. Podcasts.app and iBooks.app should chasten those who clamor for iTunes to be be divided into separate apps. Be afraid.

[2] Their pricing is a bit nuts — high list prices and large discounts. Do look for discount codes and the like before purchasing, though the iTunes audiobook prices are often quite reasonable

[3] Their audio/video file format recommendations are bit odd, but I didn’t have time to dig into it. Does Windows 10 still prefer wmv?

[4] I’ve chatted on app.net about writing a book that would describe a ‘day in the life’, from pooping to earning money to playing with kids across history and geography. So I’m looking forward to this one.

[5] Collections used to be sort of meaningful in iBooks, but that ended a year ago.

[6] Well, not quite. If you go to your iTunes purchase record, click on problem and say you had trouble downloading, the purchases are added again to the download list. I had my original purchases, but tried that as an experiment.

[7] Very much for the worse. Audiobooks had a large regression with iOS 7. iOS 8.4 is, in some ways, a partial improvement on iOS 7. Which mostly shows how bad iOS 7 was. Tim Cook has failed to rescue Apple’s long ailing software engineering.

[8] It no longer works to manage iPhone content from both iTunes and iOS. It never worked well, but these days it doesn’t work at all. iTunes can’t synchronize device and desktop states. So if you use Audiobooks, and you have any hope of sensible software behavior, you probably need to go all iTunes for media management.

Update 8/13/2015: Audiobooks not being synchronized to iPhone

I thought I was done, but the Audiobooks wouldn’t sync to my iPhone. That turned out to be a side-effect of an iOS/iTunes bug with photo sync from Aperture. The Aperture photo sync bug causes iTunes sync to silently fail (no UI indication) prior to Audiobook transfer. Removing photo sync let the process complete.