This was a code-only (no graphics required) paying job involving private help developing a website within a team of people.
We would love and really desperately need some help developing, testing and debugging our new site design, and I'm willing to pay someone a modest fee for some personal time to help me with some practical things, because we've been meaning to get some "professionalistic" help for a long time but could never quite get there for a number of reasons, whether it's software licenses or credits and advertising, or all-or-nothing professional webdesign contracts, there have always been issues finally getting it done right.
____
We have mockups to work from already:-
(please test these sites with different browsers, poke it around, laugh at the source, let me know how it can be improved and any feedback so far is very welcome, thank you!!!)
(if the above URL is 404, it means the site is done)
____
This has been made entirely with Wordpad so far and the source you see is how I've written it. Horrible! - but does fundamentally work how we want it already. I'm not a webdesigner, I know some basic HTML from the early days and can "hack" things together (as you can see) using frames, layers and tables. I've spent the last couple of days just trying to get the preformatted text to wrap correctly in both Internet Explorer and Mozilla Firefox, which are the 2 browsers I've been using to test with while I write the HTML.
So first of all, what I did and why, and then what I want to do and need help with...
I began with a focus on resizing and zooming in browsers. Every site I had made before was made under the assumption that everyone on Earth was either using 800x600 or 1024x768, and the highest beyond that was only slightly wider, 1280x768, and box shape sitting right in front of them, a fair assumption too. These days people have 16:10 ratios and 2560x1600 displays that take up nearly a whole wall, I need to make sure the site works "well enough" under both conditions, and that it can be resized in its window and zoomed in and out in a nice way. So far, I think it's a miracle I've actually been able to do it like I have and it already beats anything I've done before based on that.
Far less impressive is the menu system I have in mind and using frames the way I have. I can sense your disgust in me already, but please keep in mind it's that I still don't know any better. I've hacked together this code in such a brutal way to get around problems the best I can, looking at the code you'd probably be somewhere between confused and amused. The big issue I have right now is that one can easily lose the menus by dragging the mouse within them, which is a generally huge issue to have as they would become lost to the user, not visible and require a refresh. The reason I've done it with frames is because ("I think I can" and) want to have like an optional multiple subsystem menu, by allowing links in that frame to target itself and bring new options without making a mess. It will be from 1 to 3 options, which will be "menu option" > "project/site area" > "project details/site area details". So the main menu can target the content area, the submenu, or the submenu could target itself again to allow access to every different part of the site and never need to reload the navigation content.
And now what I want to do next, and need (paid) help with, is the menu system and its issues. I don't like it, but like I said, I simply don't know any better, which is the whole reason I began writing the HTML using frames, for as many issues as it unleashes, it's still the most efficient way I know to do what I want. This would be the first paid involvement. Beyond that, we should probably focus on different scalability and compatibility concerns because I'm sure there's much more I'm not aware of yet, and having preformatted text that is easy to update and wraps nicely around the page is a big concern for me, but then afterwards there's a whole lot of fun and nifty things I'd like to do which should be a lot more enjoyable to work on.
Details about how this would actually work out is a varying hourly payment (~$), privately negotiated, for personal communication time where the issues would be dealt with using IRC and FTP, then along with another software such as Skype. Development must not rely on other unlicensed softwares or libraries, and developer must upload unique files to FTP server with restricted access under a non-exclusive rights contract, which relates to the payment itself. Basically, it's forced to happen legitimately or not at all, so please contact me only if you actually have the artillery to do this. The upside is that we'll have a decent amount of time, no huge rush yet, so this can easily be someone's side-project.
If everything works out nicely enough in all aspects, we may consider going a lot deeper into another big website design that involves more complex code and so bigger contracts and payments, but for now what we're really looking for is both some community help and feedback, in whatever form it may be (feel free to edit our HTML files and post them right back to me!
) and anyone who is interested in some extra income for privately helping me along with having better code, please PM me for more details.
A thousand thankyous for your time!
.
.
.
_____________________________________________________
----------
issues:-
- needs debugging, many incorrect tag functions and values.
- missing graphics, still many text placeholders and temps.
- can click and drag the mouse in the menu frames, losing focus, hiding buttons and losing navigation.
- still can't get the preformatted text to wrap nicely around the tables.
- preformatted text different IE vs Firefox (padding issues).
-
----------
todo.next:-
- have all non-content graphics preload and display first (300KB).
- make sure unique content URLs always load within frames.
- prevent text resizing in all non-content frames.
- functional menu/submenus and multiple content pages.
- galleries and image-viewer.
-
.
.
.
We would love and really desperately need some help developing, testing and debugging our new site design, and I'm willing to pay someone a modest fee for some personal time to help me with some practical things, because we've been meaning to get some "professionalistic" help for a long time but could never quite get there for a number of reasons, whether it's software licenses or credits and advertising, or all-or-nothing professional webdesign contracts, there have always been issues finally getting it done right.
____
We have mockups to work from already:-
(please test these sites with different browsers, poke it around, laugh at the source, let me know how it can be improved and any feedback so far is very welcome, thank you!!!)
(if the above URL is 404, it means the site is done)
____
This has been made entirely with Wordpad so far and the source you see is how I've written it. Horrible! - but does fundamentally work how we want it already. I'm not a webdesigner, I know some basic HTML from the early days and can "hack" things together (as you can see) using frames, layers and tables. I've spent the last couple of days just trying to get the preformatted text to wrap correctly in both Internet Explorer and Mozilla Firefox, which are the 2 browsers I've been using to test with while I write the HTML.
So first of all, what I did and why, and then what I want to do and need help with...
I began with a focus on resizing and zooming in browsers. Every site I had made before was made under the assumption that everyone on Earth was either using 800x600 or 1024x768, and the highest beyond that was only slightly wider, 1280x768, and box shape sitting right in front of them, a fair assumption too. These days people have 16:10 ratios and 2560x1600 displays that take up nearly a whole wall, I need to make sure the site works "well enough" under both conditions, and that it can be resized in its window and zoomed in and out in a nice way. So far, I think it's a miracle I've actually been able to do it like I have and it already beats anything I've done before based on that.
Far less impressive is the menu system I have in mind and using frames the way I have. I can sense your disgust in me already, but please keep in mind it's that I still don't know any better. I've hacked together this code in such a brutal way to get around problems the best I can, looking at the code you'd probably be somewhere between confused and amused. The big issue I have right now is that one can easily lose the menus by dragging the mouse within them, which is a generally huge issue to have as they would become lost to the user, not visible and require a refresh. The reason I've done it with frames is because ("I think I can" and) want to have like an optional multiple subsystem menu, by allowing links in that frame to target itself and bring new options without making a mess. It will be from 1 to 3 options, which will be "menu option" > "project/site area" > "project details/site area details". So the main menu can target the content area, the submenu, or the submenu could target itself again to allow access to every different part of the site and never need to reload the navigation content.
And now what I want to do next, and need (paid) help with, is the menu system and its issues. I don't like it, but like I said, I simply don't know any better, which is the whole reason I began writing the HTML using frames, for as many issues as it unleashes, it's still the most efficient way I know to do what I want. This would be the first paid involvement. Beyond that, we should probably focus on different scalability and compatibility concerns because I'm sure there's much more I'm not aware of yet, and having preformatted text that is easy to update and wraps nicely around the page is a big concern for me, but then afterwards there's a whole lot of fun and nifty things I'd like to do which should be a lot more enjoyable to work on.
Details about how this would actually work out is a varying hourly payment (~$), privately negotiated, for personal communication time where the issues would be dealt with using IRC and FTP, then along with another software such as Skype. Development must not rely on other unlicensed softwares or libraries, and developer must upload unique files to FTP server with restricted access under a non-exclusive rights contract, which relates to the payment itself. Basically, it's forced to happen legitimately or not at all, so please contact me only if you actually have the artillery to do this. The upside is that we'll have a decent amount of time, no huge rush yet, so this can easily be someone's side-project.
If everything works out nicely enough in all aspects, we may consider going a lot deeper into another big website design that involves more complex code and so bigger contracts and payments, but for now what we're really looking for is both some community help and feedback, in whatever form it may be (feel free to edit our HTML files and post them right back to me!
A thousand thankyous for your time!
.
.
.
_____________________________________________________
----------
issues:-
- needs debugging, many incorrect tag functions and values.
- missing graphics, still many text placeholders and temps.
- can click and drag the mouse in the menu frames, losing focus, hiding buttons and losing navigation.
- still can't get the preformatted text to wrap nicely around the tables.
- preformatted text different IE vs Firefox (padding issues).
-
----------
todo.next:-
- have all non-content graphics preload and display first (300KB).
- make sure unique content URLs always load within frames.
- prevent text resizing in all non-content frames.
- functional menu/submenus and multiple content pages.
- galleries and image-viewer.
-
.
.
.
Last edited: