Learning how FPGA's work from the transistor up is very ambitious. There's a lot of stuff inside an FPGA, and for the most part you never have to understand it to the level of detail that you are seeking. In fact, it's probably better if you ignore that stuff at first and learn some practical FPGA stuff instead.
The reason why you don't need to know those fine details is because the FPGA compiler will do it for you. Using VHDL or Verilog, you tell the FPGA compiler what you want, and it figures out how to do it for you. You don't need to know what gets programmed into the LUT's, where that LUT is located, or how to route the signals to/from the LUT. This also helps when you move from one FPGA to another. A Spartan-6 has a different LUT architecture than the Spartan-3's, and you don't want to have to learn a completely new architecture for each chip you use.
Then, as you get into it more you will learn more of the internal workings of the FPGA. Not down to the transistor level, but you will learn about the different kinds of signal routing resources, RAMs, I/O Blocks, carry logic, etc. Knowing about this kind of logic will help you make better use of the FPGA-- making your logic smaller and faster.
One really cool way to find out about the internals of a Xilinx FPGA is to write some VHDL/Verilog code and compile it. Then using the Xilinx FPGA Editor to go in and examine what the compiler did, looking at signal routing, slice usage, LUTs, and Flip-flops. This is most useful for me in understanding why my logic was bigger than I thought it should be. I would guess that 95% of the time you don't have to understand the inner working of an FPGA in more detail than what FPGA Editor will give you.
I'd go for anything Video (especially HD video) related:
- these boards often have reasonable FPGAs
- tend to be on a reasonable host interface
- are usually rather hard to kill due to the studio environments
One of favourite FPGA projects of a friend of mine, http://nsa.unaligned.org/, used HD transform boards.
Another of my personal favourites that I abused a bit myself, is a BlackMagick Intensity HD capture card, coming with a nice set of video peripherals, a decent microcontroler, and an Spartan 3.
After some abuse, it's probably the cheapest non-academic devkit for PCI/PCIe work on FPGA. It seems to be going new for $120-$150 on ebay these days, and you can probably score one with damaged video interface chips.
Best Answer
The materials declaration is used if your product needs to comply with RoHS or other regulatory restrictions on material content.
RoHS not only requires that your product not contain certain materials, but also that you document this fact. Typically, in order to do that, you need to request the vendors of all the components in your design to provide a material declaration like the one you showed. This documentation isn't just needed for the chips but also the pcb laminates, the soldermask, the solder, the adhesive stickers with the serial number, etc.