[wp-meta] [Making WordPress.org] #5473: Update one line of copy on https://wordpress.org/hosting/
Making WordPress.org
noreply at wordpress.org
Mon Oct 19 11:07:45 UTC 2020
#5473: Update one line of copy on https://wordpress.org/hosting/
--------------------------------+---------------------
Reporter: chanthaboune | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone:
Component: WordPress.org Site | Resolution:
Keywords: needs-copy-review |
--------------------------------+---------------------
Comment (by Hristo Sg):
Replying to [comment:3 chanthaboune]:
> Replying to [comment:2 Hristo Sg]:
> > I think the proposed change doesn't make it clear that there is a
difference between having a .com account and having a fully-featured
hosting account with the stand-alone application installed. In my opinion
it would further the confusion that many people have distinguishing
between .com and .org.
>
> Thank you for the feedback! Do you have suggestions for what would make
that delineation clearer?
I am more on the technical side of things and copy is definitely not my
forte but I think Aaron's recommendation makes sense. If we want to
distinguish .com as something different than other hosting companies, the
copy has to reflect it. Not sure how the marketing people of .com want to
present the product now but probably mentioning it as a SAAS solution
compared to stand-alone app suitable for normal fully-featured hosting
accounts? On the other hand if the idea is to put it on part with the
"normal" hosts, it would make much more sense to be part of the group of
recommended companies.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5473#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list