Refactor `render-engine init` to use internal code and templates and deprecate the `cookiecutter`.

Open
  • Is something wrong?
#45 4 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@tystar86 is already working on this.

Since Oct 27, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cli

Research direction

Start by reading the existing render-engine init implementation and its cookiecutter dependency, then identify how this repository packages templates. Build the site from maintained Jinja2 templates and code; done means the generated site runs as a Render Engine site and includes a basic index.html congratulating the user.

Written by the indexing model from the issue text.

Description

Djangonauts

The current implementation of render-engine init uses cookiecutter which means that any changes we want to make need to be done in multiple places. We should update render-engine init to build the site from Jinja2 templates and code maintained as part of this repository. The output of running render-engine init should be a fully operational Render Engine site with a basic index.html that congratulates the user on setting up their site.

Dominant language
Python
Stars
4
Forks
8
Avg merge
21h 34m
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from render-engine/render-engine-cli

All issues in render-engine/render-engine-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.