Way to hide the front-end?

Not directly in GP no, it’s always visible when it’s enabled.

However you could use GP Require Login (https://www.ads-software.com/plugins/gp-require-login/) to effectively do this.

Thanks @gregross! That’s just what I needed. It’s very hard to Google for info related to Glotpress. Google doesn’t seem to know how to handle it and shows all the repositories and such in results.

One more quick question: when we do a new version of the plugin, is the best practice to just Branch it? Or what’s typical/best there? This is all very new to me, so just trying to figure out how to minimize the amount of work done, since there probably won’t be a ton of differences from one version to the next.

Depends on your use case, you could branch it but “branching” in GP doesn’t copy any of the history or translations across so that would be a significant amount of work.

In most cases you simply use a rolling release, so you create a single project for your plugin and then when you have done your string freeze for the next version, import the originals again and let the translators work to get them up to date before you do the actual release.

• This reply was modified 6 years, 7 months ago by Greg Ross.

Ah, okay, that makes sense. So importing the originals again will replace the previous ones, but any previous translation work that still matches, will be left in tact, right?