make design AWAP without CSS or HTML


Tickets By Priority  

Low priority tickets

expand_more TinyMCE
TinyMCE, the text editor we use for layout and styling, is extremely customizeable (for example,
As Wagneerable as Possible   Development Tickets (by status)
expand_more Wagneer
Wagneers are Wagn engineers, people who build web applications in Wagn. See Become a Wagneer if you want to ...
expand_more editing cards
At the top right of every cards you'll typically see a card menus.  To edit a card, ...
expand_more Layout
Layout rules allow you to choose a layout for any Set of cards.  And with a little knowledge of HTML




I know there's a thought to deprecate/eliminate CSS (such as float:right) from inclusion syntax. I'd be sad about this, not because I desparately want to use CSS itself in inclusions, but because I want to control as much design as possible without resorting to editing *css. Hence this inquiry about other ways to handle this sort of thing...


expand_more TinyMCE+tickets for item
Development Tickets (by status) ...

expand_more editing cards+tickets for item
Development Tickets (by status) ...

expand_more Layout+tickets for item
Development Tickets (by status)



floating should be done via wysiwyg editor (or, eventually, layout editor)



expand_less +discussion

Thought it would be good to connect this to related tickets. It is probably right that we need to do this sort of thing in the wysiwyg editor, which is TinyMCE for Wagn until we do something else.

--Gerry Gleason.....2013-05-06 15:55:27 +0000

btw, I like "awap"

--Ethan McCutchen.....2013-05-06 16:04:28 +0000

I removed the "easier HTML editing" tag because this Idea is explicitly about maximizing Wagneerability *without* touching HTML.

--John Abbe.....2013-05-07 07:15:24 +0000

Right, but the solution suggests that it will be fixed in the long run by improving the editor, which seems directly related. I guess what I'm thinking is that we should gather all the tickets that relate to improving editing or replacing TinyMCE, and make sure they are connected sensibly.


I agree that this ticket is more about inclusion syntax, i.e. having css things as inclusion options. Our main take-away is that AWAP is more important than a nebulous goal of keeping inclusion "css pure".


Implementation in the editor is a secondary issue, as either way we have to keep and extend inclusion syntax for AWAP reasons.

--Gerry Gleason.....2013-05-07 17:34:39 +0000

Agree re gathering tickets as you described. We have three tags that seem relevant to me - TinyMCE, editing cards, and Layout. Am I missing any?


In general, I think using tickets as tags is not a great idea, it makes cards like Tickets by tag by name very noisy. At some point we realized that we wanted to see relevant support tickets from any given dev ticket, and the solution we came up with was on the support ticket to link to the ticket in the discussion. Then we added an inclusion on dev tickets that finds and links to the support tickets (discussed in support tickets+*right+*structure)). If we want to make more linkages among tickets, how about expanding on that approach?


This Idea is really more of a principle than a particular problem to be fixed. We could add it to wagn design principles...

--John Abbe.....2013-05-07 21:38:25 +0000

Good idea.

--Gerry Gleason.....2013-05-08 00:32:24 +0000

+relevant user stories