Task guides

These guides extend one task-board application. They explain implementation boundaries rather than presenting isolated snippets.

Start with server-rendered HTML

Do not start with an SPA. Keep the model, rules, URLs, and rendering together on the server. Send useful HTML first, then add AngularTS to the smallest region that needs browser behavior.

Even when using the router, prefer server-rendered route fragments. Move the model into the browser only for the most complex client-owned features. When the browser takes over model consistency and compilation, use typed programmatic views as the primary view style. REST services, explicit caching, and a browser-facing security policy also become primary at that same threshold. Until then, prefer normal HTTP pages, forms, and server-rendered fragments.

Apply this decision per module. A server-rendered login and public site can live beside a dashboard SPA in the same application. The dashboard’s complexity does not require every other module to move into the browser.

Read Keep the application on the server before choosing the application structure.

Build the application

1. Keep the application on the server
2. Structure the application
3. Build and validate a form
4. Load server data
5. Add routing
6. Handle errors
7. Test behavior

Make it production-ready

• Browser support
• Accessibility
• Internationalization
• Application security
• Observability
• Production and deployment
• Troubleshooting

Start with the complete tutorial if you have not built an AngularTS component.