Brian Casey

The image for profiles with either no "Sex at Birth" (previously Gender, which is the name of the field out of the API) or with DataStatus.Gender = 'blank' (other/do not...

Fixed (by simple expedient of checking for null MiddleName rather than the larger task of incorporating a generalized Profile Name utility).

I think we should just start with some guidelines. That'll take us a long way. If a new view developer wants to use Modules, then that will be a good...

There is no currently-existing "wikitree-common" package or repo. Sharing some common utility functions/classes across views (and across the dynamic tree / browser extension projects) would be helpful. I'm not sure...

I think a /common or /shared directory, either from the root or inside views/, makes sense. JS code/class files that can be used by multiple views could be put in...

I've updated the base, ahnentafel, and surnames views to catch problems with the starting profile. I added showInfoPanel and hideInfoPanel to wtViewRegistry to facilitate.

This is a good idea. I think we should add a "version" string to each View's "meta" content. Then it can be shown in a standard way as part of...

I think @MichalVasut's link is useful. A general Major.Minor.Patch scheme makes sense. With our views, though, I don't know if we'll ever have a new major branch from those guidelines....

My thought was to have a separate version for each view, stored in their meta() content. I think perhaps it helps debug things more, but maybe that's overkill.

I'm not sure I see the advantage in putting this into a readme text file. Having a "version" field in meta() seems much simpler, and then doesn't require any parsing...