Add initial AWS blog post #364
Conversation
This is the first draft, but I wanted to at least get something on paper. I'm still trying to find another couple quotes from users, since I think that will help add weight to the overall writing.
Documentation build overview
Files changed
Show files (22) | 19 modified | 3 added | 0 deleted
|
| </div> | ||
| </div> | ||
| </div> | ||
| {# |
There was a problem hiding this comment.
This just swaps the testimonials for now to get them up, but we'll need to futz with it more if we want more than 2.
There was a problem hiding this comment.
The content of the blog post looks fine, but I will say it mostly reads like a shared native ad marketing page for both of us. If we want other readers to get something out of this, we probably should have a bit more depth. We could pretty easily talk about what parts of our infra improved, or what problems went away, moving to AWS -- manually syncing TB of docs between web servers, inconsistent builds and build processing.
| </div> | ||
| </div> | ||
|
|
||
| ## Features that make Read the Docs unique |
There was a problem hiding this comment.
This section feels off topic for a blog post about AWS. I get we probably should have some content describing us if AWS is linking to this post, but I think that content should target users that have no idea what RTD is. So, something more like a CTA to learn more, and pointing to a page with a more basic description of RTD would probably be best.
There was a problem hiding this comment.
Aye... definitely a good point. I wanted to highlight the quote and built the paragraph around it, but I think we can use the quote in a similar fashion talking about how S3 has enabled us to build PR builds perhaps.
There was a problem hiding this comment.
That's a great idea, that should fit really well.
| - [**Flask**](https://flask.palletsprojects.com/) – the Python web framework powering everything from hobby APIs to production workloads at scale. | ||
| - [**Python Developers Guide**](https://devguide.python.org/) - the official guide for developing Python itself, maintained by the core developers. | ||
| - Tens of thousands of other open-source libraries. Scroll almost any `requirements.txt` and you’ll see at least one project whose docs live on Read the Docs. | ||
| - Tens of thousands of other open-source libraries. Browse the documentation of the libraries, software, and services you use and it won't take long to find a project whose docs we host. |
There was a problem hiding this comment.
| - Tens of thousands of other open-source libraries. Browse the documentation of the libraries, software, and services you use and it won't take long to find a project whose docs we host. | |
| - Tens of thousands of other open source libraries. Browse the documentation of the libraries, software, and services you use and it won't take long to find a project whose docs we host. |
This is the first draft,
but I wanted to at least get something on paper.
I'm still trying to find another couple quotes from users,
since I think that will help add weight to the overall writing.
Fixes https://github.com/readthedocs/meta/issues/183
📚 Documentation preview 📚: https://readthedocs-about--364.org.readthedocs.build/