Thanks for the explanations. Let me clarify: I'm suggesting something very compatible with your concerns (in fact, stemming from the same concerns). The exact content of the users_table block would just be moved into a new "control_panel/users_table.html" template (no style/script etc needed in there, just exactly that chunk of HTML), and then both current_users.html and group_users_management.html would include (wherever they want that HTML to show up):
`{% include "control_panel/users_table.html" %}`.
(very much like a PHP include, which just isn't needed as often in Django given the template inheritance, but this is a good use case for it)

To use your function metaphor, what I'm suggesting is directly like a function, whereas include_block is more like pulling a method out of a class and using it like a separate function elsewhere.

Does that make sense? Happy to hash this out in person sometime if that's helpful. This doesn't need fixing before this is merged, so I created issue #280 referencing this discussion, so we can resolve it later.