-
Notifications
You must be signed in to change notification settings - Fork 36
Enhance Landing Page Content for Clarity and Professionalism #603
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,52 +8,52 @@ | |
"description": "homepage install button" | ||
}, | ||
"home.quickstart": { | ||
"message": "All About Your Modern Apps by Platform Engineering" | ||
"message": "Everything You Need to Know About Modern Apps with Platform Engineering." | ||
}, | ||
"home.easyshipping": { | ||
"message": "Dynamic Configuration Management" | ||
}, | ||
"home.easyshipping.1": { | ||
"message": "Manage all application operations in one place, in a unified easy way" | ||
"message": "Easily manage all application operations from a unified platform." | ||
}, | ||
"home.easyshipping.2": { | ||
"message": "Environment-agnostic application configurations" | ||
"message": "Environment-agnostic application configuration for seamless deployment." | ||
}, | ||
"home.easyshipping.3": { | ||
"message": "Standardized and flexible platform configurations" | ||
"message": "Standardized yet flexible platform configurations tailored to your needs." | ||
ruquanzhao marked this conversation as resolved.
Show resolved
Hide resolved
|
||
}, | ||
"home.easyshipping.4": { | ||
"message": "Kubernetes-first, lightweight and user-friendly" | ||
"message": "Kubernetes-first, lightweight, and user-friendly for modern workflows." | ||
ruquanzhao marked this conversation as resolved.
Show resolved
Hide resolved
|
||
}, | ||
"home.platformengineering": { | ||
"message": "Enable Developer Self-Service" | ||
"message": "Empower Developer Self-Service" | ||
}, | ||
"home.platformengineering.1": { | ||
"message": "Fulfill the customized needs with reusable building blocks" | ||
"message": "Meet customized needs with reusable building blocks." | ||
}, | ||
"home.platformengineering.2": { | ||
"message": "A growing open module ecosystem integrated with various cloud-native infrastructures" | ||
"message": "A growing ecosystem of open modules integrated with various cloud-native infrastructures." | ||
}, | ||
"home.platformengineering.3": { | ||
"message": "An efficient collaboration paradigm between App Developers and Platform Engineers" | ||
"message": "An efficient collaboration model between app developers and platform engineers." | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I want to capitalize 'App Developers' and 'Platform Engineers' because these terms are important concepts in the Kusion. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hey @ruquanzhao , Absolutely we can emphasize these two terms to give them more weight in the sentence. Making them bold or using strong tags would help highlight their importance effectively. As for the word paradigm, you're right - its interpretation depends on the context. In our case, it clearly conveys a model, pattern, or way of thinking, a piece of terminology that aligns well with the groundbreaking work we're doing. Using it here adds depth and reinforces the innovative approach we're taking. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is the only remaining change suggestion. I will approve these requests once this comment is resolved. |
||
}, | ||
"home.platformengineering.4": { | ||
"message": "Building the golden path for end-to-end DevOps lifecycle management" | ||
"message": "Building the golden path for end-to-end DevOps lifecycle management." | ||
}, | ||
"home.enterpriseops": { | ||
"message": "Built-in Security and Compliance" | ||
}, | ||
"home.enterpriseops.1": { | ||
"message": "From the first line of codes to production runtime" | ||
"message": "From the first line of code to production runtime." | ||
}, | ||
"home.enterpriseops.2": { | ||
"message": "Codified shift-left validation to detect configuration risks" | ||
"message": "Shift-left validation to detect configuration risks early." | ||
}, | ||
"home.enterpriseops.3": { | ||
"message": "Extended check stages for workload lifecycle" | ||
"message": "Extended validation stages throughout the workload lifecycle." | ||
}, | ||
"home.enterpriseops.4": { | ||
"message": "Enterprise-grade fine-grained cluster control for Kubernetes" | ||
"message": "Enterprise-grade, fine-grained cluster control for Kubernetes." | ||
}, | ||
"home.whoisusing": { | ||
"message": "Adopted by" | ||
|
Uh oh!
There was an error while loading. Please reload this page.