Skip to content
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

New user guide for Customizer #95

Closed
ghost opened this issue Apr 19, 2015 · 1 comment
Closed

New user guide for Customizer #95

ghost opened this issue Apr 19, 2015 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 19, 2015

Last revised on 2016.01.20

Removed redundant details under the numbered points.


This is part of issue #86 but specifically for new user guide for Customizer.

The existing user guide found in the Manuals page has been made available in late 2011. This however, is relevant for 3.2 releases and no longer relevant for latest 4.1 release at present.

Few years ago, the first user guide was mainly written by Customizer Development Team. This time, I'd like to make the user guide creation to be more open to end users.

As such, the purpose of this issue is to discuss the following points:

  1. Do we need new user guide for 4.1 (or newer, if any)?
  2. What is the appropriate method to prepare the user guide?
  3. How to upload; Where to upload the user guide?

Above all, this discussion is not for selecting the best method, but selecting appropriate method such that most users able to access and commit to user guide with minimal hassles.

There are many collaboration-based tools available, but intentionally not mentioned here, so just let the suggestions flow in the comments below.

EDIT Don't just state your point. Explain or justify the reason for your suggestion.

@ghost ghost changed the title Customizer missing new user guide New user guide for Customizer Sep 16, 2015
@ghost
Copy link
Author

ghost commented Jan 19, 2016

The answer is "no".

There will be no user guide for Customizer 4.x releases. The Wiki has been updated since and should cover the basic needs and explanations. I was too distracted with various ways of making documentation; Then I finally realized that Wiki should be sufficient.

@ghost ghost added the Won't Fix label Jan 19, 2016
@ghost ghost closed this as completed Jan 19, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants