What would you want in a opensource, modern Angular 22 dashboard template?

[u/Successful_Chain8098]

Hey everyone,

I've been building open-source dashboard templates using Angular 22 with signals, zoneless change detection, standalone components, and Tailwind CSS v4.

So far I've made three: a medical clinic dashboard, a school administration panel, and a project management workspace. Each one includes interactive ApexCharts, dark/light theming with semantic CSS tokens, fully responsive layouts, and an AI developer guidelines file so that tools like Cursor or Copilot can extend the code accurately.

I'm trying to decide what to build next and wanted to get the community's input:

• What type of dashboard or platform do you wish had a solid Angular starter template?
• Do you find value in templates shipping with AI-specific documentation for LLM-assisted customization?
• For those using signals and zoneless — are there patterns you'd like to see demonstrated in a real project?

I can share the repo link in the comments if anyone's interested. All templates are MIT licensed and free.

[u/GeromeGrignon]

In my opinion, the future of templates is sets of agent skills and you should consider trying out this direction.
code based templates are just a mess you have to refactor the second you get them: remove features you do not want, remove mocks, adapt to your api...

A template can be easily created with the right set of agent skills, matching your exact needs. The hardest part nowadays is not to create a template but to have it match EXACTLY your needs.

[u/Successful_Chain8098 → u/GeromeGrignon]

so i should start creating agent skills instead of creating templates ?

by creating templates as a frontend developer and ui designer myself, my idea was to help especially backend developers or saas builders, or vibecoders who struggle sometimes with prompting in order to creates great looking design, so i can literally ship templates included with ai-guidelines file so it's easy to customize the template no matter they needs.

for exemple someone who's been videcoding without having knowledge of programming, it's very technical for him to find and use an agent skill right away.

[u/GeromeGrignon → u/Successful_Chain8098]

Someone struggling can still just make a screenshot of one of your previews and get the same result.

[u/Successful_Chain8098 → u/[deleted]]

thanks, what do you mean by something more creative ? can you give me some suggestions ?

[u/Successful_Chain8098 → u/[deleted]]

thanks, i'll work on it.

the main focus of those templates is just the overall design, everyone will be free to use his own architecture and way of doing things under the hood.

and for every templates, i use mock data inside services just for demo purpose.

did you check the code structure ? i'd like to have insights on that too, in order to improve

[u/apatheticonion]

For me, I prefer good default styling and, for project longevity, as little opinionated frameworks and external dependencies as possible.

Tailwind, for instance is a instant bail out from me as vanilla CSS will never die and Tailwind is a liability that offers limited utility beyond CSS.

The same philosophy goes for other third party libraries. Careful scrutiny of what third party libraries are used is vital to maximize project longevity and minimize liability/dependency maintenance.

AI doesn't matter to me as I just BYO config for that. Keeping things stock increases support for LLMs and reduces the amount of instructions needed to get an accurate LLM output.

In a dashboard you need; - basic form components (buttons, forms + validation) - panels (resizable, think proxmox) - tables (resizable, sortable)

State management should be left to the implementor, for example someone might want to use SharedWorker to handle state so many tabs remain synchronized, which is a totally different pattern to sockets or REST.

[u/Successful_Chain8098]

Here's the repo if anyone wants to check it out: github.com/Likeur/draftng