Hello. Thanks for your contribution.

I added this to the wiki earlier today: https://wiki.roundup-tracker.org/TrackerTemplates.

Usually an email is sent when a new issue is created. For this issue it's 460k while the
limit is 40k. So I am going to cancel the email.

Can you announce your template  on the roundup-users mailing list (roundup-
users@lists.sourceforge.net)? You can reference this issue: https://issues.roundup-
tracker.org/issue2551308 in your announcement for those who want to see the screenshots.

The templates could definitely use a refresh. As you noted the bootstrap is 10 years old and 
hasn't had a maintainer in most of that time. However there have been some updates
(bootstrap 4, jquery update).

The TAL based templates are in some cases over 20 years old and look it.

Just out of curiosity why did you switch from SimpleMDE to EasyMDE? Also which markdown 
renderer (markdown, markdown2, mistune) are you using with your tracker?

Being easy to reconfigure/change is one of the hallmarks of Roundup. I have to admit
I am totally stumped on how to autofocus the username field in the login dropdown. Using
google to try to resolve this issue didn't turn anything workable up after 45 minutes other 
than determining that adding "autofocus" was not expected to work 8-).

How the dropdown magically gets opened by clicking on the link (shouldn't it be a button
not a link for a11y even with the aria-role?) is confusing to me. Ideally changes should
be able to be made without requiring a high end web developer well versed in a framework.

However we only really provide info on modifying the TAL templates. We really need something 
similar for jinja2 (and whichever framework is used). Having somebody to answer questions
from users would be good as well.

Thanks for opening the issue. Let's see if people agree it can replace the existing jinja2
template (which I think is using the developer schema??). Then we can either add it to the
distributed trackers or replace the existing bootstrap based template. Also we can work out
how to handle maintenance and migrations/upgrades across releases.