On Wed, Dec 19, 2018 at 2:03 PM Rafael Bugajewski <raf...@juicycocktail.com> wrote:
> The one thing that comes straight up from my head is the current > complexity / pipeline necessary for generating output. A couple of months > ago I wanted to generate valid AMP pages within Tapestry. After one day of > research and a non-working proof of concept, I decided to use the Play > framework for this small customer and it worked right away. Tapestry does > some processing (necessary for other parts of the framework, AFAIK) that > makes it hard to generate valid AMP pages. I would really love to use > Tapestry here, and I don’t think it’s out of scope for the framework. > What issue, exactly? Exact HTML output? If yes, this is something that probably can be either fixed in Tapestry itself or customized implementing a MarkupRenderer. > > Best, > Rafael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
