Must be limited to containing at least 10 main pieces that will be accessible to the general public
This will allow the website not to become cluttered which will hopefully allow the work to be more easily accessed. Limiting it to a maximum of 10 pieces of work also make me only choose the best of my work where as I otherwise may be tempted to put on something that I would not this way.
Weather the portfolio should be a design task itself or if it should be something subtle and let the work speak for itself. Making the portfolio in CSS is a way of still making the portfolio a piece of work even if the design is plain because it shows a different skill that you are capable of.
A simple yet very effective goal, it will show that the coding is correct and it is an crucially important, especially when the large proportion of the target audience is potential employers.
Meeting this priority is something that I think the majority of web designers should be taking as a given, but many are not doing so. Simply making the website accessible to a wider range of people is what every designer wants, so why they are not doing it is beyond me. If I’m honest this is something that I have only recently become familiar with, but I will now start to try and implement it into my working methods.
13 comments:
I think you need to change goals 2 and 3. Using CSS and validation is pretty much a pre requisit now.
@4 - I think this is a good choice. I have seen many of our peers choose this goal including myself
I think if you're going to go with goal 3, you need to specify exactly what you want it to validate against.
At the moment, it doesn't specify any standard to measure your validation against, which makes your goal impossible to prove or disprove.
Marc to be fair i think that the CSS one should stay as it is. i dont know about you but im still not too confident using CSS, and if i manage to complete the portfolio using CSS that i would see that as a great achivement...
As far as the validation is concerned, strict 1.0 is probbably the way to go....
When you say you're limiting your portfolio to 10 pieces, would this be 10 pieces per category (eg Web, Print, Misc) or 10 pieces for the whole website?
Well, 10 pieces as a whole i think would be enough... and these 10 would only be the best stuff. This would keep it simple and would not confuse anyone....
You need to specifically say which CSS level you will validate to. Validating CSS is pretty straight forward, at least in comparison to XHTML.
Do you mean you need to validate your XHTML code in your 3rd goal? You'll need to clarify, so that you can measure it.
You really need to nail the whole CSS issue you're having - you won't get a decent job without it. The only way you will gain confidence with using it is through having more exposure to it.
I think most of your goals have been covered and I had the same issues raised with mine as I haven't specified my intentions in some cases. What I would say is that stating a specific number of pieces to display might not be a great choice for a goal as you might regret it later. I think you might benefit from changing this to a goal relating to production and not content.
Just to clarify i want it to validate using XHTML 1.0 Strict and CSS 2.1.
You've still not specified what you want to validate it against. You've said what to validate it to, but not the framework you will use to validate it.
You need to specify that or your goal is impossible to achieve.
Right lets get this straight.....
W3C Validation XHTML 1.0 Strict. and
W3C CSS Validation Version 2.1.
Yes... but what are you going to use to validate it? You need to specify the guidelines you will validate it against.
I will validate the XHTML using the W3C validator.
Do you not need to update your journal to reflect this newly refined goal?
Post a Comment