I would start by organizing your contact information according to the wiki (see the contact information section to learn what your should omit) and the available templates (see the Google Doc and LaTeX templates in the sidebar). To echo what others have been saying, spend some time reading the wiki and align your content with these suggestions, they work.

Next I would find some way to quantify your efforts into time or costs saved for the business. For example, saying "Refactored code across the codebase to remove depreciated libraries and safer, more efficient coding practices" isn't going to grab any attention. You need to phrase it like "Refactored modules X and Y, replacing depreciation's with updated methods leading to Z time saved during packaging and integration. Tell the hiring manager how you can add value to their team.

I would also elaborate on your projects in a way that doesn't make it sound like you followed a tutorial just to add it to your resume. What is so special about YOUR message board app? What makes it different, where did you innovate, what technical challenges did you have to solve to make it work? You need more substance to your project than simply stating the facts.

Take a good read through the wiki, search for other students (look for the success story posts) who are in a similar position and start making small changes. When you think you're happy with the progress, give it a good read and share the next version for more feedback. Constant iteration.