Frontmatter
| title | Update blog.json |
| author | adhirajpawar |
| state | Closed |
| createdAt | Oct 3, 2024, 8:14 PM |
| updatedAt | Feb 1, 2025, 6:30 PM |
| closedAt | Feb 1, 2025, 6:30 PM |
| mergedAt | |
| branches | dev ← patch-2 |
| url | https://github.com/neomjs/neo/pull/6015 |

hi @tobiu I’ve completed the steps outlined in issue #6012 and have added the blog post along with the required metadata. As this is my first contribution and I'm still learning the process, I hope everything is correct.
If I’ve made any mistakes or missed something, please do let me know—I’m eager to learn and fix anything that needs attention.
Thanks a lot for your patience and guidance throughout this contribution!

word of advice: it is crucial to review your result visually before creating the PR.
take a look at: https://github.com/neomjs/neo/issues/6012 i added the "How to add a new blog post into the Neo Website (Portal App)?" and "How to test the blog preview locally?" parts for a reason.
otherwise we can get results like this:
while we could create a feature request ticket for the blog list to also support external URL based images, it would still look not nice:
so i strongly recommend to search for a better cover image (e.g. browsing through the online examples and taking a screenshot).
regarding the json properties for a blog item:
id 59, 60, 61, 6014 makes little sense => i would go for 62 :)
publisher as far as i know only the provider Medium supports it. when writing a blog post there, you can add it to a publisher like ITNEXT, Level Up Coding, JavaScript in Plain English and many many others (empty string in your case)
selectedInto is also an obsolete property for Medium blog posts => around 2 years ago, the team did promote high quality blog posts into specific categories to generate more traffic. sadly, they removed the feature, so now authors only get a "blog post got boosted" notification. empty array for other providers.
Please make sure to read the Contributing Guidelines:
https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch, not themainbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: