Topic awaiting preservation: Reinventing oneself

Howdy, howdy. The Asylum still feels like "being argo navitch" - I have a lot of things to say, bite me.

Here is one of those things : I am reinventing myself.
One cool morning, I decided to move all former files of my website to the "/old" subfolder, stuff happens.

And to start afresh, on completely new ground : challenging, and I like challenges.

So, to make it even more a challenge, I have decided to expose the process : I mean, the "thinking" behind, not the technicalities.
http://www.beyondwonderland.com/plan.html

Why? Why exposing a "know-how" this way? Do not risk losing competitivity this way?
Quite the opposite : "information tends to be free", might as well make it free firsthand, and see where it goes.

So in short you aim for a lean standard compliant site with progressive enhancements up to Java+OpenGL if the user decides to.

There's a bunch or article about Mobile Web design and CSS Media Queries on dev.opera.com that might be useful.

Cheers,

Good, thanks. But there is a bit "more to it" - I don't give a damn about advertising by posting this, where's the mistery anyway?

I was interested in getting exactly the kind of insight you just gave back, and demonstrating how I think things.

The client side of things is not a big concern : it will be a style exercise though, and will get me back to being familiar with things I dropped
a while ago like Flash.

Setting beyondwo on the right track for the "semantic web" was much more important to me : I have experience with XML,
but I wanted to really give my site a solid/flexible backbone of "ideas" - in a nice shell, while keeping an accent
on easy maintenance.

Opening up the "course of ideas behind it" to the audience should just allow for controversy, hints, and all the "stumbling blocks"
involved in evolution - questions often matter more than a strict and "perfect" answer ,)

Random notes : users are not fully ready to welcome rich media, might as well simplify divisions this way :
* RSS feed for the visually impaired, instead of Lynx friendly page
* Web 2.0
* Rich Media - based on JavaFX

At least for the professional services gateway.
Which brings us to : http://www.beyondwonderland.com
http://www.mauro-colella.com

Nuff "work" done for today.

(Oh and, grouping the 6278 files that are hosted for my sole usage on theses domains was not a bad idea - might as well sort the sub domains someday).

(Edited by argo navis on 01-06-2008 20:36)

Could it be....!

awesome

Thanks Blaise As stated "somewhere" in the midst of these halls, I am still in the course of building myself up
in all possible ways - spending way too much time by the comp, mostly to build up my branding "weapons"
(and so often slipping into "toy making" mode).

The recent "buzz" is that same energy I wasted in outbursts and self doubt, simply
- I am genuinely happy it receives such a positive reaction
(verbal and webstatistical).

From my perspective, I am sharing my toys on one hand, my new experience in many areas as well,
using the feedback of people who do truly great job, and above everything else : enjoying myself.

That's the sumary for those who missed
the "official" comeback

[mumbles to self]
Ok, NOW it's starting to be fun. To really, REALLY get to be interesting.

....the old site used some homebrewed xml data with xsl transforms. Not bad, but it was not *it*, it still would
get some ugly code forks and unstable bits, and not fit quite as nicely as it should have in the "global environment" (from
a technical standpoint).

But at least it was fully accessible to Ajax queries.

Now, the best way to describe the resources of a portfolio (or a commercial site for that matter) in semantic terms is...
RDF.

Simple as that. It's meant to describe resources.
So why not store my content as RSS 2? I mean, the whole of it, emcompassing sections into larger scale rss feeds (programming.rss -> java.rss, cpp.rss, etc.).
That would make for - exactly what I need :
1) A network of rss feeds that is immediately accesible to the blind, the spiders, or SEMANTIC APPLICATIONS.
2) A backbone to be queried and remapped at will using xmlhttp (and easy to query at that, it's xml and it's a standard).
3) A backbone to query using Java/JavaFX in the same vein (with the same benefits).

Then of course, I could generate the rss using some kind of tool based on a database backbone.
But then again there are wonderful free tools to handle rss feeds.

So, watch out for the rss feeds :
http://www.beyondwonderland.com/archeo
http://www.mauro-colella.com

(it still is very much under construction, the interest of this post lies in the concept, pretty simple, already used - just not the way I'll use it -
to graft different, flexible interfaces and a data squeleton based on rss).