I'm sorry to be so blunt, but what you have described so far (in your original answer and your comment) sounds dreadful. I can tell you right now that if I was hiring, I would only glance at the site... A quick perusal if you will. However, you could be certain that I will not be reviewing UML diagrams and other project-artifacts.
As a hire'er (word?) I will, hopefully, be looking at several candidates. As such, I want to see what they are doing that might be interesting or what may make them qualified. And, more importantly, I want to be able to do it efficiently (not much digging). What you are describing sounds like a repository of your work. And it sounds like it might be overwhelming and not immediately obvious.
What I would be more interested to see is the nature of the projects that you've worked on and generally what you've been doing. For example, if you have a GitHub account (or similar) then I would probably browse around your repos for maybe 10 to 15 minutes (at most). From this I should be able to see what you are working on (the subject of the projects), how frequently you contribute code, and what languages you are working in.
If I like what I see, then I'll invite you in for an in-person interview. It's here that I will ask you to explain some of your projects in depth. I want to hear the explanations from you. I don't want to read UML diagrams that you created. I want you to articulate to me, on the fly, what the challenges were in your project and why your project is exciting and/or important and what makes it special. I want to know what you learned from the project and what other projects you may be working on at the moment.
So... I should just have a GitHub profile and that's it??
YES! I mean... No. You should definitely have a GitHub profile and you should put all of your fun projects on there (that you don't mind sharing with the world), but you may want to have more than just a GitHub profile. Additionally, I'd recommend writing a technical blog. Write about what you find interesting or something new that you've learned or have been struggling with.
From this, a hire'er will be able to quickly gauge what interests you and they can pick and choose a couple of articles to skim to see how much you may know on a particular topic.
Think of ways to concisely show off your skills to possible hire'ers (avoid showing UML diagrams at all costs). As a hire'er, it is their job to find qualified applications, but as the hire'ee it is your job to make your self efficiently discoverable. I'd highly recommend a GitHub profile (in which you're actively contributing) and a technical blog (of which I do myself).
Also, I additionally agree with @Akira71 in that you should keep and up-to-date LinkedIn profile with references, and your job history and what not. And remember to always keep networking, you may land your dream job through someone you met at a conference or code with online.
Warning: If you do go the route of the blog, note that it is a big commitment and an outdated blog may not be the best thing to show off.