Is there any reason you chose to use diptrace instead of kicad?
Also, for videos, I found that combinng both videos and written content is extremely difficult and hard to orginize. An alternative would be to make gif's of very short clips to demonstrate something which is hard to do in text, but too short to make an entire video for. I have never personally tried it though, and gif's might be problamatic for things such as phones, not to mention they are somewhat bandwidth intensive. If gif's are done wrong, the filesize will be huge, but if done right, they can be managable.
I originally tried to do a timelapse of the design of a simple board design, all the way from selecting parts, through designing and making a schematic, and to the end of the PCB design. I had a program which took a screenshot of my entire desktop every few seconds and saved it to a folder. Unfrutnetly the program fumbled itself, resulting in corrupted files half way through, and it did not tell you that something was wrong untill you are done and trying to render it! It wasn't fraps, but something else instead, sadely I forgot what it was. But, what I did have was very cool. It really does show what the entire process is, including getting side tracked like going on reddit, listning to pandora, and a game here and there. It was fun to watch, but with only half the content it was not worth it to upload. Keep in mind that you will rack up data on your hdd somewhat quickly, so make sure to have plenty of space beforehand!
For communication, I had a similar dilemma a while ago. How much do you value your time, and how quickly do you want to finsh the project? Are you willing to allow the communication aspect become a project in of its own? Will you use the new communication medium in future projects, and will it be warranted considering the increased cost for the communication module, or if will be usefull to you in the future. What will you use for communication before you get the bluetooth working, and will you have enough energy left to work on communication after getting the basic power supply stuff done. And lastely, do you value the expirence and latter know how of the usage regarding the new communication medium enough to warrant the time and project delays? In the end, I decided against using wireless because I am cheap and don't want to pay four bucks for every blue tooth module. But, it does make yoru projects look infitly more professional and brings a much more "cooooool" factor.
I have dabbled with both PIC's and ARM's, and both have their perks. You should also consider MSP430's! The questions are, do you do most of your projects based on battery power? If so, try out the MSP430's.
How much money are you willing to shell out for the initial investment for the new platform, mostly in terms of programming tools. ARM's can be programmed by buying a bus pirate, using their onboard boot loader via UART, or buying a TI launchpad and using the programmer on the board, so all in all it is extremely cheap to get started with the ARM platform. Also, it is getting extremely popular, the M4's are a beast in terms of preformance, and IDE's are starting to improove for arms. Not to mention that the cheapst arm is about three bucks on digikey in single quantaties, and it has a good bit of RAM and flash. The libraries are starting to mature well also. Arm's have a full blown free very mature compiler, so that is good.
PIC's are an intersting creature. It was my second MCU, if you can consider the basic stamp an MCU. You need either a PICkit2 or PICKIT3 to program PIC's. I reccomend a pickit3 so you can program PIC32's. The programmer is a somewhat expensive, but it includes some cool stuff like a low speed logic analyizer and bus interface. PIC's also come in DIP packages and are very cheap for the low pin count packages, such as DIP8. They use some sort of "opensource" compiler thing which I am fuzzy about. It is some sort of GCC thing with Microchips stuff integrated in it, and if you don't pay you dont have access to optimizations. I do not thing there is a fully free compiler for PIC32's, but I might be wrong. Microchip is also very popular, and has some cool libraries.
MSP430's have the launchpad, which has its own programmer on the board, and costs only twelve bucks or so. It is VERY beginner friendly. They have a fantastic community on 430h, and they have some dude that made a full tool chain setup thing. All you do is download eclipse, and via maybe four clicks install a plugin, and bam, you are ready to start coding and flashing. It is also continously updated, but it is lacking some features, such as seeing variable values when debugging under certain conditions, but otherwise you can easily start using it. It is the least popular of the two though, and has less full blown libraries, but I have never had a problem because of it. C is C, the libraries do not change that much between microcontrollers, you just need to muck around with the lower level components a bit to get it working on your platform.
For ultimate power stuff, you should check out the gecko line, they have some super awesome power consumption tools while debugging.
Damn, my professor got back, so I have to end it here. Good luck! :)
Edit: Holy batman, this is long, sorry! Though, this might be a front page worth small look on microcontrollers. :D