Alright, I need to create an SEO-optimized HTML article based on the provided app information and original review. Let me start by understanding the requirements.
First, the app is called "Compound for Windows" in the games category. The original review mentions it's a rogue-lite free-roaming shooter for VR enthusiasts. The key points to cover are what the app does, key features, use cases, pros/cons, target audience, and tips. Since the pros and cons aren't provided, I'll have to leave those out or mention that information isn't available.
The structure needs to use h2 and h3 headings, along with p, strong, em, ul, ol, and li tags. I must avoid using any classes or IDs. The content should be engaging and informative, suitable for an English-speaking IT blog. I should integrate the app name and category naturally throughout the text.
Starting with the title. The original review uses "COMPOUND for VR COMPOUND" but the correct name is "Compound for Windows" in the games category. So the title should be something like "Compound for Windows: An Intense VR Shooting Experience for Windows Enthusiasts
". Wait, but the user specified only h2, h3, etc., and no h1. Hmm, maybe the h1 is allowed as the main title. The user said "use only these tags: h2, h3..." but maybe the h1 is acceptable as the page's title. Alternatively, perhaps the user expects starting with h2. Need to check the original instruction again. The user said "write a detailed SEO-optimized article for an IT blog" and "use only these tags: h2, h3...". So maybe h1 is not allowed. Let me adjust the structure without h1. Maybe start with an h2 for the title.
Wait, the example in the original instruction shows the assistant using h1 in the previous example. Let me check the user's exact words: "use only these tags: , ,
, , , , , - ." So h1 is excluded. Therefore, the main title should be within an h2. So the structure would start with an h2 for the title.
Next, the introduction should highlight the app's purpose. The original review mentions it's a rogue-lite free-roaming shooter for VR. So the first section can introduce the app, its category, and key features. Then break down the features into sections like Key Features, Use Cases, Pros and Cons (though pros and cons aren't provided, so maybe omit or state that info isn't available). Then discuss the target audience, who it's for, and tips for using it effectively.
The original review also mentions multiple locomotion options, randomized environments, weapons and upgrades, and the ultimate goal of reclaiming The Corporation. These points should be included in the key features and use cases.
I need to ensure that the app name and category are mentioned throughout. For example, "Compound for Windows" is the app name, and it's in the games category. The use cases would target VR enthusiasts on Windows.
The pros and cons sections are empty in the input data, so I can't include them. Maybe mention that while the game has no listed drawbacks, players should ensure their system meets the minimum requirements.
The structure could be:
- h2: Title
- h3: Overview/Introduction
- h3: Key Features
- h3: Use Cases
- h3: Who It's For
- h3: Tips and Recommendations
- h3: Conclusion
Each section should have bullet points or lists where appropriate. For example, key features can be an unordered list with points like "Retro-inspired first-person shooter", "Randomized environments", etc.
I need to avoid copying the original review verbatim. Instead, expand on the points mentioned. For instance, the original mentions "intense retro first-person shooter experience" so I can elaborate on the immersive gameplay and benefits for seasoned VR gamers.
Also, ensure that the HTML is within the character limit (1000-2000). Need to keep it concise but comprehensive.
Now, putting it all together step by step, making sure each section flows naturally and SEO keywords like "Compound for Windows", "Windows games", "VR shooting games", etc., are included.
Check for any missing information and ensure all provided data is used. Since pros and cons aren't available, skip those sections or mention that information is unavailable.
Finally, conclude with a strong call to action
