landing for source{d}
License: MIT License
This repository contains the sources of the source{d} Landing and its API.
This site is deployed in production and in staging following our web application deployment workflow
Please take a look at CONTRIBUTING file to see how to contribute in this project, get more information about the landing architecture and how to launch it for development purposes.
All activities under source{d} projects are governed by the source{d} code of conduct.
Copyright (c) 2018 source{d}, see LICENSE
So that it can answer to /<prefix>/repositories if needed instead of rewriting the url path
The top navigation bar looks fine in the original state…
…but when we scroll down the page, many sorts of problems arise:
It is clearly unbalanced the spacing we have above (more) and below it the navigation bar items/logo (less). Looks very odd and I see no reason to be like this. Playing with the height numbers of the navbar content layer (60px -> 45px) and the background layer (75px -> 60px), it seems much more balanced.
One more thing is that the menu items font size seems a bit smaller than almost everything else in the page. 18px is the content description inside the cards—everything else is either 20px, or above. Eyeballing, 20px seems to fix the problem.
Last thing, when you scroll down you get a flat background (without any transition). Unless there's any advantage in terms of UX/UI, I'd go for keeping the same horizontal gradient we have in the original state before scrolling, since it looks pretty bleak when compared to the vivid gradients of the other parts of the site.
Extra: Another thing is that if you look at the vertical alignment, the logo is slightly higher than the menu items menu. Just a few pixels…
Extra 2: not sure about how this works better, but seems all the website content basically uses slight or no bold fonts. The bold navbar menu items work well with the logo, but maybe too strong vs. anything else in the page. Not sure about this one, just food for thought.
Given all points 1-4, this is how it looks when fixed (IMO way better in usability + aesthetics):
Given also point 5, this is how it looks like:
@ricardobaeta what do you think?
As a source{d} team member I want to have a customised url so I can link directly to source{d}'s homepage email input field on slack's join community block.
Since it points to legacy https://github.com/src-d/guide/blob/master/open-source/open_source_fridays.md
This is somewhat confusing.
Otherwise, that links will point to production instead of the same environment
So that we can pass them in helm chart deployment.
use only two tweets
(from #17)
Move from length to number
I think we could do some tiny adjustments to visual design. What do you think @marnovo @Serabe ?
As a mobile user i want to have a visual clue that I'm able to swipe the card to see more of them without thinking that the card I'm seeing is not optimised for mobile as it looks off-canvas (not all users mental model).
As an example
docker pull quay.io/srcd/landing:slackin
docker run --restart always -d -p 3000:3000 --name landing-SLACKIN -e SLACK_API_TOKEN=TOKEN quay.io/srcd/landing:slackin
docker exec -it landing-SLACKIN sh
/srv # netstat -na | grep LISTEN
tcp 0 0 :::8080 :::* LISTEN
tcp 0 0 :::8090 :::* LISTEN
/srv # ps -ef
PID USER TIME COMMAND
1 root 0:03 {supervisord} /usr/bin/python /usr/bin/supervisord
9 root 0:00 /bin/api -config /etc/production.yaml
10 root 0:00 /usr/bin/caddy --conf /etc/Caddyfile --log stdout
24 root 0:00 sh
36 root 0:00 sh
46 root 0:00 ps -ef
As it was pointed out by @rporres by src-d/blog#146 (comment) the landing/Makefile should import and follow src-d/ci/Makedile.main conventions.
copied from src-d/blog#150
Taken into account that this is not a private repo
When the window is resized, it moves over the person image
Blog posts which are present in the "upcoming" directory get the New status and are shown on the main page. We need to hide them the same way they are hidden on blog.sourced.tech
We definitely work with "big code" so can be nice to mention somewhere.
My perfectionist in me cries bloody tears:
sm size. It is not useful given the size does not fit in the screen. 🔒 (@erizocosmico)li so it is easier to tap. 🔒 (@erizocosmico)< · · · > for the slider needs to go to the bottom. 🔒 (@erizocosmico)hr in projects when screen is small enough and check line height (maybe at those sizes the background could just disappear and would be easier). 🔒 (@erizocosmico)tag v3-pre1 already at quay
https://quay.io/repository/srcd/landing?tab=tags
Footer social media icons don't show on mobile
Screenshot:
Darkish background, pale logo
As a user I want to access and know about the slack community link on the footer, where it actually says "community".
We need to adjust the menu for some custom breakpoints.
He is not able to see any of the slack forms since the redesign was launched.
iOS 10.2, in Chrome and Safary.
Reported by @rporres irl
Currently they live in the same Docker container which is not the best practise por Docker containers. It also needs Caddy to act as a reverse proxy. It makes the deployment in k8s rather obscure.
Once this is done, the Caddy config can be simplified removing the proxy parts once the landing helm chart ingress template is configured properly
parent #103
They're needed screenshots of different mobile resolutions so product will be able to decide if it exists any problem
complex set of dependencies it really is. we envision every organization running
it really is. We
Currently slackin needs reCAPTCHA configuration as per rauchg/slackin#311
If we want our current Dockerfile to work we need to checkout a previous version of Slackin. Adding
RUN git checkout 3ff77b9
before https://github.com/src-d/landing/blob/master/Dockerfile.slackin#L15 does the trick unless we want to use the last Slackin version with reCAPTCHA integration (which would need further work)
Let me know if you want a PR containing the above change.
We need to create proper documentation on the list of all files and folders related to the landing content and available fields/options available in the YAML and MD files, so that whoever wants/needs to update it not only can understand where to look and how to do it, but also doesn't break anything midway.
User story: "As a developer of the Landing I need that all people images follows the original specs; I would appreciate if I could have a template for creating next images"
Given the original specs
Circles are 75% of the block (and have a max-width of 200px) with white background, and a 5px #e8eced solid border. Images can ‘escape’ from the circles 20px above. - If this take much time, a possible solution would be to make the pictures not having this effect.
We need that all people pictures meets the same rule:
That measurements was based in Antonio's picture, that is the one who fits better the original especifications:
It would be great to have a kind of template to create new images.
It is needed to adjust –following the standard dimensions– the "new-guy" images:
Since we have not the original pictures the sources should be the current ones under static/img/people directory.
Because of that, and after the resizing/repositioning, I assume that some of them (Eiso, Máximo and Miguel, at least) will have extra transparent background below the waist, but it will not be a problem in the current /team page because the circle mask will hide that part.
Since https://github.com/src-d/landing/pull/65/files,
the hugo.config.yaml defines:
baseurl: "/"
What makes that favicons, menus in the header, and other links to have a wrong link.
Let's work with the @rporres proposal:
The hostname will be passed as a value when the image is build
Every public repo should be hosted in https://hub.docker.com/ instead of quay.
Once a new repo in dockerhub is created and images have been copied there, assign this issue to Infra team know so they can configure drone to work with the new registry instead.
We need some nicer transitions while switching between examples.
Adding Francesc to the management team section: https://sourced.tech/team/
@marnovo if you're feeling better can you take the photo of @campoy tomorrow, otherwise ask someone to do so the following Friday.
Some sections used a band + band_container system and other use mixins. Let's standardize.
Note the rectangles. Can be a problem with my system font... Should we load a bulletproof one?
As reported by @ricardobaeta the team page does not look ok in safary
Ideally it should be configurable, but due to kubernetes/ingress-nginx#720 (we will use k8s GCE ingress) I'm basically interested in api server answering 200 to GET / requests
"Perks and benefits" section's h1 does not have an id and it is impossible to reference it (and I will definitely want to reference!)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.