In terms of encouraging review questions, is it worth considering a separate category rather than a tag? A tag helps people find review questions, but doesn't advertise the fact that review questions are on topic unless a user is looking at the tag. A separate category like on Software Development would make it immediately clear to a new user that they can ask such questions.

trichoplax‭ The code review category at software development isn't very active though, compared to the main Q&A, so I don't think it serves an advertising purpose. I think the main reason for adding several categories is if the posting policies are very different for certain types of questions. For example general Q&A will encourage a minimal reproducible example whereas code review will encourage the full code without modifications. This holds true for embedded software too, but so much not for schematic reviews etc where the rules are the same as for general Q&A: clear and complete schematics, provide datasheets to key components etc.

The review tag can be given a different visual presentation if that helps, and the text at the top of the Q&A category can be edited to mention/link to reviews. Would either or both of those changes help?

Monica Cellio‭ Different colors might be interesting, as long as it doesn't turn out far too eye-catching that way (not like the status-complete etc meta tags for example that are meant to stand out).

The difference would be outlining, like the proposal tags on Proposals. We already have support for that; we'd just need to add the reviews tag to a list.

Monica Cellio‭ Hmm I had not realized there were differently formatted tags at Proposals :) I can see it now that you told me, but maybe the problem there is the opposite - too subtle.