AvocadoStackTechnologies
The tool follows the job.
The stack is named in the scope, before the build. These are the tools AvocadoStack ships with. Each one has a service page for who it is for, what is included, and what is left out.
- You edit the wordsWordPress
- A product front, or a site that should stay fastNext.js
- Accounts, roles, and rulesDjango
- A login, a workflow, and more than one roleA workflow web app
- It has to live on a phoneiOS and Android
- The systems already existAn API integration
Workflow web apps
Internal tools and customer logins, in Django or Next.js, that replace a spreadsheet or an inbox.
Mobile applications
One product for the App Store and Google Play, unless one platform has a reason to differ.
WordPress
Company sites, shops, and rebuilds, on a theme and fields your team can edit.
Django
Back offices, portals, and B2B workflows, with permissions and an admin.
Next.js
Product interfaces and fast content sites, including the front of a Django API.
API integrations
One documented path between two systems that already exist, such as a payment into a CRM.
Questions about the stack
Next.js, as it ships
This website is on the same stack. A client project gets the same care about what is static, what is dynamic, and who edits the words.
export default async function ProjectsPage() { const projects = await listProjects() return ( <Board projects={projects} empty="Nothing in flight yet." /> )}