00:00:03.680 --> 00:00:06.000 Started time to repeat everything you just said.
00:00:07.360 --> 00:00:13.000 So I was just saying OK, network got back up.
00:00:14.280 --> 00:00:18.200 So we have the basic Phil specs, one that's just MD book.
00:00:18.520 --> 00:00:22.446 You can search, full table of contents, all that publicly
00:00:22.446 --> 00:00:22.920 hosted.
00:00:23.440 --> 00:00:26.813 We can restrict it by like a simple HTTP basic username and
00:00:26.813 --> 00:00:27.320 password.
00:00:27.640 --> 00:00:28.440 All that stuff.
00:00:29.820 --> 00:00:31.380 Here's what the book looks like.
00:00:31.380 --> 00:00:32.620 It's just normal with Markdown.
00:00:33.300 --> 00:00:36.420 Right now, Commento has to be added manually to every page.
00:00:36.540 --> 00:00:39.040 However, we can probably make something that automatically
00:00:39.040 --> 00:00:40.100 adds to every page later.
00:00:43.660 --> 00:00:47.084 The book that looked at Tumble itself just defines like basic
00:00:47.084 --> 00:00:50.343 stuff about the book, like what's the title, who wrote it,
00:00:50.343 --> 00:00:51.780 and then the preprocessor.
00:00:51.780 --> 00:00:54.432 So this thing lets us do file names and directory structure to
00:00:54.432 --> 00:00:56.957 automatically generate the summary, which is basically just
00:00:56.957 --> 00:00:59.610 the table of contents that reads to make this thing over here.
00:01:02.130 --> 00:01:05.311 Mermaid charts, obviously, and then this is the preprocessor
00:01:05.311 --> 00:01:07.450 that will eventually add that in for us.
00:01:08.610 --> 00:01:11.506 Preprocessors are stupidly simple, they're just programs
00:01:11.506 --> 00:01:12.370 that it executes.
00:01:12.410 --> 00:01:16.318 It gets an array of two JSON objects, forget exactly what
00:01:16.318 --> 00:01:20.563 each one was, but basically they were just a representation of
00:01:20.563 --> 00:01:21.170 the book.
00:01:21.660 --> 00:01:24.760 And then it just has to output the second JSON object of that
00:01:24.760 --> 00:01:27.060 array with whatever changes it wants to make.
00:01:28.020 --> 00:01:30.060 So yeah, stupid simple.
00:01:31.420 --> 00:01:40.224 I actually wrote another one which I can show real quick
00:01:40.224 --> 00:01:41.460 silence.
00:01:51.750 --> 00:01:52.710 So for example this guy.
00:01:53.310 --> 00:01:57.692 This will automatically replace all triple net colons with
00:01:57.692 --> 00:01:59.030 triple back ticks.
00:01:59.550 --> 00:02:02.632 That way like mermaid charts work in both Azure and MD books
00:02:02.632 --> 00:02:03.390 simultaneously.
00:02:06.310 --> 00:02:06.670 Forget where.
00:02:06.670 --> 00:02:26.010 The other thing is that I'm looking for one second courses.
00:02:28.370 --> 00:02:29.810 I think it was P 21.
00:02:41.870 --> 00:02:42.310 Yeah, here we are.
00:02:42.950 --> 00:02:46.851 So then here's another example where I turn just like any text
00:02:46.851 --> 00:02:48.710 that's just bang, custom bang.
00:02:49.270 --> 00:02:53.532 So this would be for the sales input documents into a full span
00:02:53.532 --> 00:02:57.928 that just brings in the material icon for I forget exactly what I
00:02:57.928 --> 00:03:02.191 use for this one, but then for risk, it's like that I think was
00:03:02.191 --> 00:03:03.989 the triangle! Warning sign.
00:03:06.070 --> 00:03:09.294 So basically we like we can trivially add our own little
00:03:09.294 --> 00:03:11.670 extensions to Markdown and it just works.
00:03:16.470 --> 00:03:18.830 So yeah, that's basically preprocessors work in there.
00:03:19.840 --> 00:03:23.040 As for hosting this, this is on our new host three, which I
00:03:23.040 --> 00:03:24.480 guess Austin you never saw.
00:03:24.480 --> 00:03:27.400 Let me just get into there.
00:03:31.560 --> 00:03:35.547 So right now it's stupidly simple, just one little folder
00:03:35.547 --> 00:03:39.809 that hosts the built output of the book and then there's just
00:03:39.809 --> 00:03:44.002 just engine X rule that point set and folders to serve it as
00:03:44.002 --> 00:03:45.240 just static stuff.
00:03:47.560 --> 00:03:49.280 Alongside of that is Commento.
00:03:53.100 --> 00:03:54.860 So right now I just have that running docker on here.
00:03:55.540 --> 00:04:00.759 Basically Commento allows you to add comments to just perfectly
00:04:00.759 --> 00:04:01.820 static pages.
00:04:02.860 --> 00:04:05.740 There is also a paid hosted version.
00:04:05.980 --> 00:04:08.782 However in this one I just went ahead and self hosted it just
00:04:08.782 --> 00:04:09.460 for simplicity.
00:04:11.620 --> 00:04:15.286 So basically all we all we got to do at the moments to get a
00:04:15.286 --> 00:04:19.073 new one of these things spun up is you're just make the actual
00:04:19.073 --> 00:04:22.980 Mdbuck itself, Which mdbuck has a command for a scaffolding one.
00:04:24.740 --> 00:04:28.694 And then yeah, just build it, plop it up here, edit the
00:04:28.694 --> 00:04:33.072 engineer's conflict file, tell commando about the new domain,
00:04:33.072 --> 00:04:37.380 and just give the client their credentials to go look at it.
00:04:38.020 --> 00:04:44.429 So the idea here in the end is that we would be able to host
00:04:44.429 --> 00:04:45.060 first.
00:04:45.060 --> 00:04:48.403 Jeremy is looking for a connector documentation like
00:04:48.403 --> 00:04:52.314 this just going to be like we can just give their or give our
00:04:52.314 --> 00:04:55.972 clients access to the connector documentation probably in
00:04:55.972 --> 00:04:59.946 particular the sales info docs and they can yeah, just go read
00:04:59.946 --> 00:05:00.830 it themselves.
00:05:01.870 --> 00:05:03.390 It's always up to dates etcetera.
00:05:03.870 --> 00:05:06.717 And then I'm hoping for a longer term is that we can also get
00:05:06.717 --> 00:05:07.590 Fsc's back in here.
00:05:08.070 --> 00:05:12.183 So rather than some weird mirror board, we just have, or I should
00:05:12.183 --> 00:05:15.860 say mirror board, or endless iterations of docx files that
00:05:15.860 --> 00:05:19.599 nobody knows who which one is the most recent, we just have
00:05:19.599 --> 00:05:20.409 one of these.
00:05:21.530 --> 00:05:23.930 We get it set to update through CICD.
00:05:24.810 --> 00:05:28.109 So you just push an update of the MD book to a git repository
00:05:28.109 --> 00:05:30.610 and it just automatically deploys it up there.
00:05:33.370 --> 00:05:36.226 So clients always knows exactly where to go to see their current
00:05:36.226 --> 00:05:36.490 specs.
00:05:36.490 --> 00:05:38.985 They can leave comments on it without just, you know, changing
00:05:38.985 --> 00:05:40.570 the world without us be able to see it.
00:05:42.970 --> 00:05:48.865 And yeah, that's about the log of it really about my only
00:05:48.865 --> 00:05:54.658 request for sharing the client specific docs with or not
00:05:54.658 --> 00:05:55.370 client.
00:05:55.610 --> 00:05:59.144 The connector docs with clients would be some way for us to mark
00:05:59.144 --> 00:06:00.450 stuff as developer only.
00:06:01.330 --> 00:06:04.330 Yep, that should be pretty simple.
00:06:05.250 --> 00:06:09.870 I'm pretty sure we can just like have a little tag that we put on
00:06:09.870 --> 00:06:14.420 top of a page and then in one of those preprocessors we can just
00:06:14.420 --> 00:06:18.620 strip it out based on some environment variable that we set
00:06:18.620 --> 00:06:21.000 before running the MD book build.
00:06:21.480 --> 00:06:25.875 So like the CICD would build two or two versions of it, one just
00:06:25.875 --> 00:06:29.730 normally that would contain everything and then one that
00:06:29.730 --> 00:06:33.720 says like internal equals false as a environment variable.
00:06:34.680 --> 00:06:38.613 And then preprocessor here would just look in the JSON strip out
00:06:38.613 --> 00:06:41.640 any pages that start with the internal specifier.
00:06:43.000 --> 00:06:45.520 Ohh, actually probably yeah do it the other way around.
00:06:45.520 --> 00:06:50.946 So it's like a specifier that says it is allowed to be
00:06:50.946 --> 00:06:56.373 external facing just to be careful what web server I I
00:06:56.373 --> 00:06:57.360 missed it.
00:06:57.360 --> 00:06:58.800 Is this all running on by the way?
00:06:59.040 --> 00:06:59.800 Yep Host three.
00:07:00.640 --> 00:07:04.240 I meant like specifically is it Apache NICs?
00:07:04.440 --> 00:07:09.280 Ohh, engine X OK, I'm planning on seeing if I can figure out
00:07:09.280 --> 00:07:13.486 some way to have because ngx actually supports Lewis
00:07:13.486 --> 00:07:18.009 scripting, I'm planning on seeing if I can find a way to
00:07:18.009 --> 00:07:22.373 have it like automatically generates all the different
00:07:22.373 --> 00:07:27.293 contexts it needs for like many different spec folders all at
00:07:27.293 --> 00:07:27.690 once.
00:07:28.730 --> 00:07:31.463 That way I don't have to keep editing the config file every
00:07:31.463 --> 00:07:32.010 single time.
00:07:34.050 --> 00:07:37.865 That's kind of some of the stuff I was thinking because I know
00:07:37.865 --> 00:07:41.740 some of those web servers can do modifications and stuff to the
00:07:41.740 --> 00:07:43.800 file before it serves it as well.
00:07:45.080 --> 00:07:49.030 Of course the other possibility is also we could just have like
00:07:49.030 --> 00:07:52.486 everything under one domain and then just have multiple
00:07:52.486 --> 00:07:55.942 different subdirectories that are individually password
00:07:55.942 --> 00:07:56.560 protected.
00:07:57.520 --> 00:08:02.529 So it's like specs.clarityclient.com and then
00:08:02.529 --> 00:08:08.410 slash connector docs slash, I don't know, P21 that's.
00:08:08.530 --> 00:08:11.977 So then about the only thing is do you think you have a good
00:08:11.977 --> 00:08:15.595 weight with the automation tool that you're planning to make or
00:08:15.595 --> 00:08:18.930 CICD to where we could have versioned deployments as well.
00:08:18.930 --> 00:08:22.188 So like say we mark this as this is version one of this
00:08:22.188 --> 00:08:22.770 connector.
00:08:23.730 --> 00:08:26.621 Yeah, And then we can go and look back at that if we end up
00:08:26.621 --> 00:08:27.730 getting an old project.
00:08:28.850 --> 00:08:31.971 Because I have seen like some rough documentation where you
00:08:31.971 --> 00:08:35.352 can just arbitrarily select the version of library you wanna see
00:08:35.352 --> 00:08:37.850 the Yeah, documentation for, that'd be awesome.
00:08:38.620 --> 00:08:40.969 So it's not like it just got wiped out, but it's actually
00:08:40.969 --> 00:08:41.860 tracked and versioned.
00:08:41.860 --> 00:08:45.940 Yeah, that should be doable.
00:08:45.940 --> 00:08:50.083 It might not work with comments though, because I'm pretty sure
00:08:50.083 --> 00:08:53.967 the way commento probably works is it probably looks at the
00:08:53.967 --> 00:08:57.657 absolute path of the page, so comments made on the newer
00:08:57.657 --> 00:09:01.541 version would probably not immediately go back to the older
00:09:01.541 --> 00:09:04.260 version, but that might actually be best.
00:09:04.380 --> 00:09:08.180 Like, maybe only allow comments on the current version, right?
00:09:08.300 --> 00:09:12.035 And then just make the preprocessor not even add the
00:09:12.035 --> 00:09:15.700 commento stuff to the like individual version ones?
00:09:16.700 --> 00:09:19.666 Yeah, I would wipe them out because you're either going to
00:09:19.666 --> 00:09:22.784 add them to that version of the documentation or make the new
00:09:22.784 --> 00:09:25.952 documentation based on what's in the comments and then it also
00:09:25.952 --> 00:09:29.070 make sure we all like we only ever have one continuous stream
00:09:29.070 --> 00:09:30.780 of all comments for the document.
00:09:31.260 --> 00:09:31.500 Yeah.
00:09:34.300 --> 00:09:36.780 And yes, you can give up votes in Commento.
00:09:37.510 --> 00:09:45.302 So let the Karma Pharma begin Now, does Commento have any pens
00:09:45.302 --> 00:09:52.475 like licensing issues or pricing stuff that'll have to be
00:09:52.475 --> 00:09:53.960 factored in?
00:09:54.960 --> 00:09:56.880 Negative, at least not doing the self case.
00:09:56.880 --> 00:10:02.120 Let me double check here, not doing the self hosting at least.
00:10:02.560 --> 00:10:02.960 Let's go.
00:10:02.960 --> 00:10:04.000 Just opening them up again.
00:10:04.920 --> 00:10:04.960 Ohh.
00:10:04.960 --> 00:10:05.440 OK.
00:10:05.440 --> 00:10:06.760 So this is self hosted.
00:10:06.760 --> 00:10:07.160 Come in.
00:10:07.280 --> 00:10:07.520 Yeah.
00:10:08.000 --> 00:10:08.400 Yep.
00:10:08.640 --> 00:10:09.400 Nice.
00:10:11.670 --> 00:10:12.670 Who are you talking to?
00:10:13.950 --> 00:10:17.910 I mean I would I would hope with it being you jail, I just had to
00:10:17.910 --> 00:10:21.510 make sure because I've seen far too many websites use those
00:10:21.510 --> 00:10:25.350 builtin comment things that then you have to sign up and get an
00:10:25.350 --> 00:10:27.150 external account in that crap.
00:10:27.270 --> 00:10:31.519 No, you just so or rather you can set to allow anonymous
00:10:31.519 --> 00:10:32.190 comments.
00:10:33.390 --> 00:10:35.470 But you can also in here sign up.
00:10:36.390 --> 00:10:38.430 It doesn't even bother verifying e-mail address.
00:10:38.430 --> 00:10:41.384 I don't think you really just give it an e-mail address and a
00:10:41.384 --> 00:10:42.480 password and that's it.
00:10:43.200 --> 00:10:46.720 And is that account specific to our Commento instance?
00:10:47.080 --> 00:10:47.720 Yes.
00:10:48.240 --> 00:10:52.208 So it's my understanding I can I don't know that for certain,
00:10:52.208 --> 00:10:53.040 double check.
00:10:55.440 --> 00:10:58.390 And we can also turn on 2 factor, not two factor single
00:10:58.390 --> 00:10:59.760 sign on with other things.
00:11:00.480 --> 00:11:03.592 Although obviously I don't know what we would actually do that
00:11:03.592 --> 00:11:03.840 with.
00:11:06.320 --> 00:11:10.539 Like what's gonna actually work for all of our clients all at
00:11:10.539 --> 00:11:10.880 once.
00:11:12.600 --> 00:11:15.425 I always yeah, I'm a bit hesitant with single sign on
00:11:15.425 --> 00:11:18.565 just because then it's, you know, a single point of failure
00:11:18.565 --> 00:11:19.560 then to get access.
00:11:19.720 --> 00:11:24.421 Although with the comment stuff it's less of a problem because
00:11:24.421 --> 00:11:25.840 it's just comments.
00:11:31.360 --> 00:11:33.040 OK, so here's command to database.
00:11:35.840 --> 00:11:36.240 Let's see.
00:11:43.010 --> 00:11:45.570 Yeah, here are the current entries.
00:11:48.130 --> 00:11:48.250 Cool.
00:11:48.250 --> 00:11:51.870 So then, interestingly that that does also mean that both
00:11:51.870 --> 00:11:54.930 moderators and commenters are in the same table.
00:11:54.930 --> 00:12:01.463 I don't know why they need their commenters then, but yeah,
00:12:01.463 --> 00:12:02.770 that's cool.
00:12:03.290 --> 00:12:05.450 Also, nice to see that it's hashing passwords.
00:12:05.450 --> 00:12:05.690 Good.
00:12:05.690 --> 00:12:06.010 Good.
00:12:06.090 --> 00:12:08.470 I would hope so with the project.
00:12:09.590 --> 00:12:13.630 I guess I should notice Cominto is not at all set in stone.
00:12:14.150 --> 00:12:17.406 That was literally just the first thing that I was able to
00:12:17.406 --> 00:12:19.670 find just in a working session with JLR.
00:12:20.750 --> 00:12:23.466 Technically the working session was supposed to be for SO, but
00:12:23.466 --> 00:12:26.226 we were just getting it deployed and then we're like, hey, what
00:12:26.226 --> 00:12:26.829 if we do this?
00:12:29.470 --> 00:12:31.750 So I'm still going to look for something else if I can.
00:12:32.870 --> 00:12:36.883 Partially because it looks like this might be using an older
00:12:36.883 --> 00:12:40.567 version of the Postgres connector for I think it was in
00:12:40.567 --> 00:12:44.647 Go does not support the SCRAM, so like SCRAM 256 Shay hashing
00:12:44.647 --> 00:12:46.949 that Postgres recommends nowadays.
00:12:47.870 --> 00:12:51.531 I have actually set it to send the password in plain text over
00:12:51.531 --> 00:12:55.077 the connection, which obviously isn't as bad since it's only
00:12:55.077 --> 00:12:58.390 going over like pretty much just a local bridge network.
00:12:58.390 --> 00:13:01.649 But it'd still be nice to have something a little bit more up
00:13:01.649 --> 00:13:02.070 to date.
00:13:04.590 --> 00:13:05.070 Fair enough.
00:13:06.790 --> 00:13:10.596 So I think it's very least a good fall back if we can't find
00:13:10.596 --> 00:13:11.470 anything else.
00:13:13.670 --> 00:13:17.475 And then I guess the one downside to this thing overall,
00:13:17.475 --> 00:13:21.748 obviously you can't like select and then directly say I want to
00:13:21.748 --> 00:13:22.750 come into this.
00:13:23.670 --> 00:13:27.482 Rather, you would select something and then just use Mark
00:13:27.482 --> 00:13:31.230 Johnson's X to say, hey, this is what I'm talking about.
00:13:32.470 --> 00:13:35.824 So we would have to do a little bit of training to tell the
00:13:35.824 --> 00:13:39.290 clients, hey, this is how you use Markdown syntax, but that's
00:13:39.290 --> 00:13:41.750 probably not too bad unless I'm missing it.
00:13:41.750 --> 00:13:44.423 There's also not a preview button, which that would be one
00:13:44.423 --> 00:13:46.870 thing that we would, yeah, probably want the clients.
00:13:54.750 --> 00:13:55.070 I am, yeah.
00:13:55.070 --> 00:13:58.145 Curious, since it's directly integrated into the page, are
00:13:58.145 --> 00:14:01.169 you able to type out mermaid stuff into there and have it
00:14:01.169 --> 00:14:01.430 work?
00:14:04.110 --> 00:14:07.750 It's my depending on how it handles mermaid.
00:14:08.750 --> 00:14:10.710 Let me search you on.
00:14:10.710 --> 00:14:12.990 So they they have not left any comments yet.
00:14:13.630 --> 00:14:13.990 Good.
00:14:15.190 --> 00:14:15.390 Great.
00:14:15.430 --> 00:14:15.550 Yep.
00:14:16.910 --> 00:14:19.803 OK, so let's just real quick try this and then delete it really
00:14:19.803 --> 00:14:20.030 fast.
00:14:21.790 --> 00:14:22.870 I doubt they even looked at it.
00:14:23.110 --> 00:14:24.390 The Swedish team, I think you'd be fine.
00:14:24.390 --> 00:14:26.950 You mean the Swiss Swiss team?
00:14:27.430 --> 00:14:31.540 Yeah, let's see.
00:14:35.980 --> 00:14:36.980 Does tab work there?
00:14:36.980 --> 00:14:38.260 Does it go to the next thing?
00:14:38.740 --> 00:14:40.100 It it goes tab?
00:14:40.100 --> 00:14:41.180 Work around the page as a whole.
00:14:41.180 --> 00:14:43.780 All right, thanks.
00:14:47.420 --> 00:14:47.580 Nope.
00:14:47.940 --> 00:14:48.220 Darn.
00:14:49.940 --> 00:14:50.180 OK.
00:14:50.180 --> 00:15:03.673 And then I guess this also shows off the Oops admin interface,
00:15:03.673 --> 00:15:08.600 clear all the comments.
00:15:09.880 --> 00:15:11.400 So here's the admin interface for that.
00:15:11.400 --> 00:15:14.544 So whenever you want to add a new one we or if we do the whole
00:15:14.544 --> 00:15:17.640 domain thing, you just can't go in here click add new domain.
00:15:20.960 --> 00:15:24.957 So again I'm I am starting to lean a little bit towards have
00:15:24.957 --> 00:15:28.757 just have one gigantic domain and then just use sub paths
00:15:28.757 --> 00:15:32.558 because that also makes it much much easier to handle the
00:15:32.558 --> 00:15:36.227 engineer's context side of things because you know it's
00:15:36.227 --> 00:15:40.355 just more directories and far easier I would think to automate
00:15:40.355 --> 00:15:40.880 for you.
00:15:42.840 --> 00:15:46.957 And it would also give well I don't know, I guess the user
00:15:46.957 --> 00:15:51.424 accounts would still be global no matter what, didn't look like
00:15:51.424 --> 00:15:55.822 the database was really storing anything to do with which site
00:15:55.822 --> 00:15:56.520 you're on.
00:16:00.800 --> 00:16:02.880 We can see that the client hasn't read their specs.
00:16:10.320 --> 00:16:14.076 Does the analytics thing work for like each page or is it
00:16:14.076 --> 00:16:14.400 just.
00:16:15.040 --> 00:16:19.320 No, it looks like it's global DAR 27th.
00:16:19.360 --> 00:16:24.120 Ohh yeah, with all the refreshes we get time.
00:16:25.200 --> 00:16:31.007 Ohh OK We can also add our own analytics if you really wanted
00:16:31.007 --> 00:16:32.600 to like the mark.
00:16:32.720 --> 00:16:33.680 Yeah stuff an empty book.
00:16:33.840 --> 00:16:34.120 Yeah.
00:16:34.120 --> 00:16:39.035 You already saw like we can just directly splat some and some
00:16:39.035 --> 00:16:43.000 mark down into it or mark down some HTML into it.
00:16:44.440 --> 00:16:47.400 Only reason I I was bringing that up is just because I could
00:16:47.400 --> 00:16:50.214 see clients just certifying stuff without even looking at
00:16:50.214 --> 00:16:50.360 it.
00:16:52.720 --> 00:16:53.640 So Mr.
00:16:53.640 --> 00:16:56.954 Client, we could see that you have not looked at any of your
00:16:56.954 --> 00:16:57.280 pages.
00:16:57.600 --> 00:16:59.520 Please do so before you sign off.
00:16:59.840 --> 00:17:00.400 Thank you.
00:17:03.060 --> 00:17:07.126 Find that Big Cassie was using to make a very simple message
00:17:07.126 --> 00:17:07.860 sound bead.
00:17:16.740 --> 00:17:20.046 Yeah, and then one of the other nice things here, we can have it
00:17:20.046 --> 00:17:20.860 send off emails.
00:17:20.860 --> 00:17:24.020 So I haven't actually fully set that up yet on the server side.
00:17:24.540 --> 00:17:26.220 Just whenever any new comments come in.
00:17:28.240 --> 00:17:31.705 Of course, if we don't or if we don't do it as multiple
00:17:31.705 --> 00:17:35.542 different domains, then I think just everybody in the Connect
00:17:35.542 --> 00:17:38.080 team would get emails every single time.
00:17:39.640 --> 00:17:48.887 So we'll, yeah, we'll need to figure something out there, lots
00:17:48.887 --> 00:17:55.640 of stuff to look into, but I hear no dissent.
00:17:55.640 --> 00:17:56.640 So this is what we're doing.
00:17:56.920 --> 00:18:04.184 Prepare to implement it tomorrow, But you're not
00:18:04.184 --> 00:18:05.370 descent.
00:18:05.450 --> 00:18:06.650 I also need to do a sense.
00:18:07.250 --> 00:18:10.133 I like the idea of having a doc that is hosted on a web page
00:18:10.133 --> 00:18:11.410 that people can go look at.
00:18:15.250 --> 00:18:18.242 I mean, especially when we're dealing with difficult
00:18:18.242 --> 00:18:19.090 customizations.
00:18:19.450 --> 00:18:19.650 Yep.
00:18:20.850 --> 00:18:25.072 And the best part, of course, is that we will actually have the
00:18:25.072 --> 00:18:28.570 real spec sheet for what Connect needs to be hosted.
00:18:28.930 --> 00:18:30.170 Hosted in one place.
00:18:30.680 --> 00:18:31.640 Yeah, that we can update.
00:18:31.720 --> 00:18:35.123 And then they don't get the ancient version that still tells
00:18:35.123 --> 00:18:38.080 them they absolutely need SQL Server no matter what.
00:18:38.840 --> 00:18:39.200 Right.
00:18:39.440 --> 00:18:40.800 And done at Framework 4.
00:18:41.720 --> 00:18:45.320 Yep, Yep.
00:18:45.480 --> 00:18:46.360 I really like the idea of that.
00:18:46.840 --> 00:18:48.040 I think there's a lot of potential here.
00:18:48.320 --> 00:18:52.600 I still like, outline a lot, but you're still like that.
00:18:52.600 --> 00:19:01.070 Again, get outline.com I think not that one.
00:19:01.150 --> 00:19:02.230 Don't think it's gonna be good.
00:19:02.590 --> 00:19:03.870 So not get out good online.com.
00:19:07.350 --> 00:19:08.790 Oh OK, I see it.
00:19:09.070 --> 00:19:13.510 Yeah, that's not confusing, right?
00:19:13.990 --> 00:19:15.350 Less than a mess of the docs.
00:19:15.630 --> 00:19:18.532 Come here and pay us to give you another best that we will let
00:19:18.532 --> 00:19:19.270 you back out of.
00:19:19.590 --> 00:19:29.410 You can self host it download for Mac OS.
00:19:29.410 --> 00:19:34.318 Interesting it thinks you're on Mac because my thing with
00:19:34.318 --> 00:19:39.649 something like this is the MD book thing allows us to keep the
00:19:39.649 --> 00:19:45.149 connector documentation with the connector which is what I would
00:19:45.149 --> 00:19:48.450 prefer versus it being disjoint right?
00:19:48.450 --> 00:19:48.650 Right.
00:19:49.370 --> 00:19:53.943 Just because otherwise you end up with like Nucleno where yeah,
00:19:53.943 --> 00:19:58.444 it was handed C3 documentation for AC4 project where they look
00:19:58.444 --> 00:20:00.660 nothing along, yeah, yeah yeah.
00:20:01.740 --> 00:20:05.000 And of course if it's an indie book, like the markdown stuff is
00:20:05.000 --> 00:20:07.140 pretty much just universal at this point.
00:20:07.700 --> 00:20:10.914 Like if we want to switch to Doku wiki or media wiki or
00:20:10.914 --> 00:20:14.588 something down the line, there are plenty of converters that we
00:20:14.588 --> 00:20:17.860 could use to trivially convert to whatever else we want.
00:20:18.380 --> 00:20:18.580 Sure.
00:20:19.580 --> 00:20:21.666 Whereas I don't know what this thing is going to use
00:20:21.666 --> 00:20:22.100 internally.
00:20:23.930 --> 00:20:26.290 So if we keep it empty book, it's easy to convert to anything
00:20:26.290 --> 00:20:27.090 else that we need to.
00:20:28.050 --> 00:20:28.490 And then what?
00:20:28.490 --> 00:20:31.367 You mean, you mean in terms of, like, marked down itself, marked
00:20:31.367 --> 00:20:31.810 on syntax?
00:20:32.330 --> 00:20:32.610 Yeah.
00:20:32.770 --> 00:20:35.711 Like if we ever wanted to just convert to a different system
00:20:35.711 --> 00:20:37.930 later, that stuff would be much, much easier.
00:20:38.290 --> 00:20:38.410 Yeah.
00:20:38.410 --> 00:20:38.530 Yeah.
00:20:39.450 --> 00:20:43.290 Does it start in a way that we can actually get to it nicely?
00:20:43.290 --> 00:20:43.410 Yeah.
00:20:43.410 --> 00:20:43.730 I don't know.
00:20:47.250 --> 00:20:51.388 And like Sarah was saying, is there a way to have it tied into
00:20:51.388 --> 00:20:52.440 the repo, right?
00:20:52.440 --> 00:20:54.960 Yeah, I don't know the answer to those.
00:20:57.000 --> 00:20:58.240 So yeah.
00:21:00.640 --> 00:21:03.560 And of course, MD book is basically the de facto Rust
00:21:03.560 --> 00:21:06.859 documentation software now, so it has a pretty big community
00:21:06.859 --> 00:21:07.400 behind it.
00:21:08.000 --> 00:21:08.400 Oh, sure.
00:21:22.000 --> 00:21:23.040 Actually, actually went away.
00:21:23.040 --> 00:21:25.080 Good, right?
00:21:26.500 --> 00:21:30.100 Yeah, or once going twice implemented.
00:21:35.180 --> 00:21:35.340 Cool.
00:21:35.500 --> 00:21:39.385 So this kind of goes into our next topic, which is going to be
00:21:39.385 --> 00:21:42.900 making more documentation for our connectors in general.
00:21:43.500 --> 00:21:45.900 We started doing that with the sales info doc stuff.
00:21:48.020 --> 00:21:50.741 I'm kind of looking for a solution similar to this, like
00:21:50.741 --> 00:21:53.796 the MD book stuff where we can just host this page and serve it
00:21:53.796 --> 00:21:53.940 up.
00:21:53.940 --> 00:21:59.027 Which means that I could send this along to a client and say
00:21:59.027 --> 00:22:01.530 you have Sage 50, here you go.
00:22:01.530 --> 00:22:04.642 Here's all the documentation in the Level 3 docs for our Sage 50
00:22:04.642 --> 00:22:07.611 connector, Sage 100 connector for what it does and doesn't do
00:22:07.611 --> 00:22:08.330 out-of-the-box.
00:22:09.050 --> 00:22:10.170 I don't know if you were in here.
00:22:10.170 --> 00:22:14.077 When we were talking about it, we were discussing ways to mark
00:22:14.077 --> 00:22:17.489 pages as internal or external, so I was thinking maybe
00:22:17.489 --> 00:22:18.730 something like this.
00:22:20.570 --> 00:22:23.447 So this would be something that a preprocessor would pick up and
00:22:23.447 --> 00:22:23.890 strip out.
00:22:24.620 --> 00:22:27.128 But then there will be two different ways of running
00:22:27.128 --> 00:22:27.460 things.
00:22:27.860 --> 00:22:32.396 So if we set the environment variable maybe like externally
00:22:32.396 --> 00:22:37.159 equals true or sorry probably actually internally equals true,
00:22:37.159 --> 00:22:40.940 then it will include pages that do not have this.
00:22:40.980 --> 00:22:45.912 Otherwise, it would just strip out any pages from the little
00:22:45.912 --> 00:22:51.248 bit of what was that I told that Jason, that it receives and just
00:22:51.248 --> 00:22:52.300 publish that.
00:22:53.060 --> 00:22:55.974 Then we can just publish those, the different directories and
00:22:55.974 --> 00:22:58.700 have like, you know, different access rules and all that.
00:22:59.300 --> 00:23:01.578 Yeah, I mean, heck, we could even make it automatically
00:23:01.578 --> 00:23:03.734 redirect if it finds you're coming from the internal
00:23:03.734 --> 00:23:04.060 network.
00:23:04.940 --> 00:23:05.180 Sure.
00:23:06.660 --> 00:23:10.144 So that would let us host it all in one place while still being
00:23:10.144 --> 00:23:12.540 able to mark pages as internal or external.
00:23:13.180 --> 00:23:13.380 Yep.
00:23:18.740 --> 00:23:19.460 Yeah, that'd be cool.
00:23:19.700 --> 00:23:22.510 Because yeah, what we'll do next is create that Level 3
00:23:22.510 --> 00:23:25.522 documentation to have to send along to a client to once and
00:23:25.522 --> 00:23:28.282 for all solve the problem of what do our connectors do
00:23:28.282 --> 00:23:30.140 out-of-the-box and what do they not.
00:23:31.660 --> 00:23:35.580 So if you have the time to make the documentation right.
00:23:35.580 --> 00:23:36.820 And that's what I'm saying.
00:23:36.820 --> 00:23:40.388 So I have approval from Chris that we can get time into the
00:23:40.388 --> 00:23:43.540 sprints to start doing that and start creating that.
00:23:43.540 --> 00:23:46.919 Because I think, I think everyone realizes by now that
00:23:46.919 --> 00:23:50.421 the main main issue, that challenge that we face is just
00:23:50.421 --> 00:23:52.940 not understanding what's out-of-the-box.
00:23:52.940 --> 00:23:55.443 When it comes to these connectors especially, I know
00:23:55.443 --> 00:23:58.514 they've been pushing hard for a Level 3 doc for just the Connect
00:23:58.514 --> 00:23:58.940 platform.
00:23:59.300 --> 00:24:02.653 But I stress to them that that doesn't really do much for a
00:24:02.653 --> 00:24:06.006 client because yeah, OK, they understand that they get cues
00:24:06.006 --> 00:24:07.180 and things like that.
00:24:07.180 --> 00:24:11.368 And really the only thing that I ever hear is like push back that
00:24:11.368 --> 00:24:14.477 way is is related to performance, like real time
00:24:14.477 --> 00:24:15.620 sinking and stuff.
00:24:15.980 --> 00:24:19.156 Rarely have I ever heard someone complain about what the Hang
00:24:19.156 --> 00:24:22.282 Fire offers out-of-the-box, but I have heard people complain
00:24:22.282 --> 00:24:25.100 about what the connector itself offers out-of-the-box.
00:24:25.420 --> 00:24:27.340 So I want to create Level 3 documentation.
00:24:27.340 --> 00:24:30.080 We can send it out to a client in the initial onboarding to say
00:24:30.080 --> 00:24:32.691 here's what the connector does out-of-the-box, here's what's
00:24:32.691 --> 00:24:35.474 gonna be customization, and just refer back to that document all
00:24:35.474 --> 00:24:35.860 the time.
00:24:37.140 --> 00:24:39.740 So I think this, the Empty book solution kind of gets us there.
00:24:40.420 --> 00:24:44.415 Go ahead, we'll have what that is, how specific mappings
00:24:44.415 --> 00:24:47.780 interact, so you know with customers and stuff.
00:24:47.780 --> 00:24:52.764 How addresses maps over can be a bit hard to describe, especially
00:24:52.764 --> 00:24:56.691 when you know it's the combination of those systems
00:24:56.691 --> 00:24:58.580 rather than just the one.
00:24:58.580 --> 00:25:01.780 What do you mean?
00:25:03.180 --> 00:25:08.033 So for example this has come up a lot where the they want the
00:25:08.033 --> 00:25:12.966 company name to go into like the name on the order in Sage 100
00:25:12.966 --> 00:25:17.819 because Sage 100 only has one name field and stuff like that.
00:25:19.110 --> 00:25:22.277 You know little bits and pieces like that where they think it's
00:25:22.277 --> 00:25:24.950 going to be one mapping when it's actually the other.
00:25:24.950 --> 00:25:29.192 Well that's what I mean like this this document could specify
00:25:29.192 --> 00:25:33.503 that like by default we declare they're still going to have to
00:25:33.503 --> 00:25:37.883 they're they're still going to have to understand though that's
00:25:37.883 --> 00:25:42.262 or like make the association in their minds sure that's company
00:25:42.262 --> 00:25:46.437 name is separates and the other side is only mapping name to
00:25:46.437 --> 00:25:47.190 name right.
00:25:47.310 --> 00:25:47.590 Right.
00:25:48.270 --> 00:25:53.787 Yeah, if only we had maybe like a UI a connects that would show
00:25:53.787 --> 00:25:57.840 the mapping with both sides just side by side.
00:25:58.600 --> 00:26:00.280 Maybe it's a little three column layout.
00:26:07.280 --> 00:26:10.948 We can get a backup for it and then build that straight off of
00:26:10.948 --> 00:26:11.240 that.
00:26:12.200 --> 00:26:13.280 We could, we could.
00:26:15.640 --> 00:26:21.137 We'd also have to determine where that priority lies, and I
00:26:21.137 --> 00:26:24.620 couldn't tell you the answer to that.
00:26:24.620 --> 00:26:25.900 All the things we want to accomplish.
00:26:27.140 --> 00:26:32.405 In my mind, it's probably something like finishing up the
00:26:32.405 --> 00:26:37.942 sales info docs, finishing up Level 3 docs, finishing up the
00:26:37.942 --> 00:26:43.480 CICD and then getting into the custom scheduler and stuff in
00:26:43.480 --> 00:26:49.472 terms of most immediate value to long term stuff which also gives
00:26:49.472 --> 00:26:54.737 us time to properly plan the schedule and not just Russia
00:26:54.737 --> 00:27:00.093 that we have something to say that hey we've completed our
00:27:00.093 --> 00:27:01.999 story points exactly.
00:27:04.120 --> 00:27:10.210 Yeah, I kind of curious to hear what you guys thoughts on that.
00:27:10.210 --> 00:27:14.604 Like do you think a Level 3 documentation Or or rather, do
00:27:14.604 --> 00:27:18.998 you think there's a version of documentation that helps us
00:27:18.998 --> 00:27:23.467 solve the issue of sales and clients not understanding what
00:27:23.467 --> 00:27:26.000 our connectors do out-of-the-box?
00:27:29.280 --> 00:27:32.320 And here we can partially know because.