One problem about which the programming team might not be aware is that their admirable skills as seen with innovations like the above- can be intimidating for those of us who are technological troglodytes.
For example, I have a formatting question that is so basic, as to be unaskable, but of burning importance for site workability, and y…
One problem about which the programming team might not be aware is that their admirable skills as seen with innovations like the above- can be intimidating for those of us who are technological troglodytes.
For example, I have a formatting question that is so basic, as to be unaskable, but of burning importance for site workability, and yet am embarrassed to even ask. I know Support is busy, and the key questions on Product Development have nothing to do with the issue, so I can't even put it there. In the meantime, there are plenty of less exciting but actually important fixes that would really help. For a very few;;
1. In the same way that the system alerts a user if they are about the post an article without buttons, could you put some sort of occasional alert on the back-end emails? I was shocked - shocked, I tell you! - to find that somehow the email template in settings going out to free subs was empty. I suppose it is my fault, somehow, but I can clearly remember having filled it out. This sort of thing should be avoidable.
2. PLEASE darken the fonts in the new posts (where is asks to specify a Section is practically invisible). Anyone with any kind of visual disability has a terrible UX with Substack. And that goes for these chat boxes too.
One problem about which the programming team might not be aware is that their admirable skills as seen with innovations like the above- can be intimidating for those of us who are technological troglodytes.
For example, I have a formatting question that is so basic, as to be unaskable, but of burning importance for site workability, and yet am embarrassed to even ask. I know Support is busy, and the key questions on Product Development have nothing to do with the issue, so I can't even put it there. In the meantime, there are plenty of less exciting but actually important fixes that would really help. For a very few;;
1. In the same way that the system alerts a user if they are about the post an article without buttons, could you put some sort of occasional alert on the back-end emails? I was shocked - shocked, I tell you! - to find that somehow the email template in settings going out to free subs was empty. I suppose it is my fault, somehow, but I can clearly remember having filled it out. This sort of thing should be avoidable.
2. PLEASE darken the fonts in the new posts (where is asks to specify a Section is practically invisible). Anyone with any kind of visual disability has a terrible UX with Substack. And that goes for these chat boxes too.
Thank you,
CD
p