Draft blog comeback and catch-up posts#6
Merged
amir-arad merged 6 commits intoApr 9, 2026
Conversation
Created 11 blog post drafts covering 2.5 years of development: - We're Back! - Opening post acknowledging the gap and setting expectations - Post 1: Letting Go of 3D - The decision to remove 3D rendering for focus - Post 2: Engineering Complete - Energy, heat, and system effectiveness - Post 3: Missiles & Explosions - Completing the engagement circles - Post 4: Armor Reborn - Sectional armor implementation - Post 5: Bots & AI - From spiral bug to tactical AI framework - Post 6: Navigation - Warp drives, waypoints, and docking - Post 7: Combat Refinements - Targeting, physics, and polish - Post 8: Developer Experience - Documentation and testing revolution - Post 9: The Rewrite - Why we rebuilt the foundation - Post 10: State of Starwards 2025 - Roadmap and community invitation All drafts follow the Starwards voice: conversational, honest, transparent, process-focused. Each post references relevant past blog posts and GitHub PRs, explains technical decisions with rationale, and emphasizes LARP value. These drafts are ready for review, editing, and scheduling for publication over the next 3-5 months (one post every 1-2 weeks).
Updated based on feedback: Voice improvements: - Removed AI social media content patterns (dramatic one-liners, artificial tension) - Made pacing more straightforward and matter-of-fact - Eliminated choppy dramatic beats and marketing speak - Added critical section to WRITING_STYLE_ANALYSIS.md documenting what to avoid Factual corrections: - Removed false "March 2024 rewrite" narrative (it was focus shift, not rewrite) - Added Unity POC context to 3D removal explanation - Clarified that 3D will return as separate Unity client - Fixed "we're back" post to be more honest about what actually happened Still needs work: - Post 9 (The Rewrite) needs major revision or deletion - Technical posts need voice adjustments - Need answers to BLOG_QUESTIONS.md for next iteration
Replace the 10-post topic-based series (which had factual errors and wrong tone) with 2 posts based on actual git history and interview: - were-back.md: chronological recap 2022-2025 - state-of-starwards-2026.md: current status and what's missing Key corrections: most systems built in 2022 (not 2024), March 2024 was a refocus not a rewrite, added life context (war, immigration). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Updated the draft to reflect changes in the project's timeline and development progress over the years, including challenges faced and future plans.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please note that if you are trying to update your website, this is the wrong place to do so. Please carefully follow the Beautiful Jekyll instructions (found at https://github.com/daattali/beautiful-jekyll#readme) and make sure you submit changes to your version of the project.
If your intention is to submit a Pull Request, please describe what your pull request achieves.
Thank you!