-
Notifications
You must be signed in to change notification settings - Fork 882
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
Improve copy for author archives in onboarding wizard #6699
Comments
@mariekerakt We've got a request for a copy improvement as described above. Can you take a look and improve the copy? |
@willemientje Can your team provide better copy. Info described above |
@CarolineGeven Is it a matter of providing new copy or should the copy above just be used again in the wizard? |
@willemientje I'm unsure about that. As this is UX, I'm not the best one to give the answer. (cc @moorscode, @afercia, @Annelieke) |
#6933 Also improves copy of the configuration wizard |
Please use the same copy. |
While not using the same copy, the option now has a description of the implications and the reasoning: While I am tempted to close this thread as changes have been made, I also think that the description can be improved upon by at least linking to the same duplicate content article as the archives pages does. |
We turn off the author archives as this is better for SEO. We explain this in the advanced settings under TItles and Metas -> arcguves as shown below.
![schermafbeelding 2017-02-20 om 16 34 45](https://cloud.githubusercontent.com/assets/8614579/23131617/efd7fa1e-f78a-11e6-9c66-0bce3e491b56.png)
We should also explain this in the onboarding wizard as well. A lot of our users will not see the explanation we've given in the Archives tab, as we turn off the Titles and Metas tab after users have successfully run the onboarding wizard.
We turn off the author archives for anyone who selects 'person' or who selects 'company' with only one author, but do not explain that we do this or even why.
@Annelieke, could you please take a look at this?
The text was updated successfully, but these errors were encountered: