Template-based file and project creation lacks flexible inputs
People who create files or projects from reusable templates run into separate friction points: Obsidian users must create a file and insert its template in separate steps, while Nix users want generated projects to reflect their inputs. Requests about templated folder paths and customizable Nunjucks includes point to related gaps in configuring where files go and how shared content is reused. A flexible generator could address much of this, though the image-remaking signal is a separate need.
For developers and Obsidian users who generate files from templates. Mentioned from Oct 2015 to Oct 2025 on Bluesky, product forums and GitHub.
5 different people described this problem in 5 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 4.8/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
the generated project is fixed, and cannot depend on any configuration variable specified by the user. I'd love to be able to be able to specify some variables, like the name of the project, the description of the project, the licence of the project...
Currently you need to create your file manually and then apply correct template separately using Templates: Insert template
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks