Beyond code, Himanshu has a genuine interest in clear, well-structured writing for technical audiences. He has written SEO-optimized content for ToolJet’s platform blog, maintains a personal blog to share what he learns along the way, and enjoys creating documentation that makes complex tools more approachable for developers.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/himanshubalani/himanshubalani.github.io/llms.txt
Use this file to discover all available pages before exploring further.
ToolJet Writing Portfolio
During his Content Writing internship at ToolJet (Oct 2024 – Jan 2025), Himanshu authored 10+ in-depth blog posts covering ToolJet’s platform features — from UI components and integrations to real-world use cases. Skills used: Google Docs, Markdown, Research, SEO, Content Writing, User ExperienceView ToolJet Writing Portfolio
Browse the full collection of ToolJet articles on Notion — including published posts and writing samples.
Personal Blog
Himanshu maintains a personal blog where he shares learnings, project reflections, and developer insights as he builds.Personal Blog
Visit Himanshu’s personal blog at blog.himanshubalani.com for posts on development, tools, and ongoing projects.
Also on Hashnode
Find Himanshu’s writing on Hashnode, covering developer experiences, fellowships, and technical topics.
Notable Post
My Experience with Keploy API Fellowship
A first-hand account of Himanshu’s participation in the Keploy API Fellowship — covering key learnings, challenges, and takeaways.
Writing Approach
Himanshu’s technical writing is guided by a few core principles:- Research-first — deep-diving into the product or topic before writing a single word
- SEO-optimized — structuring content to surface for the right developer queries
- Developer-audience focus — writing for people who read critically and want precision, not fluff
- Hands-on with the tools — actually using what’s being documented to ensure accuracy
- Clear and jargon-aware — plain language where possible, precise terminology where necessary
Interested in collaborating on technical content? Reach out via the /socials page.