Portfolio Delivery Requirements
This is a list of the technologies I will use for my portfolio webpage, with an explanation of how they will be used.
XHTML 1.0 Strict
This coding language will be used for displaying the content of the webpage, and will generate links and other interactive content such as navigation on the website. The XHTML code will also be validated, as this is the best practice when creating websites. It will also ensure that my website remains future proof, ensuring that users will be able to view the website in the coming years.
CSS2.1
Cascading Style Sheets version 2.1 will be used to alter the presentation of the website. This information is kept separate from the content, which will make it easier for me to update. This will also be validated to ensure that it is future proof, and will enable browsers to display the website to give a near identical end user experience for the user regardless of which browser they use.
Textpattern is a content management system (CMS) which will allow me to alter the content of my website quickly and easily. I will create a page template of XHTML and CSS which I will copy into the system, before setting up the CMS to allow me to input different content into different areas of the site. I have chosen this system because it will allow me to update my website with new projects, so that a potential employer will be able to see the quality of my latest work.
This plugin for Textpattern will allow me to use the popular ‘lightbox’ application. This will allow me to show pictures of my projects and development work in an interesting way. Using Lightbox will reduce the amount of pages needed to display images, and will also give the user the option of downloading a higher quality image. This should reduce the bandwidth usage of the end user, giving them control of what content they decide to access.
Fire FTP v0.97
I will be using the Fire FTP plugin to upload my web information to the internet. This FTP client is free and simple to use, and works within the Firefox 2.0 browser.
I will have to set up a MySQL database on my web hosting so that I can install the Textpattern software. This will keep all of the data I input into Textpattern organised into a relational database, which the software can then use to display information.
POP 3
I will be using the POP3 email system to allow viewers to contact me. This will be done through Textpattern, which will be able to build a tag which I can insert into my site. It also allows for a newsletter system to be set up, so interested users could be informed of new developments on the portfolio.
3 comments:
You seem to be relying heavily on Textpattern for the technologies needed to build your website.
I commented on Craig A's post earlier about using one software application for developing websites (Dreamweaver) It struck me that there is similarity with your use of TP.
I realise that you have invested your time to learn TP, I am not knocking it all, but would you consider using another CMS in the future?
I have read online, there were suggestions that TP isn't being developed as much as Wordpress.
If you're learning how to create a CMS for the self-managed learning plan, why aren't you implementing your own?
Textpattern is useful for a lot of things, but one of those is not building portfolios to any effective degree (as I've found out).
If you want to go down the route of an existing CMS, then they're far better CMSs out there that are purpose-built for portfolio situations.
@Scott: I've tried Wordpress before and didn't like it, plus I'd like more experience with the Textpattern system.
I'm not sure if your view on using different software is a valid one. I'll just be hand coding into textpattern, and then setting up the articles - common in pretty much all CMS systems of that type. I want to focus on getting a quality site, not the method of creating one.
@Craig: I don't want to be locked into using my own CMS system because a) it might not get finished b) it may not do all I want it to do c) I'm finding it tough to make progress with the PHP stuff d) it may not be secure e) it may be generally useless at everything.
I'm confident that I can make a good job of it with Textpattern. After all, the design is already compromised by it only showing work from college, and will no doubt receive an overhaul after we finish the course anyway.
I'd rather concentrate on the accessibility side, which I have not had much experience with yet, than waste time learning another CMS.
Post a Comment