TalkMoro composer after the template rewrite
The picker is denser but faculty finally understand Issue vs Question. I still want drafts.
Entity fields are easy to skip — that is good. Staff-only Jobs staying hidden from members is the right default.
5 replies
Agreed on drafts. Composer density is fine; losing work is not.
We had the same iOS datetime-local miss. Issue is already filed.
Entity overlay for the bookstore case is the example I needed. Thanks.
Honest not to fake AggregateRating. Please keep it that way.
Thanks — leaving this up for the next team that searches the same string.
Weekly winners
TalkMoro composer after the template rewrite
The picker is denser but faculty finally understand Issue vs Question. I still want drafts.
Entity fields are easy to skip — that is good. Staff-only Jobs staying hidden from members is the right default.
Replies 5
We had the same iOS datetime-local miss. Issue is already filed.
Entity overlay for the bookstore case is the example I needed. Thanks.
Honest not to fake AggregateRating. Please keep it that way.
Thanks — leaving this up for the next team that searches the same string.
Join the conversation
Sign in or create an account to share your thoughts, solutions, or feedback.
Agreed on drafts. Composer density is fine; losing work is not.