-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standard Employer Pitch Document #8
Comments
+1 |
1 similar comment
+1 |
+0.8 |
+3.14159265359 |
Happy to do this, perhaps somebody could get a draft started in the campjs wiki and I'll move it onto the site later |
i.e. writing copy is very slow and any help would be very appreciated. |
Yep, I'll have a look at this at some point today, if someone doesn't get to it first. |
Thanks @chrisdewar 😗 |
I did some brief research and thinking on what it should contain: Needs to include the basics of location, date, and cost (including approx travel and hotel, if needed, from different capitals around Australia), and can summarize what you'll learn. It would be useful to explain exactly what we can get out of CampJS and how it's content benefits your employers and/or team. What is it's unique value proposition. |
@Kevdesign great ideas |
I seem to remember JSConf.au having a good one of these; I don't suppose anyone knows where it might be located? |
@chrisdewar get a chance to draft this? |
I couldnt find one from JSConf but the one from WebDirections is here http://www.webdirections.org/downloads/wds13-why-send-the-team.pdf |
TBH I haven't had a lot of time to spend on this, but I have made a start on it. I will add it to the wiki now. update: https://github.com/campJS/campjs/wiki/Employer-Pitch-Document |
We should have some form of standard employer pitch document. Something simple that we can give to employers to convey the importance of this event, and the expected advantages and outcomes it will have for their dev staff.
My initial thoughts are that it should be a simple markdown file in a github repo, that we can then > html > pdf when required.
The text was updated successfully, but these errors were encountered: