Michilis/Spanglish
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity
26 Commits 5 Branches 2 Tags
95ee5a5dec797df6fc1a159e9bd445832516b744
Commit Graph

4 Commits

Author SHA1 Message Date
Michilis
95ee5a5dec Improve llms.txt for AI: metadata, ISO dates, explicit status, structured events, update policy, AI summary; fix social links 
Co-authored-by: Cursor <cursoragent@cursor.com>
 2026-02-12 07:12:51 +00:00
Michilis
77e92e5d96 Fix llms.txt event times: format in America/Asuncion timezone 
Co-authored-by: Cursor <cursoragent@cursor.com>
 2026-02-12 05:17:47 +00:00
Michilis
07ba357194 feat: FAQ management from admin, public /faq, homepage section, llms.txt 
- Backend: faq_questions table (schema + migration), CRUD + reorder API, Swagger docs
- Admin: FAQ page with create/edit, enable/disable, show on homepage, drag reorder
- Public /faq page fetches enabled FAQs from API; layout builds dynamic JSON-LD
- Homepage: FAQ section under Stay updated (homepage-enabled only) with See full FAQ link
- llms.txt: FAQ section uses homepage FAQs from API
- i18n: home.faq title/seeFull, admin FAQ nav

Co-authored-by: Cursor <cursoragent@cursor.com>
 2026-02-12 04:49:16 +00:00
Michilis
5885044369 Make next event visible to AI crawlers (SSR, JSON-LD, meta, llms.txt) 
- SSR next event on homepage; pass initialEvent from server to avoid client-only content
- Add schema.org Event JSON-LD on homepage when next event exists
- Dynamic homepage metadata (description, OG, Twitter) with next event date
- Add dynamic /llms.txt route for AI-friendly plain-text event info
- Revalidation: support next-event tag; backend revalidates sitemap + next-event on event CUD
- Allow /llms.txt in robots.txt

Co-authored-by: Cursor <cursoragent@cursor.com>
 2026-02-12 04:10:49 +00:00