I’ve been thinking about Projects in Hammer.
In the new Hammer, I’ve added Projects as a very simple container for sites. At the most basic level, it makes using Hammer to build more sites manageable.
I already have many projects and multiple sites per project, so naturally I’m thinking about the gaps and unmet needs that projects could unlock.
Thought I’d start a topic thread to open that brainstorm up to the community.
A few things I’ve been thinking about are:
project level assets
These might be images, fonts, colours etc that are common to all sites in the project, short of a full design system or component library but a utility that can be easily used to bootstrap a new site with derived boilerplate and commonly used assets.
shared context
Particularly useful when using AI IDEs like cursor, the project context can be injected into sites directories with custom cursor rules that maintain long term persistent memory and context during development. This could be text based and also visual, like screenshots from forge canvas, a Miro board or Figma.
project dashboard
Simple metrics across sites in a project, such as todos, accessibility, performance, SEO readiness reports etc., usage analytics (could pull from forge api if sites are mapped to and deployed to forge)
Thoughts?