New texts and slides on the main page #51
Conversation
Gatsby Cloud Build Reportmlem.ai 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 1m PerformanceLighthouse report
|
There was a problem hiding this comment.
OK these are the most important texts in the whole site probably so let's give them some extra thought 🙂 Cc @omesser
| bold: 'Save your model with a single command', | ||
| text: 'Stick to your training workflow' |
There was a problem hiding this comment.
What command? The gif shows a Python call (model.api.save()), Maybe
| bold: 'Save your model with a single command', | |
| text: 'Stick to your training workflow' | |
| bold: 'Save ML models from your Python code.', | |
| text: 'Sticking to your existing training workflow' |
| bold: 'Use simple YAML file to save model metadata', | ||
| text: 'Use the same human-readable format for any ML framework' |
There was a problem hiding this comment.
I understand these top texts try to show the basic workflow of the tool, right? So maybe
| bold: 'Use simple YAML file to save model metadata', | |
| text: 'Use the same human-readable format for any ML framework' | |
| bold: 'Model metadata into YAML automatically.', | |
| text: 'Use the same human-readable format for any ML framework.' |
| bold: 'Deploy your model anywhere you want', | ||
| text: 'Switch between deployment providers with a single command' |
There was a problem hiding this comment.
💅🏼 punctuation (optional in featured "marketing" texts so up to you, but preferable IMO).
| bold: 'Deploy your model anywhere you want', | |
| text: 'Switch between deployment providers with a single command' | |
| bold: 'Deploy your model anywhere you want!', | |
| text: 'Switch between deployment providers with a single command.' |
Not sure about the term "deployment provider" though. Production environments? Cloud providers? Servers? Hosting?
aguschin
changed the title
Co-authored-by: Jorge Orpinel <jorgeorpinel@users.noreply.github.com>
Co-authored-by: Julie <43496356+julieg18@users.noreply.github.com>
|
@jorgeorpinel, sorry for not accounting for all your feedback, I'm merging this for the sake of time. I've accepted some, it was useful here. |
|
No worries. Should I make an issue to discuss #51 (review) later? Pretty important texts |
|
Yes, please do @jorgeorpinel 🙏 |
No description provided.