Hey, Mark1, as Niavmai said, there shouldn't be a "modpack" folder in "bin", just the "modpack.jar" directly. You can make it by just renaming the Forge zip like you did. No need to place the class files from all the mods in that one, though. Just place all your mods directly in the "mods" folder. A few mods, like "NotEnoughItems", have to go into "coremods". (There are a tiny few mods that do require you to place stuff in the "modpack.jar". Like Optifine, I think.)
To begin with, I don't think you actually need to include any config files unless you want to include an edited version of them. So if you haven't modified any config files, just leave that folder empty for now. (If you need to get a clean config file for a mod, one way to get at them is to install the mod, run Minecraft and then check the config folder. There should now be a config file for your newly installed mod.) One common reason you might want to include these is when you've edited them to resolve block-ID issues.
If you want to see the folder/file structure for yourself, just check out the folder for any modpack you've already installed via the Launcher. Besides all the stuff that gets downloaded and unpacked, it'll have the four folders you mentioned with all the files as they need to be.
Hope that helps.