Wide layout with split panels

[nilshoerrmann]

Symphony Factory knows two layout modes: .wide and .centered. Most sites will default to the centered layout and this is what we have been working with ourselves so far. The site we basically created the wide mode for is xPathr.com.

The question is: how will the layout and functionality of xPathr evolve?
And which extras are needed to provide a decent version of xPathr with Factory?

And a general question: Will be remove Symphony branding (like the footer) to gain more space and to make the app look more universal? Or are we just pushing the footer out of the viewport on page load?

/cc @alpacaaa, @bauhouse, @allen

[bauhouse]

The design is in progress and at the beginning stages, so it's hard to say at this point how the layout and functionality will evolve. It also may depend on how we answer the question regarding the domains.

At this point, I am going to assume that xpathr will live as either a subpage or subdomain of the getsymphony.com site, as that appears to be the consensus so far. However, for my own reasons, I would like xpathr.com to be its own domain, since I will be making a significant effort to try to extend the interest in XSLT beyond the Symphony community. Personally, I am leaning toward making the application more universal.

[nilshoerrmann]

I am leaning toward making the application more universal.

So this raises a question for me: what about making (keeping) xPathr a standalone app but offering an integrated version on the Symphony site.

With standalone I mean:

• no Symphony network toolbar and footer
• still the styling could be in line with the network

With integrated I mean:

• the forum offers an inline option to create new entries on xPathr ("xpaths"?) within the comments form
• the forum fetches the history of such an "xpath", displays links to its history within the comment and links back to xPathr for editing, forking and such

[nilshoerrmann]

the forum fetches the history of such an "xpath", displays links to its history within the comment

This could work similar to how Github displays issue or commit references inside issue tracker threads. So technically if it was possible to link an "xpath" to a discussion, xPathr could post special forum notifications about changes on the topic.

[alpacaaa]

Good stuff on the forum functionalities, completely agree.

[nilshoerrmann]

What about removing Symphony network branding from xPathr (or more precisely: not adding branding), Marco? It would help keeping the xPathr interface lean and would make it easier to position xPathr as XML/XSLT tool and not a Symphony one.

But – as a consequence – it wouldn't make much sense to have xPathr in Symphony network toolbar (the black area on the top) because if xPathr doesn't offer the toolbar itself it would become a dead end for the network: the user would loose the network context while navigating the network.

Of course it would still be possible and make sense to link to xPathr from the network sites, but position wouldn't be that prominent anymore in my eyes.

/cc @symphonycms/symphony-network

[alpacaaa]

That's something I don't really have an opinion about, I'm fine with both solutions. The only remark in removing it from the network bar is that it will have far less visibility (much as it has now, nearly zero) and I'm afraid people wouldn't adopt it.

If I think about github gists, the fact that they are clearly visible in the header and not a tiny voice in the footer is what makes them so widely adopted. It stands out, so it must be good and the cool guys are using it, I want to be one of them :)

[nilshoerrmann]

Yeah, the positioning is a tough problem: we just have to make sure that we have a return path. Removing the toolbar from xPathr takes a away that path.

I think Github has the same problem with its Gists – and my personal opinion is that their current solution is not ideal at all. But – of course – they opted for the simplest way which is: putting Gists in the main navigation although it's (for some reasons) a separate application.

I don't want to hide xPathr or remove its visibility because I'm convinced it's a good service that needs tighter integration with the Symphony site (especially the forum where we post a lot of code examples). But we need to find a solution to keep the network navigation logical.

Things I have in mind:

• xPathr could detect if the referrer is a network site and – if it is – include the network header.
• There could be two xPathr URL: xpathr.com and getsymphony.com/xpathr. Both link to the same xPathr (Symphony) install but dependent on the URL xPathr either displays with or without Symphony network toolbar and footer.