Considering article options
I'm thinking about creating a template article with placeholders. The harness suggests keeping formatting light, but we can definitely write something. It's essential to avoid misinformation, so I'd need to ask the user for specifics like matchday details and scores.
Here's what I propose: I can draft a Chinese post-match report that includes the score, key incidents, and VAR discussions, or I can write a more general piece. I should ask if they want a specific report or a generic one. A little back-and-forth could clarify what they're looking for!Crafting article options
I've realized it's a good idea to ask for a few key details while also providing a fill-in template and a short neutral version focusing on tactics and VAR without scores. I can offer two options along with a template.
First, I should ask three quick questions about the desired word count, style, and if they have specific scorers and quotes in mind.
Then for deliverables, I can prepare an instant write-up (400-600 words) with generic wording, a detailed outline (1000 words), and social media snippets for platforms like Weibo.
Keeping it concise, I'll include a sample article structure with placeholders for the user to fill in later. It’ll have sections for title, lead, main text, data points, coach quotes, and match outlook with minimal formatting. Let’s make this helpful!Localizing and formatting the template
I'm thinking it would be helpful to include the template in a code block for better clarity. Following the guidelines, I know code samples or multi-line snippets should be wrapped in fenced code blocks, so I’ll present the template clearly.
Also, since we're already using Simplified Chinese, I could propose localizing it for that audience. Let’s finalize the answer with the formatted template and make it easy to understand!
\n
\n
\n
\n
\n
苏ICP备10003674号