mirror of https://github.com/affaan-m/ECC.git synced 2026-10-17 05:35:36 +02:00

Files

T

Affaan MustafaandGitHub c70874fae9 feat(pi): curated pi/core skills+prompts profile, CI load test, and 2.2.2 release sync (#3264 )

Adds a curated, Pi-native, skills+prompts-only profile at pi/core/ for downstream packagers that mirror GitHub Releases.

- manifests/pi-core.json: explicit include lists, per-item exclusion reasons, curation rules, safety allowlists; every root skill and command must be classified.
- scripts/build-pi-core.js regenerates pi/core deterministically (package.json from VERSION, LICENSE, README.md, CURATION.md, skills/, commands/); --check fails CI on drift. council is renamed ecc-council inside pi/core only.
- Safety checks: no callable endpoints outside the allowlist, no npx/curl|sh/pip install, no secrets, no absolute home paths, no symlinks, valid frontmatter, no duplicate names.
- CI: build + drift check and an offline Pi CLI load test of pi/core.
- Release: VERSION, package.json and pi/core/package.json at 2.2.2, CHANGELOG, tag-triggered release verification, and a two-week cadence in CONTRIBUTING.md.

pi/core: 123 of 293 skills and 24 of 94 commands; 35,006 characters of skill description text.

2026-09-29 20:24:05 -05:00

1.8 KiB

Raw Blame History

Rendering Strategies

Angular supports multiple rendering strategies to optimize for SEO, performance, and interactivity.

1. Client-Side Rendering (CSR)

Default Strategy. Content is rendered entirely in the browser.

Use case: Interactive dashboards, internal tools.
Pros: Simplest to configure, low server cost.
Cons: Poor SEO, slower initial content visibility (must wait for JS).

2. Static Site Generation (SSG / Prerendering)

Content is pre-rendered into static HTML files at build time.

Use case: Marketing pages, blogs, documentation.
Pros: Fastest initial load, excellent SEO, CDN-friendly.
Cons: Requires rebuild for content updates, not for user-specific data.

3. Server-Side Rendering (SSR)

Content is rendered on the server for the initial request. Subsequent navigations happen client-side (SPA style).

Use case: E-commerce product pages, news sites, personalized dynamic content.
Pros: Excellent SEO, fast initial content visibility.
Cons: Requires a server (Node.js), higher server cost/latency.

Hydration

Hydration is the process of making server-rendered HTML interactive in the browser.

Full Hydration: The entire app becomes interactive at once.
Incremental Hydration: (Advanced) Parts become interactive as needed using @defer blocks.
Event Replay: Captures and replays user events that happened before hydration finished.

Decision Matrix

Requirement	Strategy
SEO + Static Content	SSG
SEO + Dynamic Content	SSR
No SEO + High Interactivity	CSR
Mixed	Hybrid (Route-based)

1.8 KiB Raw Blame History