-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Create landing page for servo.org #8365
Comments
I'd like to work on this. |
@nerith thank you! It's probably best to enable github pages on a personal fork of https://github.com/servo/servo.org to test changes, then make a PR once you're happy with the page. |
Staging landing page at http://lucywyman.github.com/servo.org |
Wow! Nice work! |
My prototype of the landing page is at http://nerith.github.io/servo.org |
@lucywyman Has your prototype been tested in Servo? |
@edunham Yeah -- I built the latest release version from github: I'm not certain how much of a problem the OS error is, but it does at least seem to be rendering... Let me know if you need more information! |
@nerith, @lucywyman Thank you both for the site prototypes! We just talked about them in the Servo meeting and the team's consensus is that we love the content completeness and GitHub, blog, and contributing icons of @lucywyman's prototype, yet feel that the visual style of @nerith's is more consistent with Rust's themes and portrays the more serious, researchy (as opposed to playful, start-up-like) tone that we'd prefer going forward. In my opinion, the easiest way to combine the best of both prototypes will be to merge @nerith's PR, then ask @lucywyman to PR against the repo to update the site's content and icons. Does this sound good to both of you? Thank you both again for the speedy, awesome work -- choosing between the two prototype sites has been a surprising and wonderful problem to have. |
Sounds good :) |
@edunham Sounds good. |
Thank you both again for all the hard work! |
https://github.com/servo/servo.org should contain a web page rather than just a redirect. Requirements:
The text was updated successfully, but these errors were encountered: