-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Add Annual Survey Web Report #1654
Comments
@gtewallace if there's a standalone HTML version of the report, it hopefully shouldn't be too difficult PR it into this repository and get it published on the site. @fhemberger @mhdawson @MylesBorins do y'all think we could help @gtewallace with this? |
thanks @bnb It's self contained - I have already tested publishing it as a GHP - we had it up in a matter of minutes in a test repo. That gives me confidence it should be relatively straightforward. @fhemberger @mhdawson @MylesBorins I look forward to your thoughts. Greg |
+1 from me. @fhemberger any concerns? |
No, we could add all the html under @gtewallace Are you fine with submitting a Pull Request? Otherwise just send me a mail with the zipped report files, and I'll add it to the website. |
great news! thanks all! @fhemberger Just to confirm, the path will be: https://nodejs.org/en/user-survey-report Is that right? If so, my colleague @alexcontini will update the HTML file with the new path and I will open a PR with all the assets. Thanks again! Greg |
We might need to adjust the HTML a bit to fit into the website design properly, but we can help you with that once you've submitted the PR. |
@fhemberger awesome - that would be great. Can we keep the page private or unpublished until May 31? @alexcontini - can you please go ahead and update the links in the tweet buttons with this path: https://nodejs.org/en/user-survey-report Then I'll open the PR. Thanks! Greg |
@gtewallace What's in the GitHub repo is public. But if @alexcontini prepares everything locally and submits the PR on 31st, we're good. |
@fhemberger would it make sense to add the year to the path? ie something like /user-survey-report-2018, with possibly the link /user-survey-report pointing to the latest version. I expect that we'll be adding one each year going forward. |
@mhdawson this is what we did for Node by Numbers at NodeSource, and it does indeed seem to be the best path. |
correction: We did routing on sub-paths. So /node-by-numbers and /node-by-numbers/2016 |
@fhemberger Hi! On second thought, is it ok if I give you a zip with all the web report assets? LMK if that's OK and what's the best way. Thanks!! |
@gtewallace I'll have a look at it and get back to you. |
Sounds good, thanks!
…On Tue, May 29, 2018, 3:13 PM Frederic Hemberger ***@***.***> wrote:
@gtewallace <https://github.com/gtewallace> I'll have a look at it and
get back to you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1654 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALmLTBwYF1Itdn5BwkO7lzYsfxvpopuxks5t3Z3igaJpZM4T-CmB>
.
|
This site comes with its own HTML and assets and doesn't depend on any of the regular website's resources. It's not supposed to be translated. It is added to a website subdirectory for ease of deployment, we might consider to move it to a separate subdomain and repository next year, when the next report comes out. Fixes: #1654 Review: @gtewallace, @alexcontini
This site comes with its own HTML and assets and doesn't depend on any of the regular website's resources. It's not supposed to be translated. It is added to a website subdirectory for ease of deployment, we might consider to move it to a separate subdomain and repository next year, when the next report comes out. Fixes: #1654 Review: @gtewallace, @alexcontini
Hi everyone!! Is it possible to get the GA code added to the survey page/pages? thanks again! Greg |
@gtewallace Sure: #1688 |
Hi all,
The Node Foundation has created an HTML version of the Annual Node.js User Survey report and we'd like to host it here.
We think it makes sense since we will also make the data (PII removed) available for download for others in the community to perform their own analysis. We also have some nice executive summary powerpoint slides we can place here for others to use.
There's one aspect of the report that needs to be updated - we have a click to tweet button under every chart and we'd need to update the URL path in the tweets to match the eventual path of the report here on github.
Our goal is to have the report go live on May 31.
I look forward to everyone's thoughts.
Thanks!
The text was updated successfully, but these errors were encountered: