Resource hub
Resources for reviewing Laravel work faster.
Project brief, structured portfolio data, resume files, feeds, and machine-readable indexes for evaluating the portfolio without digging through every page.
- Planning files for project discovery.
- Structured JSON for portfolio and resume review.
- Search, feed, sitemap, and contact assets.
Files
Direct resource links.
Use these files for procurement review, technical discovery, search indexing, or simple sharing.
- Laravel project briefMarkdown brief for describing goals, risks, constraints, and delivery expectations.
- Portfolio JSONMachine-readable project and capability summary.
- Resume JSONStructured senior Laravel developer resume data.
- Search indexCanonical search data for the public portfolio pages.
- LLM summaryShort site summary for AI search and assistant indexing.
- RSS feedProduction Laravel writing in feed format.
- XML sitemap indexRoot sitemap index advertised in robots.txt and linked from every page head.
- Page sitemap XMLCanonical static page URLs for services, portfolio pages, policies, and resources.
- Blog sitemap XMLComplete article URL inventory for the Laravel and PHP archive.
- News sitemapRecent article feed for Google News and Search Console news tracking.
- OpenSearch XMLSearch provider description for browser and site-search discovery.
- Browser tile XMLTile configuration for browser and device surfaces.
- vCard contactContact card for email clients and address books.
Usage
How these resources fit together.
The Markdown brief is the fastest starting point for a project conversation because it captures goals, constraints, risks, and delivery expectations. The JSON files are better for structured review, internal notes, or systems that need to parse portfolio and resume details.
The sitemap, feed, search index, and LLM summary support discovery and indexing. They also make it easier to verify that public pages, blog posts, contact assets, and machine-readable files stay aligned after content changes.