dvc.org
dvc.org copied to clipboard
iterative
feat: add platinum service support page
- Closes https://github.com/iterative/dvc.ai/issues/67
- Added platinum service support page based on document
It's still WIP. Preview so far:
- [ ] Request a quote form in a dialog
- [ ] Update the missing logos
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This looks great @yathomasi! @djsauble is working on a more prominent logo for DVC Enterprise Services. We should put alt text on this so that it is searchable as an image when that's complete.
I think some clarification needs to be made to the copy "keyboard support" if possible. cc: @joshcohen15
And @dberenbaum's note about the customer success stories.
@jendefig Are you talking about these? If so, then that's great. These are quick icons I could find on the Icons list. Also, feel free to suggest topics, modules and text highlights.
I think it's also fine to publish as it and reiterate unless we want some big changes.
Are you talking about these?
No, these icons look great!
I'm talking about having an actual image logo for DVC Enterprise Services with alt text attached to it so that when someone types it in google the image shows up and people can find and share it in UGC. It will also look better at the top of the page.
"Platinum Services" like "Studio" are too common of phrases for anyone to find absent the connection with DVC.
But I'm also totally ok in moving forward and iterating in the interest of time.
Good stuff. A bit unrelated.
Since top menu becomes crowded - can we drop the Other tools? It's really only VS Code. Make VS Code an icon nearby GitHub and Discord?
Later - can we merge Course, Community, etc at some point?
Also, do we show now anywhere our regular support channels? (just to clarify)
Later - can we merge Course, Community, etc at some point? Also, do we show now anywhere our regular support channels? (just to clarify)
The Community page needs some serious overhaul, but is where they are found. I'm working towards it starting with finding more quotes. See related. The other support channels can be arrived at through a button at the bottom.
fyi, I'm working on a new logo for DVC platinum services. This doesn't necessarily need to block the PR, since we can add it later, but wanted you all to have a heads-up.
@yathomasi It sounds like everyone is fine to merge and iterate.
@shcheklein The one support channel that gets completely "dropped" here is email.
@yathomasi Sorry for the late feedback. Can we make the How we can help? message optional in the request quote form? Once they provide the team size and email address, I think we have enough info to reach out to them.
Also, once there is some issue in the request quote form, it's not possible to close it even after fixing the issue. Eg, here, I tried to submit without the message. I could not close the form after that.
https://github.com/iterative/dvc.org/assets/32855442/f8d78145-84d1-4bd8-8be3-808996d34dec
@tapadipti, Oops, silly mistake; I forgot to change the submitting state. I have quickly dropped a PR to fix that: https://github.com/iterative/dvc.org/pull/5145. Thanks for reporting.
Also, I am not sure about making the field How we can help? optional. People will have queries, concerns that they want to address. I think it should be fine. I added the * sign to show it's required so people will not get confused.
People will have queries, concerns that they want to address
Agreed. But some people might want to just discuss all that over all call instead of having to write it down beforehand. But it's ok if you strongly feel otherwise.
But some people might want to just discuss all that over all call instead of having to write it down beforehand. But it's ok if you strongly feel otherwise.
I hesitated a bit because I already proposed having Calendly so that users could directly setup meetings without having to fill out the form. But we agreed to use Hubspot, so I assumed we were looking to collect the data.
cc: @dberenbaum @jendefig Feel free to chime in and let me know if we want to make the field optional.
Hi, a minor feedback regarding the colors: I tried to click on them thinking they were links, as all three colors are closer to link colors for links and visited links.
I cannot tell what those three different colors mean, and some colors seem out of place (not sure why "experience" and "technical" are being colored, etc.)
I first tried to click on the links too like @skshetry. I love color and think that they are mostly highlighting keywords that we would want to stand out. There was one today I noticed that maybe should be colored but was not -> scalability under the Best practices and standards heading and also 'standards' there as well.
So maybe we add this to the next issue to update the logo when it's ready and make these corrections.
It would also be super amazing to make content for these items that we could point to with links ultimately to prove these points. There are some we could do right now like "End to end solution" - Alex Kim's video. 🤔
About making the How can we help field optional, looks like it's ok to make that change.
Re. colors, I agree with @skshetry at least on the blue color. Can we use a color other than blue? Imo, it's even better if we remove these colors and use a different style for highlighting - eg, make the text bold? Or use a single color for all these highlights, so that once a user finds out that one of them is not a link, they understand that all the others are also not links. For the ones that have content to link to, like @jendefig suggested, we can make them blue.
Thanks to everyone for the review. I have created a separate ticket at https://github.com/iterative/dvc.org/issues/5152 for this issue. Feel free to add more if you have.