A GitHub Pages blog (Jekyll) documenting #AI4Good — building AI-for-good apps (education, health, culture, heritage) one day at a time, with hands-on guides for Azure, AI, 3D, and mobile.
- Flagship — #AI4Good build story:
_posts/2026-07-10-ai4good-an-app-a-day.md— six AI-for-good apps shipped in eighteen days (KidKat, NeoFit, Sopāna, Chaturanga, ActionCut, GpsCamera), chronological, with live links + screenshots. Cross-posted to DEV. - Image → 3D:
_posts/2026-07-10-image-to-3d-huggingface-blender-copilot.md— carving a glowing 3D chess army from single images with a free Hugging Face Space (tencent/Hunyuan3D-2) + headless Blender, driven by Copilot CLI autopilot. - Azure AI Foundry:
_posts/2026-06-29-onboarding-oss-models-azure-ai-foundry.md— onboarding open-source models into Azure AI Foundry.
bundle install
bundle exec jekyll serve # http://127.0.0.1:4000/AI4Good- Repo
naveenneog/AI4Good, pushmain. - Settings → Pages → Source: Deploy from branch →
main/ root. - Site:
https://naveenneog.github.io/AI4Good.
Markdown files in articles/ are auto-synced to DEV on every push to main
via .github/workflows/publish.yml (uses sinedied/publish-devto).
One-time setup — add your DEV API key as a secret:
- Generate a key at DEV → Settings → Extensions → DEV Community API Keys.
- In this repo: Settings → Secrets and variables → Actions → New repository secret.
- Name it
DEVTOMASTERKEY, paste the key, save.
You can run the sync manually anytime from Actions → Publish to DEV → Run workflow (the workflow also has a workflow_dispatch trigger), or just push a change under articles/.
Each article's front matter carries published: false (creates a draft on DEV to review first); flip to
true to go live. Images use absolute raw.githubusercontent.com URLs so they render on DEV, and canonical_url
points back to the GitHub Pages post for SEO. The action stores each post's DEV id back into the file's front
matter on first run to keep future pushes in sync.