Rewriting the rules for TRIRIGA docs

Veni, vidi, vici! TRIRIGA, TRIRIGAFEEDIA, and TRIRIGA UX! But to start off, happy anniversary! Believe it or not, November 2015 not only witnessed the 2nd anniversary of my quiet “bright blue” tech blog at jay.manaloto.ibm, but also the 10th anniversary of my tech career at TRIRIGA. From the old TRIRIGA days of co-locating at the office to the global IBM days of telecommuting from home. Not a bad deal.

So why have I returned? To be honest, I was always going to return. But this year has been especially consuming, fascinating, and satisfying with my exploration of new TRIRIGA territories, namely TRIRIGAFEEDIA and TRIRIGA UX. With the former, if you remember, I created “an experimental WordPress hub that collects feeds”. With the latter, I recently dove into the world of Google Polymer.

TRIRIGA UX Article 1

Hi, my name is Jay, and I’m an IBM TRIRIGA information developer at IBM. I’ve always been pretty transparent about the origin of my TRIRIGAFEEDIA blog. But now that IBM has announced the releases of IBM TRIRIGA 10.5.0 and IBM TRIRIGA Application Platform 3.5.0 with its UX Framework, I can finally reveal the origin, design, and development of my TRIRIGA UX Articles. Wanna find out?

Pouring Polymer onto TRIRIGA docs

Google Polymer! What am I talking about? First, let me ask you this: Have you ever designed your own websites in HTML, CSS, and JavaScript? Or edited your own blog posts and switched from rich-text view to HTML view? In any case, if you’re a technical writer or developer, you’re probably familiar with HTML tags — tags like [a], [div], [img], and [p] — the basic building blocks of traditional HTML.

But what if a new web standard emerged where HTML tags were no longer the basic building blocks? What if the new building blocks were widget-like components that rendered visual effects in a single custom tag or attribute that formerly required dozens or hundreds of tags and attributes? This is where Web Components step in, a new set of W3C standards being developed by Google.

Polymer Topeka Demo

Hi, my name is Jay, and I’m an IBM TRIRIGA information developer at IBM. Next, let me ask: Where does Polymer step in? Based on these Web Components standards, Polymer is a growing library of pre-built reusable components also being developed by Google. Can you imagine a sliding or rippling tap effect added to your app with a single custom tag, instead of dozens of traditional tags?