Explore use of Wordpress for front-end

[richpomfret]

Examine whether this would be a suitable route to go down, or other possible alternatives.

[richardofsussex]

Can someone please give me the URL of the spec for the front end? It's the usual nightmare trying to navigate the Google Docs metaverse, where folders and a sensible hierarchy of folders/docs doesn't appear to be part of the plan ...

[PatReynolds]

Hello Richard, I've shared the document with you, and sorted out the folders concerned: [image: image.png] It is in the mail ComeTT Online Transcription folder, rather than a sub-folder. Best wishes, Pat *- -* *Dr Pat Reynolds* Executive Director A Charitable Incorporated Organisation registered in England and Wales, number 1167484 VAT registration: 233 0105 70 *Join us on social:* [image: : https://www.facebook.com/FreeUKGEN] https://www.facebook.com/FreeUKGEN <https://twitter.com/FreeUKGen> <https://www.instagram.com/freeukgenealogy/> <https://www.pinterest.co.uk/FreeUKGenealogy/> Please read our *Privacy Notice* <https://www.freeukgenealogy.org.uk/files/Documents/Privacy-Notice.pdf> for information on how we will protect and use your data. <https://www.easyfundraising.org.uk/causes/freeukgenealogy/?utm_campaign=raise-more> +44 1723 362616 +44 7943 145387 Westwood House,Westwood, Scarborough YO11 2JD, UK

…

On Tue, 21 Jun 2022 at 20:24, Richard Light ***@***.***> wrote: Can someone please give me the URL of the spec for the front end? It's the usual nightmare trying to navigate the Google Docs metaverse, where folders and a sensible hierarchy of folders/docs doesn't appear to be part of the plan ... — Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQLSBQW3J3WPWUCPNKS4C3VQIJIJANCNFSM5ZNCFOFQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[richardofsussex]

One rationale for looking at Wordpress is that if ComETT is developed as a Wordpress plugin, it will be very straightforward to make it available to other organisations (which I understand to be one of our goals). The process of installing Wordpress plugins is straightforward, and widely understood. If we were to produce something which is locked into our Ruby stack, I can't begin to see how we could make it possible for anyone other than FUG to use it.

Another argument is that we could do the coding of this development in PHP. I think it would be much easier to find volunteer developers with PHP and Wordpress skills than to find more Ruby programmers - we are already challenged on that front. (I, for one, would be able to help.) Also, setting up Wordpress and pulling in our plugin code from GitHub would be orders of magnitude simpler for a developer than installing our current development environment (a task which has taken me two months, and I'm not finished yet).

Conversely, this direction of travel requires us to be able to access our MongoDB databases using PHP code. The MongoDB site talks about a PHP driver (https://www.mongodb.com/docs/drivers/php/), but this would have to installed and shown to be fit for purpose before we could be confident about pursuing this approach. Maybe that should be the first task to address?