-
Notifications
You must be signed in to change notification settings - Fork 40
Document how content is published from this repo to nodejs.org #315
Comments
Great question, about building process. I also don't know how it's working now, and my suggestion is going directly from nodejs/node repo with some |
We need to understand build flow first, and then make decisions. I think, docs for all versions are rebuilds everytime with a new release. Not sure that someone implements atomic build/deploy, because it's so hard and complicated for simple docs website. |
OK, going by the other issue on the build repo, it sounds like this content isn't being published anywhere right now |
@nschonni yeah, i18n docs never be live and we should figure out way to deliver it. What is our plan? |
Could you take a look on possible ways and try to implement it? I'm asking because don't want to duplicate work, again ;) Let me know if it works for you and how can I help |
I've unarchived this repo so I can close all PRs and issues before re-archiving. |
It's not clear in the documentation here how the content in this repo get onto the nodejs.org website. I don't see anything with a quick search of https://github.com/nodejs/build that would indicate it's getting pulled down.
I want to keep this separator from #310, but it may influence that direction. EX: if there is nothing publishing content outside of a manual release process, there is no point continuing translations for old content unless we can change that.
The text was updated successfully, but these errors were encountered: