Hi everybody, first post here. I’m self hosting Ghost and everything’s been going well so far, but I found out recently that in order to translate everything in my blog to Spanish, I’m going to have to fork the project, instead of just translating the theme.
So, according to documentation, it seems I’ll have to fork the project, work on it, then run yarn archive and update my existing instance with the --archive flag by ghost cli. Am I right so far?
Are there any good practices you recommend when forking Ghost? I’m probably running a backup prior to updating, and I see there’s a --rollback flag that might be useful. I just don’t want to lose stuff and have to manually migrate/set up the instance again.
I’m curious, given ongoing work to get everything except themes translated (and several community efforts to offer translated themes, too), what is missing that you’d need to fork the core for?
Hi, thanks for the responses! @Cathy_Sarisky , I was unaware of the ongoing work. I’m getting acquainted to the community and platform, so whatever info you have on that topic will be greatly appreciated. I’ve translated Casper theme myself, as the documentation suggests, and it’s worked out fine, but for some exceptions. Those are mostly unimportant, like the “x min read” part, but the “free preview” in articles being in English is annoying, and it’s a particularly visible part of every post/page where I use them (uploaded screencap).
Other than that, I also intend to tinker with Ghost a bit, partially to improve my skills and to check Ghost’s potential, so I’d eventually try to fork the project even if it was fully translated to Spanish.
Thanks a lot @Cathy_Sarisky ! That solved it. With this fragment translated, I can postpone translating the other remaining fragments in the site, as they are mostly unimportant.
Suscribed to your blog too. Thanks again!
