===== CSS-driven link tails===== Wikka currently gives admins the option to configure a specific tail for external links in the [[Docs:ConfigurationOptions | configuration file]]. For example: [[http://www.google.com | Google]] (see the small infinity symbol appended to the link). I see two issues in the current implementation. ===##span## vs. ##:after## selector=== The tail is currently rendered through a #### that displays the tail as configured in the config file. It would make more sense IMO (especially as soon as we allow [[TestSkin | multiple CSS stylesheets]]) to render it through an ##a.ext:after## selector. Tails are layout, not content, and they should consequently be handled by CSS. === Different classes for different kinds of link === Currently, only external links have a dedicated class and tail. If the link parser is modified, dedicated classes, titles and tails could be given to specific kinds of link. I think this could be applied both to link types and Wikka handlers. For instance (titles are displayed on mouse roll-over): === Link types === ~-Internal link: ""HomePage"" ~-Internal link to missing page: ""MissingPage"" ~-External link: ""Google.com"" ~-Userpage link: ""DarTar(USER) "" ~-FTP link: ""ftp://xxx.xxx.xx(FTP) "" ~-MAILTO link: ""DarTar(EMAIL) "" ~-CALLTO link: ""DarTar(CALL) "" ~-Handlers: ~~-Edit handler: ""LinkTails[edit] "" ~~-Backlink handler: ""HomePage[backlinks] "" ~~-Clone handler: ""LinkTails[clone] "" Tails need not be textual, they can be configured as icons as well, for instance: MAILTO link: ""DarTar  "" Userpage: ""DarTar  "" ---- CategoryDevelopmentFormatters CategoryLayout