Yeah, that's one thing I do kind of wish for on the new site: better deck tags.
This too. I am not sure what you are referring to specifically, but I hate that there is so little control over the number of columns or the number of cards in each column. I actually have a program to create decks in deck tags to ensure that I always have 3 columns when posting my EDH decks. I don't like it when I only have 2 columns because it looks poor and certain orders of the cards prevents the current tags from automatically creating 3 columns.
There are certainly better improvements that can be made, but this is my big one.
As a dev, to your dev (spoilered since 99% of people in this thread won't care):
Many modern forum post/comment submission/blog post systems and the like allow for HTML/CSS to be used. Having worked on one such system previously, without going into too much detail, I can say that it's just about running post submission through a parser and having a whitelist of tags and attributes that are considered to be safe. You strip out or reject anything offending. When I did this in the past, I used sanitize-html (granted that's only particularly useful if you're running JS server-side, like via node.js or similar, but there are guaranteed to be similar libraries for other technologies).
An alternative that I've seen done for this sort of thing is to have any HTML based posts/edits go into a review queue before they can go live, but that requires dev-savvy manpower to review them, which is meh.
I don't mind chatting with your dev one on one if you/they are interested.
But, either way, if the decision is to stick with just BBCode, I will definitely have some requests. Like, just off the top of my head after having just posted a thread, a better way to manage deck block layout (columns and such). The way that's done automatically here can be frustrating sometimes with it trying to shove everything into two columns and be super long.
Those are words.
I'll link him to this post and see what he says. It isn't my intention to blow you off, I'm passing this on as best I can and attempting to give accurate responses.
Apologies, I didn't catch that the person asking was tech savvy. I thought it was a random request of "lets just have full html access".
The board software stores all posts in s9e/xml, so I would have to write a heft extension to sanitize the input and then convert it into the proper xml/s9e. Such would definitely take some time, and would definitely take a back seat to the myriad of other things we're wanting. That said, tag/property filtering is something that I want to add to the front end CMS eventually, so it's entirely possible that when it's worked out I can port it over. So hopefully down the road perhaps.
Before that, I'm fully willing to add ALL the various tags and parameters that we need. My goal is to have the basic usage as straight forward as possible, so the average user can use them intuitively, and also have them fully customizable for the more advanced user.
Our new [BOX] tag is a good example:
And I'm absolutely willing to add more optional/defaulted parameters as we need.
For [DECK]s, currently they use css columns to allow the browser to do the column breaking. That's not set in stone, and needs some more testing, but so far it's been rather good. Adding a COLUMNS parameter to specify the number of columns is doable. My only concern would be how to handle it with Mobile. I've been painstakingly careful that nothing anywhere ever makes a mobile screen have to scroll sideways. It might just have to force it back to 2 columns regardless at a certain screen size.
First of all, that is super cool. Second, will there be another "Tag Explanation Thread" to go over all the different options each tag offers? Especially if they are different than the current tags?
There will be two:
One for "these are the basic tags and how they work"
Another for "This is actually everything you can do"
I'm trying to make them as "backwards compatible" as possible, but there will definitely be some that have to change in order to best serve stronger function. For instance, [hr]black[/hr] is what we have here, but [hr] (that's it, no closing tag, etc) will work easier for the average user. We can then add width, color, size, dashed/dotted/solid, etc, to make it a real customizable line for those of us who really want to control the look and feel.
Passing it on to the dev is exactly what I was looking for.
Feel free to reach out to me directly, just note that I'm juggling quite a bit between both sites, developing, setting up, etc, so my response time might be poor.
It's my goal to give primer writers everything they need to have full control over the look and feel of their primer. If you're going to invest the amount of time it takes to really do a good primer for the love of the game and for the benefit of the magic community, the least I can do is make sure you have every tool you need at your disposal. If we're lacking something, at launch or even down the road, let me know.