Muse PreRelease to DPS 2015
I'm producing a muse page that is responsive so that it can be used in DPS 2015.
When I have an HTML article from muse placed in DPS it loads on iPad and phone great. But when I tap on the article the top menu does not show-up.
Is this a known issue?
I should add that other Muse 2015 html articles I have place in DPS 215 that are not responsive don't have this problem.
It would then be nice if adobe would put together an explicit (in the sense even dummies can follow along) tutorial on how to add AEM UI to a Muse Published page.
Since this would be a repetitive workflow for every artical created in muse.
@BobLevine: That kind of generalization is not helping.
For every "skilled coder" there are probably hundreds - if not thousands - of other human beings who don't, won't, and can't get a grip on coding. And they have very legitimate needs for digital publishing tools. You're right: many of them will happily use some kind of template or framework solution. But a fair amount of designers will never touch a tag.
But let's go back to the problem at hand: AEM not playing nice with Muse.
A friendly Adobe staff member discovered that older Muse output (before the responsive hoopla) worked fine, so something must have crept in with a recent Muse and/or AEM update.
Would a straight-forward "dummy" tutorial on how to apply that Gesture API solution help ?
If copying/pasting/editing some necessary code into an HTML file is the solution, then why not let Muse, AEM, or even the Packager handle it ? As a temporary work-around, we consider developing a script and a hot folder to process the code into the files.
My $0.02 is that there is no such thing as an HTML solution with no coding required. Yeah, you might get away with something highly templated but to not have any HTML skills today is to put yourself at a very big disadvantage.
As I said in this other thread: same problem here.
I'm guiding a former DPS client into the realms of publishing with AEM and Muse for HTML content, but they have absolutely no experience or ambitions in coding. Let's wait for Adobe's official stance on their earlier "non-coding" approach and promise...