Added blog post link to the official blog section

[adhirajpawar]

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)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch, not the main branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[tobiu]

hi @adhirajpawar,

thanks for writing the blog post!

a couple of steps remain:

1. Blog Post: An Introduction to Neo.mjs: Revolutionizing JavaScript Frameworks #6014 => add a comment, then i can assign the ticket to you
2. normally you would reference the ticket id inside commits (not an issue for first time contributors)
3. i added a new description on how to add blog posts to the neo website here: Write a Blog Post about Neo.mjs #6012
4. please follow the steps below the h2 headline (a dummy file with a comment won't work)

best regards,
tobias

[tobiu]

outdated duplicate of #6015. closing this one.