Template talk:Ent

I think that if Jeff would know XML, he could simply create a new tag in the CSS itself, called <ent>. That would leave the question, what is easier to write - "{{ent|path_track}}" or "<ent path_track/>"? --Andreasen 10:21, 23 Sep 2007 (PDT)

Not much of a difference really...—ts2do 12:06, 23 Sep 2007 (PDT)

The big difference would be if Valve allowed us to set the CSS on our user settings page. In that way Jeff would get his highlighting, while I could just read the ents as plain text, at the same time. --Andreasen 12:11, 23 Sep 2007 (PDT)

Actually, as this template means that entities will always be linked to, Jeff is against it, as this is considered excess use of linking. Unless you can write [[{{ent|func_wholly}}]], XML tags seems like the only possibility (and don't consider writing a "{{nolinkent| }}", please). --Andreasen 20:27, 23 Sep 2007 (PDT)

One Template, two Purposes

If I may ask, why use this template for two completely different purposes? (1. a code-style link, 2. the first sentence for an entity page)
If we want to revolutionize {{point ent}}, then I'd suggest doing the first step with a new template, and not with this simple template that is being used on nearly every page. Extending {{ent}} for two distinct purposes makes it unnecessarily hard to find the pages that use {{ent}} for just one of the two purposes. And honestly, isn't it annoying to write {{ent|mode=entity|...}} every time? Why not make a new template? Template:Entity is still open.
--Popcorn (talk) 20:52, 23 January 2023 (PST)