-
Notifications
You must be signed in to change notification settings - Fork 14
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
Refactor to mimic wp-cli docs process #9
Comments
Per bugscrub today, we're keeping this in the |
There's also a wp-github-sync plugin (and a couple other plugins/theme tweaks) that could be used to keep markdown files in a GitHub repo synchronized with posts in WordPress. I've functionally proven that in a local environment and personal repo, so if we decide to alter our process and stop using docpress then I've found another option for us. |
Right now we've got the docs in a pretty good place and probably will not be making this change. |
I worked on refactoring the docs to remove docpress and simplify to GitHub Pages, just waiting on the GitHub Pages deployment process to catch up to all my commits. My forked repo is here: https://github.com/jeffpaul/docs. Sample docs site is here: https://jeffpaul.github.io/docs/. If I can get things cleaned up a bit (once GitHub Pages deploys catch up to my commits), then I’ll open a PR to merge my changes upstream and we can assign the wptide.org domain to the GitHub Page and be done with the docpress mess. |
@jeffpaul how is this going to work as a WordPress theme? |
@derekherman skipping WP, having docs live separately as their own repo |
See: https://github.com/wp-cli/handbook/. Specifically:
Our current docs site is being spun up quickly for WCEU, but as we look to refactor that to be a more maintainable site we should consider recommendations from other WP teams. We can check with the Meta and Support teams to see if they have any best practice recommendations.
The text was updated successfully, but these errors were encountered: