OK here is a part for the display and a basic explaination of what I did to create it. First the part (if you unzip the fzpz file you will have the fzp file and svg files that make up the part) .The breadboard svg is what a svg to load in to parts editor to edit needs to look like.
elegoo-2.8in-tft-display.fzpz (12.7 KB)
I expect some parts of this explaination are going to be greek, but feel free to ask
Started with the pcb svg by grabbing the pcb svg for a Uno and stripping out the silkscreen leaving only the connectors. resize the drawing and rescale it to standard. Used vi (text editor) to change the pads to standard .1 header size. Edited it in Inkscape and removed the unwanted connectors (two from the left end on both sides of the board) and added the missing dual row connector on the right of the board (the position is just a guess and needs to be checked against a real board, their mechanical drawing doesn’t have position info for that connector). Renumbered all the pins to start at 0 and increase linearly as they should. Put in a board outline on silkscreen. Resize again, group silkscreen and both coppers save and done.
ungroup and resize
removed all the current connectors and the path (which defines their board outline) leaving only the TFT display.
Resize and rescale to the proper scale. Copied in the connectors from pcb view via copy/ paste in Inkscape. Resized the tft display to fit inside the connectors (In real life it doesn’t but the connectors won’t work in breadboard that way). Added a rectangle as the underlying board. Resize regroup save and done.
Changed the designations on the pins to match this board and removed the buses except for a 2 pin ground bus. It doesn’t look like there are any bused pins on this board other than the two grounds (although I could be wrong).
Was a mess, so completely redid it (this took most of the time as schematic is fiddly).
Ungroup, resize rescale. Changed the pin designations to match the board and arrange them to match breadboard. Run the part through the part checking script to catch any typos or errors, zip it to an fzpz and test it in Fritzing (including generating and checking the gerber output). Looks fine, so post it.