-
Notifications
You must be signed in to change notification settings - Fork 22
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
Company setup should have a logo field #73
Comments
@silentworks @claudey Who to upload the images to? |
We can begin by asking for the URL to the logo. If they have a website they could have their logo on there and should be able to use the same link here. But that's not a good long term solution. |
We used to do this with AF Radio, these guys deleted the images and we were left with dead images. Just saying. |
as per the scenario @bubunyo mentioned, then I'm imagining if the image doesn't exist, a placeholder of sorts can be loaded instead |
I think cloudinary is a good option |
@bubunyo Sure, I was thinking of what would be the cheapest option in the interim. If we can go with them. |
I think it should suffice for about a year. And i am sure by the time we
have more than enough traffic there will be a way it will pay for itself so
we can move it to s3 of gcloud
…On Wed, 27 Feb 2019 at 13:18, Yaw Boakye ***@***.***> wrote:
@bubunyo <https://github.com/bubunyo> Sure, I was thinking of what would
be the cheapest option in the interim. If we can go with them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#73 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEzH-oBoAeptLfUJSIKI46_xz_zaMtc7ks5vRoWNgaJpZM4ay-QF>
.
|
@bubunyo I'm guessing, per @seanmavley's suggestion, we can have an image like this to use, when they don't supply a logo url, an image like this loads from our @yawboakye @silentworks thoughts? |
Makes sense to me. |
Resolved in ebc4518 |
We should allow for a company to provide a logo when signing up.
The text was updated successfully, but these errors were encountered: