- blog_comments table + Comment model/factory; comments attach to the post,
public list shows approved rows only, public submission starts unapproved
- Admin moderation API: list/filter, approve, delete comments
- Public POST posts/{slug}/view and posts/{slug}/like toggle counters
- Route groups: comments throttled like the contact form, interactions at
60/min; comments resource exposed to the generic admin list
- Six new topic pairs (EN+FA): TypeScript advanced patterns, SQL indexes,
Git branching/reviews, TDD, clean architecture in Laravel, browser page load
- Every existing post gains Key takeaways + FAQ sections in both languages
- New engineering-practices category pair and database/git/testing tag pairs
- Single-post API now returns same-language previous_post/next_post links
Persian covers are percent-encoded into og-image URLs and several long Persian titles produced URLs over 255 chars, failing the prod seeder with a data-too-long error. Shorten Persian cover text so every featured_image fits the column; guard with a seeder test asserting all 24 images are non-empty and under 256 chars.
- Add FilterableByLanguage scope (posts/categories/tags) keyed off the -fa slug convention; every public blog list endpoint honors ?lang=fa|en, feeds/sitemaps keep all languages when omitted
- Homepage (latest/most-viewed/random posts + categories) filters per language; post detail shows same-language related posts only
- Reseed content to a strict English/Persian mirror: 6 existing international topics + 6 new Iran-market topics (technical SEO for Persian sites, Iranian dev freelancing, AI & Iranian dev careers, web design for Iranian businesses, React job market in Iran, WordPress-to-Next migration), 12 posts per language, zero posts in only one language
- Fix 2 legacy FA slugs to follow the EN-slug + -fa convention so twin redirects and mirror assertions hold
- Update seeder test to assert balanced languages, full twin coverage and same-language related posts; add lang-filter coverage
Contact form messages were sent via mailto and the site has no mail
service, so visitors saw a placeholder caveat instead of a working
channel. Add a contact_messages table, a public throttled POST endpoint,
and admin list/mark/delete endpoints, then wire them into the panel.
Replace the faker-generated blog demonstration content with real
English and Persian SEO-oriented articles via RealBlogContentSeeder
(deterministic, bilingual posts with per-language categories and tags,
and cross-linked related posts).
Two things the image upload feature needs at runtime were missing.
public/storage is gitignored, so it never reaches the build context, and
nothing in the image created it. Storage::url() returns .../storage/media/x.jpg,
so nginx 404s every file the admin uploaded even though the upload succeeded
and the URL was stored in the record. storage:link at build time fixes it;
the ln fallback covers artisan refusing to boot without APP_KEY.
PHP's own ceiling was the other half. StoreMediaRequest accepts 4 MB but
upload_max_filesize defaults to 2M, so larger files are discarded before
Laravel validates them and the admin just sees a 422 for a valid image.
Next's Server Action limit was already raised to 8 MB, so 8M keeps the
whole chain consistent. post_max_size must sit above upload_max_filesize
or the extra form fields are dropped along with $_FILES.
The ini directory is resolved at build time rather than hardcoded, and the
effective values are asserted so a silently mislocated ini fails the build.
These three had read endpoints or nothing at all, so their content could only
be changed by hand in the database. All writes are admin-only and rate
limited like the existing admin routes.
Testimonials are the awkward one: the migration that collapsed the legacy
per-locale tables into JSON columns deliberately skipped them, so they still
live in a child table. Testimonial therefore exposes a translations accessor
to present the same translations[key][locale] shape as Service and Skill,
which is what the generic resource form binds to. Reading the child relation
has to go through getRelation(), since a plain $this->translations inside an
accessor of that name re-enters the accessor and silently yields nulls.
The store requests now mark the NOT NULL columns as required. Leaving them
nullable let a bad payload reach the database and come back as a 500 instead
of a 422, and about_me_id is additionally a cascading foreign key.
Also registers the three resources with the admin read endpoint so the panel
can list them, eager loading the relations their forms need.
Posts, projects and about-me all carry an image column that could only ever
be filled by typing a URL by hand, so every featured image in the database is
still a placeholder. Uploads are the missing half of content management.
Filenames are generated rather than reused from the client, which is what
keeps a double extension or a path traversal out of a web-served directory.
The upload surface is restricted to raster formats (no SVG, which can carry
script) with a size and dimension ceiling, and throttled at 12/min against
the general admin API's 30/min because an upload costs far more than a JSON
write.
Routes move to per-feature files registered from bootstrap/app.php, since
api.php had become a chokepoint for parallel work on this repo.
Edit forms are populated from a single request, so posts need their tags and
projects their category attached; otherwise the tag multi-select and category
picker come back empty.
Two gaps blocked building the admin panel:
About-me writes could only set the image. Title and description live in the
JSON translations column and were unreachable from the API, so the homepage
bio could never be edited through the app. Accept title_fa/title_en/
description_fa/description_en on both About Me form requests and write them
per locale through setTranslation().
Editing also needs raw rows. The public project and about-me endpoints only
return display-oriented payloads - one translated title, reshaped image
arrays, no second locale - which is not enough to populate a form. Add
GET /api/admin/resources/{resource} behind the same auth:sanctum + admin
middleware as the write routes, returning stored rows including every locale,
plus a public GET /api/website/project-categories so project forms have a
category picker.
Covered by AdminResourceReadTest: anonymous and non-admin callers are
rejected for every resource, unknown resource names 404, and project rows
expose both locales.