What is preventing you to invest in the Capitains Python environment and what could we do about it ?

[PonteIneptique]

It's been few years Capitains Python environment has been available (MyCapytain, Nautilus, Nemo and HookTest). Unfortunately, I see that this software base, which I believe is interesting, is not getting as much love as I'd like it to get.

Maybe, maybe, it's not matching needs (in this case, there's not much to do) but I feel like it interests some people which in the end to not invest in this code base which I absolutely want to be shared and for which I hope that a community can grow for.

This is why I want to start this discussion. Please feel free to discuss what improvement do you feel Capitains need so that you would use it in outreach or research projects (and even in teaching !).

Current ideas for outreach

• Finally write an article for the Digital Classicist wiki...

Improvement

• Write a tutorial to replace old youtube videos for Nemo + Nautilus Draft
• ?

General questions

• ?

[redmer]

I'm exploring it, coz it’s just what I need. I want to start exploring the software with the Docker Image, but it’s tutorial appears outdated. I can load custom epigraphic texts, but I can’t figure out how to load custom templates, or custom CSS.

This stops me exploring the rest of the Capitains software.

An other problem with Nemo is that it does not specify a license (preferably MIT as MyCapytains).

[PonteIneptique]

Hey @redmer , thank you for the answer. So your main issue is with configuration of Nemo if I understand right ? Then I shall write a new tutorial (or do you prefer video ?)

As for the license, I will add it to Nemo and other softwares. Thank for the notification on this !

[redmer]

Wonderful and what a great response time 😄 I actually prefer a written tutorial. Those are also easier to update I suppose.

[PonteIneptique]

This is the marvel of being in the same time zone.
Until then, if you want some examples, there are some out there. A template of app is there ( https://github.com/OpenGreekAndLatin/leipzig_cts/blob/master/modules/capitains/templates/app.py.erb ) but a more simple configuration is here ( https://github.com/OpenGreekAndLatin/cts_leipzig_ui/blob/master/run.py )

[PonteIneptique]

Note that I started to write a tutorial. Feel free to propose corrections or raise issues in terms of contents you want to see me approach https://github.com/Capitains/tutorial-nemo

[emchateau]

I think you could think about what some calls "personas" in design or marketing. It would be nice to have a kind of FAQ centered towards users :

• You are editing a TEI corpus, why would you need Capitains ?
• I’m not editing classicals text, How Capitains is still relevant for me ? What should I do to make it works for me ?
• etc.

[PonteIneptique]

Thanks @emchateau for this feedback. Specifically the part on classicist. There is something along these line on the website homepage : http://capitains.org/ , do you think we could improve this ?

[PonteIneptique]

I just created another tool that might help you get in the Capitains World, much more quickly than the tutorial : the Nemo Template App which aims at reducing the time you need to start a Nemo website. Demo of the repository here https://nemo-template-app-demo-prod.herokuapp.com