3 ms·

Thanks Peter. I don't feel I was making excuses, but communicating our immediate priorities. The signup page seems fine, would you mind checking it again? I ta

Thanks Peter. I don't feel I was making excuses, but communicating our immediate priorities. The signup page seems fine, would you mind checking it again? I take your point on first impressions etc., well made. Would you mind telling me where you've seen spelling mistakes, I'll correct them. Thanks :)

petervandijck 16y ago
The docs have lots of spelling mistakes, can't find any now though, but I noticed about 3 while glancing through them earlier. The signup page is up now. Also, and I understand it's not a priority, the docs are a little wordy. For example: "you will need to make sure you comply with the following requirements". Why not write: "You'll need these:". Much friendlier. Or "In order to deploy an application on the Orchestra platform, one is required to login at https://my.orchestra.io/login https://my.orchestra.io/login. Once you've logged in, click on the Deploy A New App from your Dashboard. You will be taken to the Deployment interface where a few new terms might appear strange to you. Allow us to describe the fields you will see:". You can replace that entire paragraph with this sentence: "To deploy an application, login at http://my.orchestra.io/login http://my.orchestra.io/login, and click Deploy A New App." Another one: "Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering. Memcached is trivial to use and a very important part of any serious platform infrastructure. We are currently on an addon that will enable application deployers and Orchestra users to use Memcached. We will keep you updated with our progress." Instead write: "Memcached support is coming soon". That has the same amount of informational value and is easier to read. Just nitpicking on the writing now :) It does sound like a great product.
- EamonLeonard 16y ago
  Really appreciate the feedback on the documentation, Peter. Docs are a type of UI, I guess, and the same rules should apply. Consider them a work-in-progress! :)

petervandijck 16y ago

The docs have lots of spelling mistakes, can't find any now though, but I noticed about 3 while glancing through them earlier. The signup page is up now. Also, and I understand it's not a priority, the docs are a little wordy. For example: "you will need to make sure you comply with the following requirements". Why not write: "You'll need these:". Much friendlier. Or "In order to deploy an application on the Orchestra platform, one is required to login at https://my.orchestra.io/login https://my.orchestra.io/login. Once you've logged in, click on the Deploy A New App from your Dashboard. You will be taken to the Deployment interface where a few new terms might appear strange to you. Allow us to describe the fields you will see:". You can replace that entire paragraph with this sentence: "To deploy an application, login at http://my.orchestra.io/login http://my.orchestra.io/login, and click Deploy A New App." Another one: "Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering. Memcached is trivial to use and a very important part of any serious platform infrastructure. We are currently on an addon that will enable application deployers and Orchestra users to use Memcached. We will keep you updated with our progress." Instead write: "Memcached support is coming soon". That has the same amount of informational value and is easier to read. Just nitpicking on the writing now :) It does sound like a great product.

EamonLeonard 16y ago
Really appreciate the feedback on the documentation, Peter. Docs are a type of UI, I guess, and the same rules should apply. Consider them a work-in-progress! :)