FizixRichard

Thanks for the offer but I'll have to pass.

You mean an advertising agency / web design studio hybrid? Have a look at digital agencies and interactive agencies (same thing btw); they are spawned from the marriage of advertising and web design. They all have their own target audiences; the ones with strong marketing or advertising expertise tend to be geared towards campaign websites (i.e. promotional websites for the latest product), brand destinations and strategy. The ones with stronger technical/interactive backgrounds tend to be geared towards RIA's, interactive applications (things like product configurators, design applications, broadcast/conferencing applications etc). Others strike a middle ground; some literally are full service; but even then they have their strong point and everything is geared in a certain kind of direction. So I'd look at your strengths, what types of clients and offerings you want to target, look at the agencies that are already out there; see where you fit and go from there.

This makes me very sad

1. Don't use MS Word; if you must use a visual editor at least use one that's built for the job (although knowing what you are doing and actually coding it is far better). 2. @suganyabenton... what on earth are you talking about? You sir win todays award for badly pointing out something that is at a superficial level, kind of correct but of the "you don't say!?!?" variety, in the most strange and useless way possible.

While it may not sound nice for the client, what Renaissance-Design said is true. If a client changes their mind half way through a contracted project, it costs you money and to be frank, contracts exist to protect both you and your clients on roughly equal terms. If you mess a client around, you'll hear about it and it should go both ways. Ask yourself this, if you were contracted by a client to complete a 2 month project and then half way through you dropped them a message saying "actually, I can make more money if I drop your job and take on something else", would they deem that as acceptable? The answer is no; at best they would want you to hand over what you produced and settle any balance difference paid beyond what you provided or ask for a refund - or maybe both. At worst they would sue you. It would certainly do damage to your reputation. What they are doing appears to be the role revesal of the above; so personally I don't think its acceptable and should be something you protect yourself against. Have a look at your contract and see if they have breached it; if they have, then talk to them about it. You should have exit clauses in the contract for if a client terminates it because they have simply changed their mind half way through a project. Or alternatively, if you choose to adjust what you are providing them, then make sure you protect yourself properly if they mess you around again. While I wouldn't exactly advocate taking a client for the whole contract value if they terminate, tthere should be some form of renumeration. Due to the nature of your work, it messes schedules up and costs you money if people can just walk away without any consequence. Provided it's reasonable and you aren't taking the p*** yourself, you are well within your rights to contract exit clauses that mean the client has to pay a portion of the total balance off should they change their mind. There has to be some kind of balance. I'd take it as a lesson and learn from it.

Congratulations!

They nuked it for financial gain, sadly while it's clearly not worked as it's empty with the odd job posted once in a blue moon, they haven't reverted it back While it got some junk, it also got some good stuff posted in it. All it needed was a sub forum for collab works for the no/low budget stuff. It was still far better than what we have now though. I suspect it won't return though, it's been brought up a number of times and Ben hasn't done anything with it, so I suspect it's not going to happen. Shame really.

You don't want to avoid it really. Friendly url's without the extension have quite a few benefits; such as users not having to remember the pages extension and allowing you to easily change the way the site works (i.e. through to a cms later) without having to worry to much about how that will affect your websites link structure. You can also use htaccess to redirect people away from old depreciated pages to new ones automatically. HTACCESS is a file (named .htaccess - note that there is no name before the .) that contains rules for how the server will handle requests. You just map the name to x extension (so about will map to about.html or about.php - and later if you get advanced, through an MVC framework - but don't worry about that just yet). There are loads of tutorials on how to create htaccess rules and it really is simple. It's not daunting at all.

As others have said, .php means the script can contain PHP code and thus you can do serverside operations and processing before the HTML/CSS is delivered to the client. I will add though, if you start with .html and want move over to .php learn how to beautify your URL's with HTACCESS (it's easy) so you don't break extensions when you change to PHP. So about.html would be accessed as yourdomain.com/about and it wouldn't matter if the extension was .html or .php or whatever else.

No but why not try adobe creative clouds programs for 1 month as its cheap, or use a trial of any good program if its a one off? Outside if that, google and try a few application out (from trusted sources)

When I played with a prerelease ages ago the metro apps seemed very primitive, obviously it was a fairly early version so it won't be comparable to now. It will be interesting to see how much you can integrate with the OS because you couldn't do much then. There was a lot of talk about OS and inter-app integration; plans for very deep integration. So that's one of the first things ill be investigating.

That doesn't help much, in fact you've confused the issue. Can you take a step back and explain exactly what you are doing, maybe even highlighting who the host site are as that could give a clue. Are you trying to integrate webcam chat from one service to another? Clarity is key.

It's a RESTful API; so you'll need to learn how to code REST API's and use json. ETA you can use PHP or their Javascript SDK. ETA 2: You can find their PHP integration guide here: https://github.com/j...ration-Guide.md Not being funny but that took me 2 minutes from the link you gave, it pays to actually read the site. The reason I say this is because if you don't take the time to read the documentation you're going to make a hash of it and have problems (security, bugs etc.)

What sort of chat, text or broadcast (like webcams)? Whats the chat application for? Is it one on one or multi-user?

To be fair most of what you can do with a Flash gallery (in the normal sense) can be done with HTML5; so unless they are going for something like a rich product configurator or something particularly engaging/awe inspiring (which I doubt very much), I would say no to Flash.