Explain the problem as you see it
Build title still feels very primitive and definitely can improve further.
We also have lesser known techniques of displaying fields like ${X|..} or ${X|?}.
I'd love to be able to have non-fields be optional and dependent on whether fields are there.
I'd also love to be able to edit field content "in-situ" within the built title.
Why is this a problem for you?
For example, sometimes I like to wrap my field content with brackets "( )". However, given that we cannot control the optionality of these characters, they tend to just appear as empty floating characters - e.g. "node title ()" (built from ${name} (${optional field|?}). Sometimes I also use other characters like "->" or ":".
Another frustrating thing is that when I change the name of a field, it does not automatically change the text (understandably so).
It's a problem because as the size of the database increases, it becomes more difficult to maintain. These things will help to 'plug the gap' and ensure a less buggy experience for users.
Suggest a solution
I would like to propose:
1) something similar to the Live Search filters, where we can copy and paste fields directly.
2) some documentation or guided help or workflows/inspirations/use cases for people to build titles properly.
3) the ability to edit field data within the title, and not always requiring to place ${name} at the beginning of the built title which is pretty restrictive
2 Comments
Hi @Winston, I had exactly the same thoughts very recently and posted about it on Slack. I then realised there is already a similar feature request, in case you want to add up votes:
https://ideas.tana.inc/posts/178-build-marktitlemark-from-fields-conditional-text
I would like to add that some additional control about which parts are greyed out would be fantastic. I use this feature a lot, and really love how good it is at reducing the visual clutter. However, sometimes I need to manually include a certain part that I would normally have as the added stuff at the end, or the whole title is built from fields and none is greyed out. It leads to a bit of inconsistency in my nodes, and it bothered me enough that I felt the need to compromise and switch some of the latter cases to be partially manual.
Another note is that the format not being inherited from parent supertags is super annoying, and sometimes I have a node that has two slightly different supertags which both use this feature (again, slightly differently) and I want to include elements from both. But instead I have to decide which tag I want to put first so it will use that format, then put whatever the other one would be in the regular title. This part might be more difficult to solve, but I wanted to put it out there.