When including projects in your resume try to be as objective as possible - if in doubt whether a project is worth mentioning or not you could simply add links to your Github repos and talk about them on the interview itself.
If those "mini" projects are suitable for the organization you're sending your resume to, then go ahead and add them. Also, if they are not in your main expertise, adding them would show your potential employers you have a broad area of interests.
I'm a backend developer, but I usually add small "front-end" projects like simple CSS animations and stuff. This shows that while I'm a backend expert I also like and am capable of doing frontend tasks.
One last thing - you could also add any certificates in MOOC or any other training, related in any way with the position you're applying for. It would give a hint to what your interests are.
I tend to prepare my resumes specifically for the organization/position I'm applying - I would start with a very brief "cover letter", explaining my motivations and interest in the job, then I'd add links to some of my projects and activities and would finish with skills and expertise. This way I make the HR's job easier and prepare them on what we can talk in a face-to-face meeting.
So in short - keep your resume as short and informative as possible; leave the talking for the interview itself. And always update your resume depending on the position/organization you're applying for.