You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Example code, that is not just added to the blog post, example themes and plugins can now housed in a separate GitHub repo on the Learn WordPress GitHub organizations.
We would need to come up with the process and some ground rules on how repos are created, updated and maintained.
The text was updated successfully, but these errors were encountered:
Jotting down some rough thoughts (or, as I call it, thinking out loud):
Generally speaking, I don't think code needs to be updated unless the code in the associated post is updated.
I mostly view posts as a static point in time, and some posts will naturally no longer be relevant in the future. I'd rather writers not be too worried about maintaining repositories on something they've written a year or two ago.
I also don't want to put the burden on the editorial group to maintain code in repos that they may not be familiar with.
One thing to consider is plugins/themes with a package.json file. Eventually, the package dependencies may become outdated.
There's also a chance that if someone updates the dependencies that specific code needs to be updated (e.g., use within a webpack.config.js file).
Example code, that is not just added to the blog post, example themes and plugins can now housed in a separate GitHub repo on the Learn WordPress GitHub organizations.
We would need to come up with the process and some ground rules on how repos are created, updated and maintained.
The text was updated successfully, but these errors were encountered: