-
Notifications
You must be signed in to change notification settings - Fork 42
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
Migrating block editor end user docs issues from Trello to GitHub #109
Comments
Working on 5.8 Widget Screen: https://trello.com/c/E74yu6Ua/104-widget-screen?filter=label:5.8,label:WP5.8 |
5.8 widget screen is all good. |
@zzap working on 5.8 Query Loop Block |
@zzap Trello card did not have a linked live document --> https://trello.com/c/aRyoj9sq/115-query-loop-block?filter=label:5.8,label:WP5.8 or corresponding /core doc. I did find --> https://wordpress.org/support/article/query-loop-block/ published on the same day referenced by @annezazu and it looks all good! This Trello card can be closed. |
@zzap working on 5.8 Block Pattern |
https://wordpress.org/support/article/block-pattern/ Looks great! Changes referenced reflected and live. |
@zzap Reviewed 5.8 Block Pattern Directory. There isn't any context or source to compare on Trello (https://trello.com/c/fvlMKyyO/117-block-pattern-directory?filter=label:5.8,label:WP5.8), but the Block Pattern Directory article is live on /support |
Context
Before we created this repository, block editor end user documentation was managed in Trello board and team's Google Drive folder. The way it was managed is recorded in this video.
Now we want to migrate all relevant Trello cards here.
Steps to get involved
Why don't we use automated tools for migrating Trello cards into GutHub issues?
Because we need a human to review Trello card and associated docs in Drive, compare it to the actual page at wordpress.org/support and confirm that a card is still valid.
We can, however, use something like Zapier's Create issue in GitHub when card moved to list in Trello (you have to be logged into Zapier to see it), which would be incorporated to move the card to the "GitHub issues" or something when the card is verified by a human as still valid. Archive card otherwise.
The board looks overwhelming, where to start?
Cards are labeled with WordPress versions, amongst other labels and can be filtered out. At the moment there are 5.8, 5.7 and 5.6 version labels. My suggestion is to start from 5.8 and go backwards. Once we're out of version cards we'll see what's left and act accordingly.
When new page is published, this page should be updated with the link to the newly created page: https://wordpress.org/support/article/blocks/
The text was updated successfully, but these errors were encountered: