Feature/blog standards compliance #1147
Conversation
- Added Kingsumo embed script below the leaderboard section - Script loads from https://kingsumo.com/js/embed.js - Addresses issue recodehive#758 for giveaway page integration
- Add comprehensive blog standards document (wiki/blog-standards.md) - Update contributing guidelines with blog writing section - Standardize existing blog posts to match new standards: * Fix frontmatter consistency across all blogs * Remove invalid commented meta tags * Improve SEO descriptions and formatting * Ensure proper date formats and required fields Closes recodehive#567 - Blog structure standardization
|
@Gupta-02 is attempting to deploy a commit to the recode Team on Vercel. A member of the Team first needs to authorize it. |
|
Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs. In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊 Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv. We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰 🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨ 📚Your perks for contribution to this community 👇🏻
If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊 |
|
✅ Synchronized metadata from Issue #567:
|
|
could you provide ss for the changes made to the podcast page. @Gupta-02 |
|
Also @Gupta-02 the cause for this issue is to Make a standard to the structure. like github blog and google blog as sample . i think this changes are good but doesnt align with the main goal |
|
Hi @Gupta-02 this is misaligned with our requirment, lets stick to issue spesfic changes. |
3 participants
This PR implements comprehensive blog writing standards for the Recode website to ensure consistency, quality, and SEO optimization across all blog content. The changes standardize frontmatter, content structure, and writing guidelines while updating existing blog posts to comply with the new standards.
Fixes #567
Type of Change
New feature (e.g., new page, component, or functionality)
Bug fix (non-breaking change that fixes an issue)
UI/UX improvement (design, layout, or styling updates)
Performance optimization (e.g., code splitting, caching)
Documentation update (README, contribution guidelines, etc.)
Other (please specify):
Changes Made
Created blog-standards.md with comprehensive blog writing guidelines including frontmatter standards, content structure, SEO best practices, and quality checklists
Updated CONTRIBUTING.md to include a blog writing section with reference to the new standards document
Standardized frontmatter and content structure across 6 existing blog posts:
index.md
index.md
index.md
index.md
index.md
index.md
Ensured consistent meta tags, author information, and content organization
Dependencies
No new dependencies or tools required
All changes are backward compatible with existing Docusaurus setup
Checklist
My code follows the style guidelines of this project.
I have tested my changes across major browsers and devices
My changes do not generate new console warnings or errors .
I ran npm run build and attached screenshot(s) in this PR.
This is already assigned Issue to me, not an unassigned issue.
Grok Code Fast 1 • 0x