A Community post for announcing the resource based api

[sumeyyeKurtulus]

Description

Relates and announces #25761

• Adds a community article announcing ABP’s optional --resource-api mode for Angular generate-proxy
• Explains why Resource APIs fit Signal-based UIs, why generation is opt-in, and why only GET endpoints get Resource helpers
• Covers generated API shape (*Resource methods, Signal inputs, ResourceRef), usage examples, and best practices (rxResource + RestService vs httpResource)

---

Waiting for this to be published #25761

[Copilot]

Pull request overview

Adds a new Community Article that announces and explains ABP’s opt-in --resource-api mode for Angular proxy generation, framing it in the context of Angular Signals/Resources and positioning it as a Signal-friendly companion API for read (GET) operations while keeping existing Observable-based methods for mutations.

Changes:

• Introduces a Community Article describing the motivation for Angular Resource APIs and how they reduce UI boilerplate for read operations.
• Documents the opt-in generation behavior (--resource-api), generated API surface (e.g., *Resource methods, ResourceRef), and reactive request construction patterns.
• Provides usage examples and best-practice guidance for choosing rxResource (via ABP’s RestService pipeline) over httpResource.