You can think of "resource" as an object in your application exposed on the web. REST actually talks about "resource representations" not: resources per se. This has to do with the Facade pattern and not tying your public interface with your internal implementation.
That said, for getting started you can think as "resource" being a web-addressable representation of an object in your application.
That said, for getting started you can think as "resource" being a web-addressable representation of an object in your application.