-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comparison: Cloudflare Pages #229
Conversation
Create a comparison page for Cloudflare Pages: https://pages.cloudflare.com/
We are talking about "Documentation projects" more than a Blog :)
Cloudflare Pages is great for hosting SPA (<em>Single Page Application</em>) for frontend developers. | ||
However, when talking about <strong>technical writers</strong> and <strong>documentation projects</strong>, | ||
Read the Docs is <em>the</em> perfect solution. | ||
</p> | ||
<p> | ||
Let's compare it to know what you can expect when deploying your project's documentation to Read the Docs. | ||
</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cloudflare Pages is great for hosting SPA (<em>Single Page Application</em>) for frontend developers. | |
However, when talking about <strong>technical writers</strong> and <strong>documentation projects</strong>, | |
Read the Docs is <em>the</em> perfect solution. | |
</p> | |
<p> | |
Let's compare it to know what you can expect when deploying your project's documentation to Read the Docs. | |
</p> | |
Cloudflare Pages is great for hosting a SPA (<em>Single Page Application</em>). | |
However, when talking about <strong>software documentation projects</strong>, | |
Read the Docs is <em>the</em> perfect solution. | |
</p> | |
<p> | |
Understand the benefits of deploying your project's documentation to Read the Docs. | |
</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hrm, your suggestion is good. However, I'd like to keep "technical writers" somehow in the sentence because I want to rank on it --I put it there on purpose. We are not mentioning that role enough and we have been focusing us more in "developers" without reaching many technical writers.
Also, "Cloudflare pages is for frontend developers" is a concept that works great to me because the reader will immediately realize that Cloudflare is not for them. It's the way they sell themselves:
which makes sense since they allow creating some kind of APIs.
Also also, I'd like to leave the "documentation projects" as-is, since we already have customers documenting other type of projects that are not software. Like hardware, for example.
I'll take some parts of this suggestion. However, I'd really appreciate your thoughts here about my points to continue the conversation. After that, we can change this paragraph in a following PR 👍🏼
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. I was mostly just trying to cleanup the language and couldn't find a good way to keep it in there, but fine with keeping it 👍
I took my own decision here, but we can upgrade this paragraph :)
Create a comparison page for Cloudflare Pages:
https://pages.cloudflare.com/
📚 Rendered version: https://readthedocs-about--229.org.readthedocs.build/comparisons/cloudflare-pages/
📚 Documentation preview 📚: https://read-the-docs-website--229.com.readthedocs.build/