I use this:

src/ - all .c and .h files, object files are placed here too
resources/ - source files for my sprites/etc
static/ - all static files copied over when making a dist (DAT files are generated automatically from the resources and placed here during a build)
vendor/ - vendor code, including Allegro
dist/ - builds and dist zip files

I'm new to C, so I've never thought about project structure too much. It's just that I like simplicity. But I should probably at least put the .o files somewhere else.

As a convention, bin/ isn't for all non-textual files. It's for executable, often-though-not-necessarily binary, code. It would make better sense to have a separate directory for that. On a Linux file system you'd expect to install those kinds of things in /usr/lib/$program/. Locally it probably makes sense in a directory next to bin. Resources is a good description, but it's also very verbose. I like media/ for audio/visual data. Another good envelop is just data/.

In case some people can't think of an example, it means this is a right place to store scripts. A file with no extension could perfectly be a shell script (similar to a Windows .BAT file), perl script, Lua script or whatever. In the Unix/Linux world, the first line of the file would determine what should run it when you double-click it or type the name in command-line.

src and include.