Datachieve Web Development Workflow
- 1
Onboarding
- Contract is signed
- Down payment received
- Questionnaire sent to client
- Initial kickoff meeting scheduled
- Teams: admin
- 2
Discovery
- Questionnaire completed
- Kickoff meeting held with client
- Project scheduled
- Teams: admin, design, development
Planning
- Team reviews project requirements
- Project brief developed
- Sitemap and site structure outlined
- Teams: admin, design, development
Site Accounts & Forms (Access & Testing)
- Google Analytics identified (setup or access gained)
- Gain access to client’s DNS and create a test record
- Form recipients identified
- If applicable, set up social media accounts and integrations
- Teams: admin, development
- 3
Wireframing
- Wireframes of the site structure and navigation developed
- Teams: design
Design
- Figma & Static concepts developed
- Teams: design
Development #1
- Choose server (e.g., Dedicated or Shared)
- Set up hosting, GIT, etc.
- Visualize data distribution
- Prototype special functionality
- Establish CRUD patterns (Create, Read, Update, Delete) - Read More
- Target accessibility compliance tier
- Identify Google APIs
- Teams: development
- 4
Presentation
- Figma and static design concepts presented
- Once approved, invoice for second payment is sent
- Teams: admin, design
Development #1 Cont.
- Continued...
- Teams: development
- 5
Design Modifications
- Modifications are made and resubmitted (both static and Figma)
- Teams: design
Development #1 Cont.
- Continued...
- Teams: development
- 6
Development #2
- Review design and identify components (small to large)
- Set up milestones and issues in GIT (and assign)
- Gauge time and identify potential delays
- Build upon foundation
- Conduct reviews of GIT issues throughout development; ensure accessibility compliance throughout
- All our current go-live development processes should run in parallel to GIT Issues and Milestones; Accessibility, Resonsive Design etc.
- Teams: design, development
Content
- Site content received from client in digital format or exported from existing site
- Content is implimented into site as development progresses
- Redirects identified and implemented as content is added
- Teams: design
- 7
Client Review
- Client presented with a working site for review
- Final payment due before going live
- Teams: admin, design
Create Users
- Identify who needs access and set up WP accounts for GoLive
- Teams: design
Site Accounts & Forms (Integration)
- Google Analytics configured
- Form recipients are added to all forms updated
- Social media accounts connected to development site
- Teams: design, development
- 8
Changes / Modifications
- Based on client feedback, changes and modifications are made to the site
- Teams: design, development
- 9
Schedule GoLive
- Schedule a GoLive date with the client
- Teams: admin, development
PreFlight
- Double-check all development processes, account setups, and integrations
- Teams: admin, design, development
- 10
GoLive
- Update DNS
- If applicable, set up Zaps (requires live URL)
- If DNS is managed via Cloudflare, configure rules
- Send to team for site check after propagation
- Teams: development
Setup Client Training
- Reach out to client to schedule training
- Teams: admin, design
- 11
Training
- Train clients on how to use their new website
- Teams: design, development
Client Follow-up 1
- Check in with the client to ensure everything is running smoothly after GoLive
- Teams: admin
- 12
Client Follow-up 2
- Follow up with the client after 30 days to ensure they’re satisfied and address any questions or concerns
- Teams: admin