This could be very useful. I would love it, and I'll rate your wish up and I suggest you do the same. Unfortunately, if I understand you correctly, it is a duplicate of an old rejected wish.

http://feedback.wikidot.com/wish:167
http://projects.wikidot.com/thread:158

Thanks for the +1 :D

This one is a little different, I would need someone who knows wordpress to understand this one. Hopfully one of the wikidot masters will accept this wish as well, they seem to know wordpress pretty well. There is a certain wordpress plugin that does this, I will have to look at my FTP to see more about this.

If you're talking about Wordpress shortcodes, this can for the most part be accomplished with includes (though admittedly it's not quite as polished).

I love the shortcodes plugin wikidot could use this as well, but there is another plugin for making your own wiki syntax. lol I'm not at home yet so I cant check out my FTP for the name of the plugin. Will get to this soon :)

Actually its extremely similar to Wordpress shortcodes.

That will be a very nice feature, i hope this wish will be accepted.

I was just about to add a request for something like this when I stumbled across this two year old request. +1 from me. I read the rejected duplicate, and I don't think the wikidot developers understand how powerful this can be and how much it can simplify things for users who aren't as well versed in wiki markup as us experts. Here is one potential application:

I have some fairly complex markup that I use over and over again to place specially formated boxes around certain types of content. Take the example of an "information box" with an info icon on the left and with text on the right centered verticaly. To achieve this I use the following in front of the user's content:
[[div class="xfbox"]]
[[div class="xficon" style="background: #484848 url(/local—files/_icons/xficonInfo.png) no-repeat 5px 5px;"]]
[[div class="xfcontent" style="background-color: #CECECE;"]]
[[table]]
[[row]]
[[cell]]

and the following after the user's content:
[[/cell]]
[[/row]]
[[/table]]
[[/div]]
[[/div]]
[[/div]]

This admittedly may not be the best way to achieve my goals, but stick with me for a moment as this requirement for several lines of markup before and after content comes up in other scenarios as well.

I currently deal with this by using includes. I have two pages:
First: _box:info that has all the markup of the first block above.
Second: _box:end that has all the markup from the second block above.
(actually it is more intricate as I employ nested includes and parameters at the lower level to dramatically simplify the CSS for multiple box types)

Now my users can use something like:
[[include _box:info]]
user content here…
[[include _box:end]]

Clearly, this is much easier for my wiki's users than entering all of the raw markup, but it is still an ugly solution because the begin include tag and end include tag look nothing like the built-in tags, so my users have to learn two different kinds of tag syntax.

What I would rather have is something simple and more like the built-in wikidot tags. Something like:
[[infobox]]
user content here…
[[/infobox]]

Which is clearly much easer, even if users must learn some of my custom tags.

I have a thought on how this might be implemented as well. Combine the concept of includes with two special categories: _start-tag: and _end-tag:.

First I would create the opening tag with the page name: _start-tag:infobox which would define the opening tag's code something like this:
[[tag]]
[[div class="xfbox"]]
[[div class="xficon" style="background: #484848 url(/local—files/_icons/xficonInfo.png) no-repeat 5px 5px;"]]
[[div class="xfcontent" style="background-color: #CECECE;"]]
[[table]]
[[row]]
[[cell]]
[[/tag]]

Everything above would be used whenever the tag [[infobox]] is encountered.

Next, I would create a page called _end-tag:infobox which would define the closing tag's code (if a closing tag is needed):
[[tag]]
[[/cell]]
[[/row]]
[[/table]]
[[/div]]
[[/div]]
[[/div]]
[[/tag]]

Everything above would be used whenever the [[/infobox]] tag is encountered.

Additionally, they could support parameters just like includes to make them even more powerful.

So while you can achieve everything above with includes, the syntax can be too messy for less experienced users. Allowing admins to extend the wikidot tag set on a local level would dramatically enhance the abilities of inexperienced users to create beautiful, rich content. Plus, the custom tags would be easier for me to remember than the messy include syntax. :)