This repository was archived by the owner on Jul 6, 2026. It is now read-only.
Add UK VAT blog post - #2747
Merged
Merged
Add UK VAT blog post#2747
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a comprehensive blog post about PolicyEngine's new UK VAT analysis tool. The post analyzes how different VAT registration thresholds affect government revenues and the number of VAT-paying firms, including validation against HMRC projections and interactive analysis capabilities.
- Adds a detailed blog post covering VAT threshold analysis methodology and results
- Includes extensive data visualizations comparing different threshold scenarios
- Updates the changelog to reflect the addition of new content
Reviewed Changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/posts/posts.json | Adds metadata entry for the new VAT blog post |
| src/posts/articles/uk-vat-firm.md | Contains the full blog post with analysis, methodology, and interactive visualizations |
| changelog_entry.yaml | Updates changelog to document the blog post addition |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
MaxGhenis
suggested changes
Sep 8, 2025
github-project-automation
Bot
moved this from Todo
to PR: Review Requested
in policyengine-app
- Use active voice throughout with UK as subject - Remove redundant explanations and duplicate table - Eliminate unsupported adjectives/adverbs - Tighten prose and reduce wordiness - Clarify data construction attribution - Improve title and subtitle for UK audience - Add forward-looking conclusion without overcommitting 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Document systematic improvements made to UK VAT thresholds article: - Active voice and conciseness guidelines - Data attribution and claims standards - Structure and flow best practices - Technical writing conventions - Conclusion and title guidelines These standards will help maintain consistent quality across all PolicyEngine articles and can be used to create automated review subagents. 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
MaxGhenis
approved these changes
Sep 10, 2025
MaxGhenis
left a comment
MaxGhenis
left a comment
Contributor
There was a problem hiding this comment.
All CI checks pass. Article improvements and documentation standards look good.
github-project-automation
Bot
moved this from PR: Review Requested
to Done
in policyengine-app
This branch was successfully deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #2748