Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

#1: Initial revision by user avatar Monica Cellio‭ · 2021-01-13T16:04:12Z (almost 4 years ago)
How does help get propagated, both seeds and updates?  (What do doc maintainers need to know?)
I know this is buried in Discord somewhere, but for better findability:

There is a seeds script (where?) that takes *new* help topics and propagates them to communities on a network.  Where do those help topics need to be deposited?  (We're using a separate docs repo to create them and then they get pulled into the qpixel repo, IIRC.)

I know that *updating* help topics is not as straightforward.  How do we propagate changes now?  Is there anything that doc-team members working on updates should be aware of, beyond reducing the number of updates (batch changes)?