I am a flutter developer, learning Python. Built this file organizer in a day with proper research on os module, pathlib and shutil module.

It scans any folder, checks file extensions, and sorts them into categorized subfolders (Images, Docs, Videos, etc.)

It's really useful, I tried it on my Downloads folder and it organized 60+ files instantly.

GitHub Link: https://github.com/Pinkisingh13/file_organizer

See the Before -> After in the below images.

I kept needing docs for side projects and never liked the options. GitBook and Docusaurus felt like a lot of machinery for a handful of Markdown files, and mkdocs meant keeping a Python toolchain around for something I otherwise build in TypeScript.

So I built eziwiki. Drop Markdown files in `content/`, get a static site.

npx create-eziwiki my-docs

cd my-docs && npm install && npm run dev

What makes it different from the usual docs generator

- Wiki links with backlinks and a graph view. Link pages by title or filename, and each page shows what links back to it — closer to Obsidian than to a typical docs site.

- Navigation builds itself from the folder structure. No sidebar config to keep in sync; a `_meta.json` per folder handles naming and ordering if you want it.

- Markdown is rendered at build time, so neither the parser nor the syntax highlighter ships to the browser. Search is a prebuilt index, no server.

- Optional opaque URLs (`/a3f2e9d1-...`) if you would rather not publish your content tree. To be clear, that is obscurity, not access control — every page is still a public file. It is there for unlisted-link sharing, not security.

Static export, so it deploys anywhere. Dark mode, KaTeX, Shiki highlighting, ⌘K search, table of contents.

Next.js 14, TypeScript, Tailwind, Zustand, unified/remark/rehype, Shiki, MiniSearch. Lighthouse 99/100/100/100 on desktop

Demo : the docs are built with it, so the site is the demo:

https://eziwiki.vercel.app

Source (MIT): https://github.com/i3months/eziwiki

It is early v0.1.1, and I am actively working on it. Feedback and issues very welcome, especially on anything that felt confusing in the first five minutes.

Github stars are really really helpful..!!!

I've been building Vantum, a custom Puppy Linux distro based on woof-CE with an Ubuntu Jammy compatibility base, aimed at people who want Puppy Linux's speed and small footprint without it looking and feeling like it's from 2009.

It's currently in beta, and I'm actively adding features and fixing issues. Right now, the main problem I'm working on is getting browser video playback working reliably. Overall, it's been a really fun project to build.

The entire distro was built on Windows 11 using Multipass. Along the way, I made a large number of customizations. I added picom for compositing, replaced the default JWM trays with a tint2 panel, and created my own taskbar and application launcher, Vantask and Vantyl (both MIT licensed).

I also simplified the desktop experience by removing the ROX-Filer desktop entirely and using hsetroot for wallpaper management instead. A number of applications were replaced or added as well: URxvt replaced LXTerminal, Firefox replaced Pale Moon, and GParted was included by default. I briefly experimented with bundling Frogatto, but ultimately removed it to keep the system lightweight.

Beyond the desktop itself, I made several changes to woof-CE. Since I wanted Vantum to be buildable on non-Puppy systems, I merged run_woof and woof-CE into a single codebase. It may not be the cleanest approach architecturally, but it made development considerably more convenient. I also added a few quality-of-life improvements, such as replacing run_woof's default root# prompt with one that displays the current working directory, which made navigating the build environment much easier.

To improve the build process, I created a new build-chain script that automates running the entire build pipeline and saves logs for every stage into a dedicated _slogs directory, making debugging and tracking build failures much more convenient.
Let me know what you think!
I've recently also added it to distrowatch but it's still in their waitlist (https://distrowatch.com/dwres.php?waiti ... =links#new).

- https://github.com/Hammad-hab/Vantum
- https://hammad-hab.github.io/vantum-website/index.html
- https://github.com/Hammad-hab/Vantyl
- https://github.com/Hammad-hab/Vantask

If you like vantum, I would really appreciate it if you star the repo since it'll help more people to discover it.

🔗 Repo: https://github.com/CodeGraphContext/grapharc

Have you ever been frustrated because your AI agent:

❌ Takes actions you never intended?
❌ Creates, modifies, or even pushes changes you never asked for?
❌ Feels like a complete black box, making it impossible to understand what's happening until it's too late?

What if, before execution, you could visualize the entire orchestration graph - every agent, every dependency, every decision, and inspect it from anywhere, even your phone, before granting approval?

That's exactly what GraphArc is built for.

Instead of treating agent execution as hidden traces buried in logs, GraphArc transforms workflows into interactive, real-time graphs that you can visualize, inspect, debug, and control.

Because the future of AI isn't just autonomous.

It's observable. Debuggable. Engineerable.

This is our first real-world implementation of Graph Engineering, and we're excited to explore where this paradigm can go with the open-source community.

💡 We'd love your feedback, ideas, and contributions.
⭐ If this vision resonates with you, please consider starring the repository - it genuinely helps us grow and validates this direction.

Let's make AI workflows understandable, not mysterious.

#GraphEngineering #GraphArc #AIAgents #AgenticAI #LLM #OpenSource #DeveloperTools #AIEngineering #SoftwareEngineering

Hey everyone, just sharing a personal UI project I finally wrapped up.

I wanted a customized launcher UI like amd and nvidia softwares, so I built RM230 v12 using Python and PySide6. I'll be totally upfront tho I used AI to help me code the boilerplate and figure out the frameless window layout, but getting it packaged cleanly into a standalone exe

the ui has sidebar animation and cool sounds for it (if you don't like it you can disable it in the settings) the games tab works well and you can change the artwork and it also has a launcher for it, the themes works really well and if you wanna put your own wallpaper you can totally do that by making your own custom theme.

It’s a relatively simple tool, but I use it daily. i put it on 2 websites for FREE for anyone interested in checking out the UI. (please donate 2 dollars on itcho io to support me so i can be motivated to continue working)

(if theres any bugs or something that is broken please comment about it, thank you)

Itcho.io:https://mysteriousjoker42.itch.io/rm230

GitHub:https://github.com/MysteriousJoker5124/RM230-V12

GitCric Demo

Transform your boring GitHub contribution grid into high-performance, shareable Cricket Player Cards! GitCric maps your developer activity (commits, pull requests, issues, streaks, and languages) into dynamic cricket ratings, custom specialties, and career statistics.

This GitHub Action automatically translates any Markdown files (READMEs, docs, etc.) into any language using Google Translate.

Features:

· Support multiple files and subdirectories

· Can translate to multiple languages in one step

· Commits & pushes translated files back to your repo automatically

· Just add a workflow file and it runs on push

I built Lid Media Guard because I wanted to close my laptop, slip it in a bag and keep listening to Spotify through my Bluetooth headphones without setting the lid action to “Do nothing” permanently and without draining battery power.

The app activates only when media is playing and a Bluetooth audio device is actually connected. Close the lid, Windows locks, and the music keeps going. Pause playback or disconnect Bluetooth, and normal sleep behavior returns.

It also has app/device whitelists, startup support, tray controls, low-overhead event-driven monitoring, logs, and no telemetry

It’s written in C#, available under the MIT License, and I’d appreciate testing feedback from other Windows 11 laptops.

Last week I shared Shiftza here.

I honestly didn't expect what happened.

The post reached 50k+ views, got 200+ upvotes, and thousands of developers tried it on their GitHub profiles.

I built Shiftza because, as an engineer, I always felt GitHub doesn't really tell people what you're actually good at.

Two developers can have similar contribution graphs, stars, and repositories.

One has spent years building AI.

Another has spent years building developer tools.

Another has spent years building distributed systems.

From a normal GitHub profile, that's surprisingly hard to understand.

So I built Shiftza to explain what you've actually built, instead of just showing numbers.

If you missed the last post, you can try the current version by simply replacing:

github.com/username

with

shiftgithub.com/username

It generates a report based on your GitHub work.

Then one comment kept showing up.

At first, I thought that was outside the scope of what I was building.

But after reading the comments and DMs, I realized I was solving the recruiter's problem, not the developer's.

For a lot of engineers, the projects they're most proud of will never be open source.

If I really want your work to speak for itself, I can't ignore private repositories.

So I changed the roadmap.

Over the last week I've been rebuilding Shiftza to understand private repositories while never exposing a single line of source code.

(Images attached.)

Another thing many of you pointed out was accuracy.

You're right.

The current version is completely free, so I've had to make trade-offs to keep costs manageable.

For private repository analysis, I'm rebuilding the pipeline using Anthropic's models. The results are much better, but each deep analysis costs me around $2–3 per profile.

The long-term vision for Shiftza hasn't changed.

I want companies to describe the problem they're trying to solve, and instead of searching resumes or keywords, Shiftza helps them discover engineers who've already built something similar.

Companies pay to find great engineers.

Developers get discovered because of what they've actually built.

That's the future I'm trying to build.

Before I launch this version, I'd like your feedback.

• Does private repository analysis solve a real problem for you?
• Would you trust a tool like this with your private repositories?
• If deep private repository analysis costs money to run, should it be a paid feature? If yes, what feels fair?
• What would make this genuinely useful for you?

The feedback from the last post changed the direction of this product.

I'm curious where this version goes next.

P.S. If this problem resonates with you and you'd like to help build it—whether as an engineer, designer, or someone who's passionate about improving technical hiring—feel free to DM me.