@Wyck, there are several translation files in order to minimize the amount of memory consumed by the translation on the front end. This can be very high number for languages that use many characters in every word like german ;) but not only it.

so yes, in theory there might be a situation in which you have the same word used in the front-end and admin and have different translation, but that is the job of the per language translation "manager" to make sure this doesn't happen.

haven't seen your original question, but if you don't get a translation at all and you can see in the relevant .po file that the string has a translation, then for some reason you don't load the right translation file for the user profile

@Rarst really nice!

@G.M. thank you :) I half–expected you to say “not enough classes” :D

haha

@Rarst no, yours + Fractal are enough :) If I have to criticize something it will be too much things in Application constructor and too much new inside classes methods :P

it's container defaults, where else... new as discussed yesterday, in some places too much constructor issues

well I think the $this->get() may go somewhere else than constructor. And yes, as discussed yesterday, I think that constructor issues is the only archicture weakness. But I think that thing will evolve, if you will support it.

Anyone have any thoughts on best practices for managing custom plugins on an online repository when making a bespoke WP site for a client?

Currently I have the site and the plugins use their own independent repositorys

just wondering how other go about this, in both managing code and deployment

Currently I use a wordpress stack as a basis for a site which I deploy from github and composer which keeps the plugins / core / dependencies seperate

But what about deploying content? (uploads, databases) when migrating servers for example?

@G.M. I hope that you one day will start to document your code...

@myol github.com/Rarst/release-belt

@kaiser which code is not documented?

Pretty much all of your code is missing docblocks.

Different topic: I was looking at your Registerables just now. How would you handle translation in JSON or YAML files?

Labels and such.

github.com/Giuseppe-Mazzapica/Registerables#labels

ah, seems I overlooked that

@MarkKaplun ah makes sense, the docs are confusing. I sorted it out except for some reason the password strength indicator text would not translate, no time to check why so I just use the best translate function ever... jQuery's .text

Killing the GitHub code highlighting?

they had swapped the detection lib or something, it suffered