Apyara's website, from prototype to working platform
A concise account of the website work completed and the next items in the project queue.
Apyara's website, from prototype to working platform
As of 3 November 2026, the project tracker records 12 completed work items and 9 open follow-ups. The original launch plan is complete, as recorded in the migration roadmap.
At a glance
On 15 October, Apyara had a static website. It could show the brand and content, but staff had no editing system, inquiries were only a local preview, and releases had no automated checks.
The production site now serves English and Brazilian Portuguese. Authorized staff can edit site content, the inquiry form stores submissions in a protected database and notifies the team, and the previous deployment remains available for rollback. Production routes, signed-in editing, and the latest automated release checks were verified before the launch plan closed.
How the site came together
| Stage | What changed |
|---|---|
| Plan the work | Hosting, language links, staff access, privacy, and data handling were decided before the rebuild. See the architecture and privacy decisions. |
| Build the foundation | The new application checks how pages and their content fit together before release, so some errors stop a deployment before visitors see them. The team added a private editing system and database, then moved the home page, supporting page details, five services, three clearly labeled editorial concepts, and seven media assets into it. See the application foundation, database setup, editing system, and content migration. |
| Rebuild the visitor experience | The responsive site kept Apyara's visual identity and custom river animation. Automated checks cover how it adjusts to image cropping, screen sizes, and visitor settings for less motion. The team added private inquiry handling and an approved privacy notice. Release checks cover language switching, draft protection, form behavior, accessibility, and database changes. See the site rebuild, river animation, inquiry handling, release checks, and privacy approval. |
| Release to production | The new site replaced the static version after production routes and content were checked. The previous deployment remains a rollback option. See the production release. |
What remains
The nine open items define the next round of work. Two address the editing team's preview workflow. The rest add content, language, or ways to find information.
- Editor workflow. Set up a separate sign-in for the non-production site and fix the reported draft-preview error. See Preview account setup and draft preview repair.
- Apyara's story and articles. Build an About page after the founder confirms the organization's story, the preferred public spelling of names, team bios, and profile links. Add a bilingual blog where editors can compose articles with varied layouts and search article text. See the About page and blog.
- Spanish and language choice. Add Spanish translations as drafts for a person to review before publication. Expand the language selector so visitors can choose a language, follow their browser preference, and keep their choice for later visits. See Spanish translation and language selection.
- Finding content and managing links. Add public search for published services and insights, connect page titles and descriptions to search and sharing previews, and let authorized staff manage redirects when links change. Services and insights currently open within the home page rather than on their own pages, so the metadata work will not create separate pages for them. See public search, search and sharing metadata, and staff-managed redirects.
Current operating detail
Authorized staff can review and delete inquiry records. The site does not delete them automatically, so staff manage deletion manually. Database backup and recovery are handled by Apyara's infrastructure owner outside this website project.