02:10 <xet7> ocdtrekkie: For Sandstorm? What features it should have?

02:11 <ocdtrekkie> Probably the only thing I really want is the seamless user integration and notifications of ticket status to go out to technicians and requestors by email.

02:11 <ocdtrekkie> I don't need anything super sophisticated, but it'd be really nice to have a basic app for it.

02:15 <xet7> Well, there is kind of similar planned for Wekan, but I presume scheduled tasks etc maybe would need to run in Sandstorm cron kind of system

02:16 <xet7> Reveiving email to card, grouping notification emails, replying to card from card or email

02:17 <ocdtrekkie> I think I could probably build a poor man's help desk out of Wekan, but I think the UI I'd expect would be different.

02:18 <xet7> What kind of UI it should have?

02:18 <ocdtrekkie> So, blatantly put, 98% of users who file help desk tickets are stupid. Less blatantly, they are not particularly computer literate.

02:19 <xet7> Well, then maybe adding form designer to Wekan?

02:19 <ocdtrekkie> So a good help desk system needs to be as bare bones as humanly possible to all users except the technicians/support people.

02:21 <ocdtrekkie> Should have only two areas: One to file a ticket, which shouldn't have more than a basic category option, a text box to explain, the ability to attach a photo, and nothing much else (a CC field is nice too). And one to see the existing tickets that user has filed where they can see comments and status changes.

02:21 <ocdtrekkie> Anything more sophisticated than that and you start having an annoying ticket system where people avoid using it and just call you.

02:22 <xet7> Can you make some screenshot mockups?

02:22 <xet7> and description about how it should work

02:23 <ocdtrekkie> Honestly I could probably give you a modified screenshot of my ticket system at work, it's close to the minimalism I expect, though it has hairy parts.

02:24 <xet7> Thanks! You can send those to support@wekan.team

02:24 <ocdtrekkie> But like, to use Wekan as a ticket system, you'd probably need an entirely separate UI to be presented to users, and then the Wekan UI would just be for technicians.

02:25 <xet7> Yes there can be separate UI

02:25 <xet7> Being inside Wekan, or outside as one of my bare bones small prototypes

02:27 <xet7> I have been doing small prototypes with many different programming languages

02:27 <xet7> Trying to design smaller faster Wekan

02:29 <xet7> For example, it's so much faster to add features to my Wekan PHP prototype https://github.com/wekan/php/blob/main/public/index.php than to current huge Meteor Wekan

02:31 <xet7> Order system could be for example PHP/SQLite grain app at Sandstorm

02:31 <xet7> Or maybe C++ ;)

02:33 <ocdtrekkie> I don't think anyone should intentionally write a web app in C++ without very good reason.

02:34 <xet7> Well, C++ came to mind because of this https://github.com/sandstorm-io/sandstorm-rawapi-example

02:35 <xet7> But that's too much optimization for small app

02:41 <xet7> Is this Node.js based WordPress https://github.com/Automattic/wp-calypso only WordPress.com specific UI, or is it whole complete WordPress implemented only with Node.js? Not PHP at all?