We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Blurring the Lines: Tiki 'No-Code/Low-Code' Empowers

00:00

Formale Metadaten

Titel
Blurring the Lines: Tiki 'No-Code/Low-Code' Empowers
Untertitel
Full Stack Developer without knowledge of any programming languages
Serientitel
Anzahl der Teile
637
Autor
Lizenz
CC-Namensnennung 2.0 Belgien:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
'No-Code/Low-Code' software by Tiki.org has blurred the lines, allowing for team member participation and engagement on digital and data initiatives on many levels. It goes well beyond many CRM, ERP, PM, etc, offerings which are good at what they do but typically narrow in focus, by giving users a wide mix of hundreds of tools in many categories - Front-end, Back-end, Databases, Admin and Mobile. Big 'Features', supporting 'Features' and countless small but handy plugins all combine, allowing users to literally create any app for any business sector. This less focused and 'utilitarian' nature is more relevant than ever as Tiki resolves a problem so many organizations today are struggling to solve - too many apps with little to no integration between them. Tiki offers so much, in fact, that it allows individuals to become Full Stack Developers - this is my story and where I'm at after using Tiki for over 8 years. However, since it's FLOSS software it also fits developers like a glove, as unlike proprietary 'No-Code/Low-Code' offerings where even developers would need to submit Bug Reports and wait for responses, Tiki allows them to get 'under the hood' and debug complex configurations at their convenience. This presentation briefly covers a few 'No-Code/Low-Code' development tools in each of the 5 categories that Full Stack Developers need, various user roles and the levels on which they can participate as well as gives examples of 'No-Code' and 'Low-Code' within Tiki.
GeradeCodeSoftwareentwicklerSystem-on-ChipDatenbankEreignishorizontWikiElektronische PublikationSpeicherabzugInformationFormale SpracheModemInnerer PunktModul <Datentyp>Coxeter-GruppeGraphische BenutzeroberflächeHybridrechnerAlgebraisches ModellCOMGeradeSoftwareCodeBitSpannweite <Stochastik>Projektive EbeneMultiplikationsoperatorNichtlinearer OperatorHomepageZahlenbereichReelle ZahlSpeicherabzugContent ManagementDatenfeldRechter WinkelComputeranimation
SystemplattformSpannweite <Stochastik>SoftwareFreewareOpen SourceGroupwareVersionsverwaltungBeweistheorieIdeal <Mathematik>RechnernetzDienst <Informatik>Physikalisches SystemDigital Rights ManagementFormale SpracheKorrelationProzess <Informatik>Installation <Informatik>Modul <Datentyp>ProgrammbibliothekSkriptspracheAppletComputersicherheitMereologieNotepad-ComputerTopologieBildschirmmaskeDifferenteOpen SourceZahlenbereichSystemplattformInhalt <Mathematik>Bootstrap-AggregationWeb-ApplikationDigital Rights ManagementTabellenkalkulationFreeware
CodeSystemplattformCodierungEndliche ModelltheorieFormale SpracheZahlenbereichPlug inInstallation <Informatik>UnternehmensarchitekturCodeSoftwareSystemplattformGraphfärbungLesen <Datenverarbeitung>DruckverlaufSelbst organisierendes SystemComputeranimation
WikiGroupwareContent ManagementCodeWeb SiteGruppenoperationTypentheorieKeller <Informatik>SoftwareentwicklerPunktFokalpunktGruppe <Mathematik>Installation <Informatik>Quelle <Physik>GraphfärbungZentralisatorBitFokalpunktMultiplikationsoperatorForcingÄhnlichkeitsgeometrieRechter WinkelDifferenteInternetworkingWeb SiteSelbst organisierendes SystemMailing-ListePunktGruppe <Mathematik>Physikalisches SystemTypentheorieFormale SpracheDatensatzDistributionenraumCASE <Informatik>BeanspruchungCoxeter-GruppeBenutzerbeteiligungUmwandlungsenthalpieMereologiePunktspektrumWeb-DesignerCodierungInhalt <Mathematik>Digital Rights ManagementComputeranimation
Mobiles InternetDatenbankHybridrechnerCross-site scriptingAlgebraisches ModellSoftwareentwicklerKeller <Informatik>Modul <Datentyp>Coxeter-GruppeApp <Programm>Desintegration <Mathematik>COMMarketinginformationssystemGraphische BenutzeroberflächeNebenbedingungPunktDualitätssatzBeschreibungskomplexitätStatistikFaktorenanalyseSchlussregelKontrollstrukturDigital Rights ManagementGruppenoperationGraphische BenutzeroberflächeMereologieFormale SpracheServerFront-End <Software>Arithmetische FolgeDifferenteCodierungInstantiierungFehlermeldungKomplex <Algebra>ProzessautomationKomponente <Software>Projektive EbeneHyperbelverfahrenTeilbarkeitBootstrap-AggregationGarbentheorieGamecontrollerInstallation <Informatik>Prozess <Informatik>Coxeter-GruppeIntegralZahlenbereichMultiplikationsoperatorMobiles InternetTypentheoriePlug inWeb-SeiteKonfiguration <Informatik>SystemverwaltungDigital Rights ManagementInhalt <Mathematik>DatenbankDatenstrukturWeb-ApplikationEinfache GenauigkeitOrdnung <Mathematik>StabMessage-PassingSoftwarewartungSchlussregelBenutzeroberflächeGruppe <Mathematik>NebenbedingungVorzeichen <Mathematik>SystemaufrufArithmetisches MittelSchedulingDreizehnContent ManagementBildschirmmaskeComputeranimation
Elektronische PublikationWeb logFAQElektronisches ForumMessage-PassingURLDienst <Informatik>KontrollstrukturComputersicherheitMakrobefehlResultanteMailing-ListeQuick-SortGradientWeb ServicesParametersystemDatensatzWeg <Topologie>SchnittmengeHyperbelverfahrenDatenbankGamecontrollerComputeranimation
Elektronische PublikationWikiGruppenoperationDigital Rights ManagementModul <Datentyp>Desintegration <Mathematik>KontrollstrukturMereologieFront-End <Software>MultiplikationsoperatorIntegralMAPPlug inCanadian Mathematical SocietyMailing-ListeFormale SpracheDigital Rights ManagementLeistung <Physik>Computeranimation
SchedulingDatenstrukturMailing-ListeIndexberechnungObjekt <Kategorie>PROMDigitalfilterSystemverwaltungGruppenoperationInhalt <Mathematik>Gruppe <Mathematik>UmwandlungsenthalpieParametersystemDateiformatCOMVersionsverwaltungDean-ZahlTypentheorieSpezialrechnerOverlay-NetzDatentypMathematische LogikPermanenteAbelsche KategorieKategorie <Mathematik>Konfiguration <Informatik>Automat <Automatentheorie>Nabel <Mathematik>BenutzerprofilTermNormierter RaumStapeldateiSynchronisierungElektronisches ForumPlug inSystemverwaltungGruppenoperationSkalenniveauMAPMailing-ListeGarbentheorieRechter WinkelBitElektronische PublikationRichtungDatenbankStichprobenumfangDatenfeldMathematikCodeAbgeschlossene MengeDefaultFormale SpracheSchedulingDigitalisierungPlotterVerweildauerMereologieComputeranimationProgramm/QuellcodeXML
SchedulingElektronischer ProgrammführerGruppenoperationPhysikalisches SystemRechenwerkBimodulMenütechnikMechatronikSpannweite <Stochastik>TaskProzess <Informatik>Graphische BenutzeroberflächeSchedulingGruppenoperationVirtuelle MaschineMultiplikationsoperatorPhysikalisches SystemInhalt <Mathematik>StrömungsrichtungSchlussregelE-MailAutomatische IndexierungFront-End <Software>GeradeServerShape <Informatik>SoftwaretestGüte der AnpassungComputeranimation
SchedulingInformationTaskDateiformatDualitätstheorieIntegralLesen <Datenverarbeitung>Web ServicesTaskNabel <Mathematik>MultiplikationsoperatorMailing-ListeGruppenoperationSchedulingPlug inComputeranimation
ParametersystemCAN-BusDefaultTemplateBildschirmmaskeDateiformatURLWeb-SeiteDienst <Informatik>Web SiteDesintegration <Mathematik>SOAP <Protokoll>WärmeübergangSelbstrepräsentationGerichtete MengeArchitektur <Informatik>ProgrammierumgebungWikiOpen SourceCodeProtokoll <Datenverarbeitungssystem>Pi <Zahl>VerzeichnisdienstProgrammQuellcodeSoftware Development KitDigitalfilterSelbst organisierendes SystemIkosaederKategorie <Mathematik>SoftwareentwicklerEnergiedichteZufallszahlenOnline-KatalogStrategisches SpielVersuchsplanungPlug inWeb ServicesMinimumSystemaufrufGenerator <Informatik>TransportproblemInternet der DingeBenutzerbeteiligungFront-End <Software>Hook <Programmierung>Physikalisches SystemAlgorithmische LerntheorieInformationWeb SiteVerzeichnisdienstUnrundheitPhysikalischer EffektQuick-SortMultiplikationsoperatorProgrammEndliche ModelltheorieComputeranimation
Maschinelles LernenVirtuelle MaschineAlgorithmusPhysikalische TheorieProgrammbibliothekMehrschichten-PerzeptronDatenmodellOffene MengeVersionsverwaltungKünstliche IntelligenzFormale SpracheEndliche ModelltheorieWikiDivisionInhalt <Mathematik>Web-SeiteWeb SiteMAPSoftwaretestWeb logRechter WinkelAlgorithmische LerntheorieVisualisierungMinimumPunktMultiplikationsoperatorEinsWeb SiteInhalt <Mathematik>TouchscreenMAPPlug inErwartungswertProgrammfehlerDebuggingCode
WikiRechenwerkKeller <Informatik>Web-SeiteCOMInhalt <Mathematik>SkalarproduktSpannweite <Stochastik>Selbst organisierendes SystemWeb-SeiteWellenpaketWikiRechter WinkelPunktGeradeCoxeter-GruppeBildgebendes VerfahrenEgo-ShooterMereologieE-MailWort <Informatik>TabellenkalkulationComputeranimation
Inhalt <Mathematik>Web-SeiteWeb SiteMAPMarketinginformationssystemMechatronikBildschirmsymbolKeller <Informatik>URLPixelKreisbogenAdditionDefaultParametersystemVariablePROMWikiVerschlingungCodeKategorie <Mathematik>BenutzerfreundlichkeitKurvenanpassungKorrelationAntwortfunktionKonfiguration <Informatik>KonfigurationsraumDreieckBildschirmsymbolGraphische BenutzeroberflächeWeb-SeiteBootstrap-AggregationFilter <Stochastik>Minkowski-MetrikTabelleDreieckPlug inKonfigurationsraumMinimumDifferenteFlächentheorieBitInformationWikiCodeWeb SiteRechter WinkelGamecontrollerDefaultSystem FInhalt <Mathematik>MultiplikationsoperatorTypentheorieMehrrechnersystemMereologieKreisbewegungKlasse <Mathematik>ComputerspielZweiPunktParametersystemLebesgue-IntegralSelbst organisierendes SystemTemplateDisk-ArrayObjekt <Kategorie>ÄhnlichkeitsgeometrieResultanteXMLComputeranimation
ZeitzoneKontrollstrukturMessage-PassingMeta-TagRuhmasseElektronische PublikationComputersicherheitSpezialrechnerKonfiguration <Informatik>CliquenweiteGruppe <Mathematik>Web-SeiteWidgetSoundverarbeitungStandardabweichungCodierung <Programmierung>Inhalt <Mathematik>CodeFontCantor-DiskontinuumGarbentheorieWeb SiteClientMAPMereologieElektronische PublikationSchlussregelWeb SiteMultiplikationsoperatorÜberlagerung <Mathematik>Lie-GruppeGruppenoperationInformationsspeicherungParametersystemPlug inInformationBitCliquenweiteSchreib-Lese-KopfSprachsyntheseFluidURLRechter WinkelDifferenteKrümmungsmaßComputeranimation
Keller <Informatik>Ein-AusgabeTouchscreenGleichheitszeichenCliquenweiteTotal <Mathematik>Produkt <Mathematik>Partielle DifferentiationGraphische BenutzeroberflächeInformationFluidDatensatzDifferenzkernCliquenweiteMultiplikationsoperatorBootstrap-AggregationGraphfärbungQuaderProfil <Strömung>Computeranimation
ClientPixelGarbentheorieMAPDruckverlaufWeb SiteWeb-SeiteKategorie <Mathematik>Digital Rights ManagementCASE <Informatik>DatenbankSharewareMailing-ListeBildschirmmaskeWikiWeg <Topologie>Inverser LimesRechenbuchDatenfeldTypentheorieAbelsche KategorieVerschlingungE-MailElektronische PublikationGruppe <Mathematik>BildschirmsymbolRelation <Informatik>VideokonferenzFormale SpracheURLGruppenoperationGleitkommarechnungLatent-Class-AnalyseDatenbankKlasse <Mathematik>BitGamecontrollerQuaderGarbentheorieRechter WinkelPlug inWort <Informatik>MereologieWeb-SeiteTropfenMultiplikationsoperatorMathematikRechenbuchMailing-ListeDivisionTypentheorieGraphfärbungDatenfeldAusdruck <Logik>StandardabweichungKonfigurationsraumKonfiguration <Informatik>BimodulGeradeMAPWeg <Topologie>InstantiierungProjektive EbeneLateinisches QuadratLeistung <Physik>Green-FunktionGebäude <Mathematik>Digital Rights ManagementElektronische PublikationSharewareVerschlingungDifferenteGruppenoperationCASE <Informatik>Computeranimation
DatenbankSharewareATMDefaultKonvexe HülleDigital Rights ManagementProjektive EbeneGraphische BenutzeroberflächeOrdnung <Mathematik>DebuggingSharewareFront-End <Software>Stützpunkt <Mathematik>CodeDatensichtgerätWeg <Topologie>Cracker <Computerkriminalität>Twitter <Softwareplattform>StellenringComputeranimation
DatenfeldDigital Rights ManagementDatentypProjektive EbeneDatenfeldÄhnlichkeitsgeometrieElektronische PublikationKeller <Informatik>MultiplikationsoperatorFächer <Mathematik>Computeranimation
DatenfeldDigital Rights ManagementDatentypMailing-ListeMathematikDatenfeldMailing-ListeSelbst organisierendes SystemWeb SiteProjektive EbeneTypentheorieE-MailDatensichtgerätStereometrieSystemaufrufTouchscreenInformationMultiplikationsoperatorDatenbankCursorDebuggingFront-End <Software>DifferenteCodeComputeranimation
Orakel <Informatik>DatenbankSharewareMailing-ListeBildschirmmaskeSelbst organisierendes SystemE-MailDateiformatDatenfeldWikiDebuggingGamecontrollerInformationBitrateComputeranimation
Selbst organisierendes SystemE-MailBildschirmmaskeDatenfeldATMElektronische PublikationWeg <Topologie>SchlussregelPlug inWikiEinsFluidFront-End <Software>DatenbankDatenfeldBitKonfiguration <Informatik>DefaultGruppenoperationWellenpaket
HomepageBildschirmmaskeFluidATMElektronische PublikationEin-AusgabePunktOrdnung <Mathematik>Selbst organisierendes SystemMailing-ListeMultiplikationsoperatorClientZweiDebuggingDatenfeldFluidGruppenoperationRechter WinkelComputeranimation
Selbst organisierendes SystemE-MailBildschirmmaskeOrakel <Informatik>DatenbankMarketinginformationssystemEinsSelbst organisierendes SystemTabelleCodeMultiplikationsoperatorMailing-ListeDatenfeldBitComputeranimation
Mailing-ListeFreier ParameterDatenbankSharewareWikiBildschirmmaskeInverser LimesWeb SiteToken-RingSampler <Musikinstrument>ServerMailing-ListeMultiplikationsoperatorMathematikBitrateServerDifferenteDatenfeldDatenbankCodeGamecontrollerComputeranimation
Inverser LimesToken-RingWeb SiteServerSampler <Musikinstrument>IdentitätsverwaltungVersionsverwaltungDateiformatMobiles InternetChecklisteWort <Informatik>InstantiierungFitnessfunktionMailing-ListeRechter WinkelComputersicherheitServerWeb SiteBitAggregatzustandSchnittmengeDefaultErneuerungstheorieComputeranimation
Web SitePhasenumwandlungInhalt <Mathematik>RechnernetzCDN-NetzwerkInklusion <Mathematik>MultiplikationsoperatorSchnittmengeServerHalbleiterspeicherWeb SiteDefaultInverser LimesTouchscreenExpertensystemModallogikt-TestComputeranimation
RechenwerkServerInverser LimesROM <Informatik>PhasenumwandlungAuthentifikationHIP <Kommunikationsprotokoll>VerzeichnisdienstComputersicherheitWeb-SeiteWikiFunktion <Mathematik>CliquenweiteSpezialrechnerCaptchaMultiplikationsoperatorMaschinenschreibenTouchscreenProdukt <Mathematik>Spezifisches VolumenWeb SiteComputersicherheitCaptchaComputeranimation
Web SiteComputersicherheitServerSchwellwertverfahrenEindringerkennungToken-RingWeb-SeiteFunktion <Mathematik>Inverser LimesROM <Informatik>VersionsverwaltungSicherungskopieRenderingSoftwarewartungMobiles InternetKeller <Informatik>Rechter WinkelMessage-PassingWeb SiteToken-RingDoS-AttackeAbgeschlossene MengeSoftwarewartungBildschirmmaskeComputersicherheitTouchscreenParametersystemMaschinenschreibenResultanteApp <Programm>BitArithmetisches MittelClientVisualisierungProzess <Informatik>RechenwerkWeb-SeiteDatenverarbeitungssystemGeradeVersionsverwaltungDigital Rights ManagementPunktGüte der AnpassungGesetz <Physik>KalkülInstallation <Informatik>Bootstrap-AggregationMobiles InternetEin-AusgabeArithmetische FolgeGrenzschichtablösungCachingZweiTrennschärfe <Statistik>ServerBenutzerbeteiligungMereologieSicherungskopieWeb-ApplikationRandwertWikiComputeranimation
WikiKeller <Informatik>SoftwareentwicklerTravelling-salesman-ProblemPunktMultiplikationsoperatorSchlussregelMereologieResultanteKeller <Informatik>Selbst organisierendes SystemSicherungskopieTrennschärfe <Statistik>Graphische BenutzeroberflächeServerComputeranimation
SharewareGruppenoperationSchlussregelDefaultGruppe <Mathematik>ViewerServerComputersicherheitPhysikalisches SystemSoftwarewartungInhalt <Mathematik>TexteditorKorrelationMAPKonfiguration <Informatik>TemplateDatenbankDigitalsignalAbelsche KategorieModul <Datentyp>BildschirmmaskeStandardabweichungGeradeSoftwarewartungGruppe <Mathematik>Komplex <Algebra>Kategorie <Mathematik>GraphfärbungMathematikOrdnung <Mathematik>Selbst organisierendes SystemMereologieExogene VariableOrtsoperatorÄhnlichkeitsgeometrieMultiplikationsoperatorUmwandlungsenthalpieMetropolitan area networkLeistung <Physik>TexteditorMAPGruppenkeimInhalt <Mathematik>Wort <Informatik>MenütechnikWeb-SeiteSchlussregelGruppenoperationEigentliche AbbildungTeilbarkeitTopologieDatenbankNichtlinearer OperatorPunktKonfiguration <Informatik>InternetworkingProjektive EbeneDatenfeldAbgeschlossene MengeDistributionenraumGarbentheorieWeb SiteInverser LimesProzess <Informatik>RuhmasseCoxeter-GruppeDateiverwaltungWhiteboardTablet PCRechenwerkDefaultVollständiger VerbandHalbleiterspeicherElektronische PublikationDigitalisierungInformationCASE <Informatik>Front-End <Software>SystemverwaltungViewerSharewareGlättungBildschirmmaskeTemplateTropfenBenutzerbeteiligungWeb logBeanspruchungBimodulTypentheorieCanadian Mathematical SocietyVererbungshierarchieGanze FunktionComputeranimation
DistributionenraumBeanspruchungElement <Gruppentheorie>Gruppe <Mathematik>Web-DesignerBeanspruchungKartesische KoordinatenDifferenteEreignishorizontDatenflussGoogolComputeranimation
Element <Gruppentheorie>Computeranimation
Transkript: Englisch(automatisch erzeugt)
Hello and welcome to blurring the lines Tiki no code low code empowers. My name is mike and I'll be speaking to you about Tiki.org software and how it empowers team members.
So let me start off first with a little bit of biographical background. You can read my biography on the FOSDEM site, it's right here. I'm not going to go over all of it but I'm just going to just mention a few things. I've worked at a few farming operations with based on Tiki one where it was a side project. Another, it was my main core project we were
doing. It was quite a large project gathering data from the field. It was quite interesting and then I've also done a number of other projects in the legal field, medical, real estate,
corporate document delivery and a few others. So let's move on and take a look what we're going to be talking about today and the top three reasons why I use Tiki. Let's look at Tiki.org on the home page. Here we go Tiki Wiki CMS groupware. It's the
free Libre open source web application platform with the most built-in features. So it does a lot, in fact pretty much everything. Why I use Tiki? Well when I started I created a spreadsheet and did all the pros and cons of all different content management systems.
Looked on their sheet here as well and of course I was looking for good strong underlying technologies, common underlying technologies, PHP, MySQL, Bootstrap and so on. And a few other things. So you can look on this benefit sheet and review a lot of them.
There's quite a few. But let me just focus on the top three reasons why I use it. And reason number one, well, no code. I don't know any coding languages so I need software where there is no coding required. Reason number two, all in one platform.
I wasn't specifically looking for this when I found Tiki but I really discovered the benefits of this later. It's particularly for enterprise use without the third-party plugin model such as WordPress or I think Joomla and Drupal also have the same thing. So it's quite
interesting. Anyways that's what the second major reason why I continue to use it today. And the third reason, Softaculous one-click installer and updater. It's a nice little thing for shared hosting. One click, well it's a few clicks but that's okay.
In general it really helps out a little bit. I have done a manual install of Tiki. The installer is pretty good and it's not that much different from the Softaculous installer but it's just nice that you know you can just do this with your shared hosting and one click
install. So those are the top three reasons why I chose Tiki and still use Tiki today. Now let's go into the next segment. Our central focus points for the talk today. Three central focus points, empowerment, engagement, and distribution of workload.
Empowerment, Tiki provides tools for innovation for your team members. Engagement, well it engages all parts of full spectrum. It engages in the people who don't know coding
languages, people who are learning a little bit low coding internal Tiki low coding language, and it also engages people who have full knowledge of coding languages. And I'll show you some examples throughout the presentation. Distribution of workload, this means from what
was before the traditional gatekeeper of your website, the IT department. Or more common today, your outsourced web host, web development company. Or maybe you have an in-house web development team. So this central point of focus also involves distribution of workload from
these three to any participant, any team member in your organization. Now I'm going to use my example as a full stack developer for Tiki. It's only one example but it's a full example. It gives you a complete picture of more examples I can show you of work
that I... more features in Tiki that I can show you. Then I want to wrap up by showing you other examples or other group types. And when I say users or examples or roles, what I mean is
groups. These are specific groups of users in a system, much like any content management system, with permissions to do certain things. Read, write, edit, view, you know, all these similar things. So that's what the two examples I want to show you. My use case
and then all kinds of others. So I think we need to move into what is a full stack developer. Let's define this. How should he refine and what is a stack exactly? So I looked on the internet, I did a long review of all different types of definitions starting with Wikipedia and many
others. I fortunately had to cut a lot of that out of this presentation. It was just way too long. But I seen this one and it was pretty good. I reproduced it and it seems to cover most of the parts. We have front-end, back-end, database, DevOps server, and mobile.
I found a common, you know, this is common theme, you know, in a lot of the explanations. And then of course the parts that they do or the languages they use to accomplish their jobs. Okay, so let's take a look at the, let's take a look at how the features in Tiki that allow me
to do the same type of work as these languages. So in Tiki we have lots of GUI plugins for page layout, design, and presentation. GUI for those that don't know graphic user interface
or more commonly known as just a pop-up. It pops up with lots of different options and you configure them. So there's no coding. On the back-end there's of course like many content management systems, management of users, groups, permissions, modules, menus,
and things like that. And Tiki adds integration and automations which some of them have, some of them don't. Tiki has databases built in, they're called trackers. It's not a third party,
it's a very large major component of Tiki called trackers. And of course you can create your own trackers, you can link the trackers, structure them. For instance they call it the snowflake schema or the star schema. And of course you need to do things like import and export and backup, things like that with the databases.
Next we have DevOps server. I'm going to focus on the server side because that's what I do sometimes. I troubleshoot the server, I look if there's any error messages, maintenance, do a few things, scheduling, or performance. There's a few things I want to
cover there. And finally mobile. I'm not going to speak too much about mobile, and there's a reason why I'll get into a little bit later. But in the mobile side, Tiki has Bootstrap and Progressive Web App. We'll get into those a little bit later. So these are the parts of Tiki that relate to the parts of a full stack developer's job
and the languages that they need to know. So before we go further, I just have a few final notes on this before we start the main part. I am greatly oversimplifying each part here.
Because of time constraints, it's not always clear-cut. So big respect to all the developers and all the front-end developers specific, the back-end specific server people. I don't claim to be able to replace all of them all the time. No. I have a certain role that
I play as well, just like a front-end specialist or a server specialist or DevOps or a mobile. It depends on the size, the duration of the project, complexity of the project, budget of the project. So there's a number of factors. Like I said, later I'm going to go into what the roles of Tiki full stack developer can contribute. So let's start with the back-end.
Okay. So let's begin with the back-end or the admin section. I always start with the admin when a new Tiki install. The reason why, of course, is when you build a house,
you start with the foundation, not with the paintings on the wall or the furniture. So, and that means in Tiki, we start globally with the control panel. This is what the control panel looks like in Tiki. Here we have all the major features and here you enable them.
For instance, trackers. That's why it's blue as opposed to gray. It's enabled. And then you set the global macro parameters within trackers. We'll look at it a little bit later. And then here, settings, is where you set individual. Here you can see just a little
to the left is a web services here. That's where you enable it. And then here is where you set up individual actual web services. But not everything is here in settings. Trackers, you set up here and I've got this one here, right there. List trackers. This is where you
set up individual trackers or databases and you manage the individual databases. So not entirely just here and here. That's the control panel. Now, Tiki has all the basic features that any CIU would expect of any basic CMS. Groups, users, permission management,
all that. Menus, modules, languages, themes, quite a bit. All on a granular level. And I'm not going to go over all that or even attempt to because there's just way too much. Instead, I think it's more appropriate on the backend if we just accent a few parts of backend
which are really relevant for today for the times that we're in right now. And that's automation and integration. Plus I'm going to have one bonus preview of a new feature coming up as well. So let's start with automation. What do we have in Tiki? Well, plugin list execute and scheduler. Two very powerful features that work hand in hand.
Let's look at plugin list execute. An extensible plugin allowing administrators to set up listings and custom actions that can be executed on objects, allowing to support complex workflows and perform some level of automation. Okay, well you can see that they're a little
understated there. First thing you'll notice here on the documentation, sample usage. Well, we're into the low code side already. This is not the no code side. So it's a bit more advanced, of course. New users wouldn't be starting off with this. It's the Tiki list language,
internal list language, very readable, far from coding, but in that direction. So what can you do with plugin list execute? Well, let's see our first example, change a status. In Tiki, the default are three statuses, open, pending, and closed. And you can change it
from open to pending, pending to closed, or whatever you want using list execute. You can delete an object, an item. It means an item, a file gallery item, a tracker item, a database item. You can do quite a bit. Change a file gallery name, email, of course. So this, you know,
and modify tracker items, tracker once again, database item. And there's a lot of fields that you can modify. We're going to go over the fields, the database fields or tracker fields later a little bit in that section. They're extremely powerful. So I'm not going to go over this in too much detail right now. Simply just want to end up this section here with one example
at the bottom here. I thought it was kind of cool. Here it is. This is a list execute here. It's kind of long, so it's quite an advanced example. Things you can do with it are quite advanced, yes. Now that works well. It works well hand
in hand with something called scheduler, also a GUI in Tiki. Scheduler for Tiki or cron jobs. An internal scheduler was added in Tiki 17 so that only one cron tab needs to be defined
in the system cron tab, like on your virtual machine or hosting. And all actions to be run at scheduled times can be defined within the Tiki GUI. And here's some examples. So rebuilding the index is a common one on a website. You usually want to do it nightly
to keep it in good shape. Test notification email. So this is sending an email. So this one has three internal, example of three internal scheduler cron tabs set up. And on the server,
there'll be only one run every one minute or five minutes or something like that. So this allows you to, this is also the lines are a little blurred because this is also in the server side, the scheduler, as you can see, not just the back end GUI side.
This is what the scheduler looks like here internally. You give it a name, description, a task. I believe most of the time it's counsel or shell. I don't really to understand this too well. I read the instructions every time I set this up and that's it. Status active or inactive, you can set it up as run if missed, run only once. So it's not too complicated. It's quite
easy actually. So that's list execute and schedule. You can see how list execute scheduler go hand in hand because one initiates the action and the other completes the action. Okay, let's move along to the integration side. Integration, we have plug-in web service.
Plug-in web service use this to pull data from any JSON or SOAP enabled web service. And this of course is very popular nowadays. And I'll go right to the bottom here for one reason,
monetization. Web service or APIs are used a lot of times, very popular nowadays, because companies are finding that they have lots of data they're gathering and they can resell it. So that's how it's a monetization model, why it's being driven, why web service and APIs are
expanding in popularity. Why do you need a web service? Well, to integrate with other websites, exchange rates, weather of course, shipping or transportation data, environmental data, legal,
your IoT devices. Lots of reasons why you'd want to integrate all this information into your website. And I just want to give a shout out to this site, Programmable Web. I have nothing, no affiliation with them, but I just like this one. They say they're an API directory here,
and they just give lots of information about APIs. Very, very on top of the ball here, they want to position themselves as a specialist. Every day they have new daily roundup, that's a good one, huh?
They have a daily roundup. Walmart, if you work as a supplier to Walmart, you'd like to hook up to their supply system to understand how much of your stock is left at Walmart so that you can replenish it. That would be quite beneficial, I think. Anyway, so that's just a shout out to their website because I think it's really nice, I like it at least. And lastly, let's just take
a quick sneak peek at the preview. New backend machine learning is coming to Tiki as well. Like a lot of websites, it's going to be integrated in Tiki 23. We're on Tiki 21 right now, so it's
still a little ways away. But you can look at the documentation, it's quite comprehensive right now for beta testers. And it's got some nice screencasts here. I'm not going to go into what it is here, you can read all about it yourself, but they use Rubik's ML, integrating Rubik's ML because it's PHP-based and Tiki's PHP-based.
So here are all the screencasts on how to get started, set it up, but expect issues and bugs because it's not even out of beta yet. But this is quite nice to see such good documentation at this point in time. So let's move on now to the front end. Okay, now let's proceed to the
front end. You know, it's a fun kind of a visual type of tools. And I created this little triangle
here. We have in Tiki, we have on the bottom layer basic tools or just wiki syntax like in any wiki, other wiki, XWiki or Dacowiki, or just like even in Word or Excel. Secondary tools, I call them midweights or about content and design plugins.
And then the top level tools, more site and page layout. So let's begin by looking at the basic ones, which, you know, this is for the low code side, or excuse me, the no code side. You know, it's got a basic wiki syntax header. You can look at the documentation on a wiki,
but let's have a first-hand look right here and let's look at this page. Okay, so what is this page made of? We got a bunch, we got a toolbar on top, just like Word and Excel. And there's buttons here which you push. And we all understand what these are, bold, italic, strikethrough, color, foreground, background, and so on.
So that's just what you do. You just write a word, highlight it, and hit bold. And it automatically adds these two underscores before and after, not rocket science. So that's, and here I'm doing this presentation. How am I breaking up these pages? All it is is three dots, the word page, and three more dots. Here's one page,
here's another. Quite simple. I think anyone in an organization can do that. This is the picture right here, an image. I've inserted an image. We'll talk about that plugin, but that's more of a plugin. This is just Wiki syntax. And of course, this toolbar can be arranged any way you like, just like you arrange on Word or Excel or any spreadsheet
or other document writer that you use. So let's start with, that's the basic Wiki syntax. Let's move on towards the second part, the midweights or the secondary tools. I use these
quite a bit for page and content design. There are different midway plugins, I call them, because they have a, you know, some have a lot of features to them. Here we have plugin button. I'm just giving you examples, a surface, just touch-scratching
the surface of examples. Plugin button, and I created a button. And all the documentation, you can just, you know, look yourself on the doc site, doc.tiki.org gives you a little explanation and then gives you all the parameters and the defaults here, if there is any default.
And there's different types of buttons here you can do. You go there, go there, you can put icons in buttons and so on. Okay, so I created one right here to go to the full stack developer page. Here we got plugin icon. Before I go further, let's stop right there and let's show you the GUI for this. You notice the little puzzle piece right here,
and here, and here, and here, and here. That happens when you toggle the icon switch. Off, on. Okay, when it's on, you can go in and edit the configuration for that
object, the button. And here is a button GUI. So URL, it can be an internal, and I have a page in my wiki called full stack developer, so I don't need to put the full URL. It's better not to hard code them here if it's internal for upgrade and update time. However, you could
have an external site, HTTPS, blah, blah, blah, to any website, any page. Give it a label, and I gave it a label. See, full stack developer icon name, button type, you know, there's different primary success, warning, and so on. So this is an example of low code.
It's not very difficult, it's very readable. You just, however, at the same time, this is also for the coders. Here we have CSS class, CSS style. I've had difficulty with this, I can't get these to work very well, but a person who is a HTML CSS specialist says, hey, why not? That's easy, here you go. And they can custom create any button they like.
Advanced, and there's more, more features here you can add, okay, and just hit save any changes, and you can put stuff in the body as well. That's what a GUI looks like, and they're all kind of the
same. Let's look at this one for a database icon. Okay, this one doesn't have so many, so much configurability. It's got the name of the icon, the size, rotation, and style. Well, that's okay, it's a simple one, but I like the icon sets. So let's exit, let's exit that,
and make it a little cleaner. Plug-in tabs, I love this one for space savings. In the first tab, I've got icons starting with the letter A. The second tab, I've got icons starting with the letter B, battery. So what I've done is I've put an icons plug-in inside a tabs plug-in,
so you can put plug-ins inside of plug-ins. Okay, plug-in fancy table. This is for small amounts of data, quick, fast tables, and that's it. You can put a table sorter like Excel on top, you know, the filters on Excel, but I didn't do that on this one. It's just a static example.
Plug-in fade, simple plug-in fade. It just has a common triangle to open it, and this is a bootstrap integrated fade. You can put lots of information in the fade to save space on your website, optimized space. Even something small as plug-in mouseover.
So what do you think about this no code, low code? These are what I call the mid-weight, like I said, plug-ins because they have a fair amount of features. Now on the top level, we start, I'm working from the bottom up here again. Of course, you're going to want to start
your site globally by configuring the, in the control panels, the look and feel. The look and feel has many different parts, starting with the theme. I like flatly. There's many different themes here. I got a thing with flatly. It's really
elegant, I think. Blue has a sub theme, dark or light, and so on. Lots of options, layout options, fixed width. I don't like fixed width too much, but you know, maybe you do. Pagination, UI. Here's one for decoders. Customization. Custom CSS class. You could
add any CSS you want right here and completely override everything. Make it a custom site, custom HTML head content, custom JavaScript. And the reason why it's best to do it here,
as opposed to the files in your file where your site is located, because these won't get overwritten when it comes time for updating and upgrading. Those could get overwritten. So that's the global look, global location for the look and feel parameters.
And so then you look at where... I'm just showing you a few of these. I'm sorry I'm speaking so fast. I'm constantly looking at the clock, making sure we're pushing forward on this. Lots of information to cover. Plug-in fluid grid. I love this one recently. I've been using it quite a bit, and this allows me... If I didn't use plug-in fluid grid right here,
here it is. Plug-in fluid grid. If I didn't use it, all this data would be pushed over to the left, and I don't really like that. I like it centered. Plug-in fluid grid, as you can see,
the examples creates two rows to equal column widths. Starts with a fluid grid like that and ends with a fluid grid like that. So there is a GUI, but a lot of times I just cut and paste. I don't even bother with the GUI anymore. I'll cut this fluid grid in and paste it in there.
This is fluid grid with column size 6222, and they have to equal 12, because I think it's from Bootstrap. It needs to equal 12, 12 columns. And this way you can put information anywhere on the page, rather than just on the left side or left aligned or right aligned.
Plug-in div is a bit more advanced. That's for the even coders. I haven't used it too much. I'll use it inside a div, mostly for giving it a background color, giving the box a background color. It's got the CSS class here again, HTML ID, title attribute, role attribute,
so it's a bit more complicated. But HTML CSS people will immediately recognize the word div, and this might help make things faster. Plug-in layout is specifically for splash pages. It
overrides all the modules, maybe on the left hand and right hand side. And it is not working today. That's okay. But it overrides a lot of the modules on the left and right hand side, if there are, for splash pages. And finally, we've got simple things like
plug-in slider, swiper, and carousel. Here I've got a slider, I believe. It goes automatically, or you can click on it, go back and forth. Nothing fancy, but just nice tools with a lot of flexibility. Let's move on to databases now. Okay, let's move along to trackers
or databases. They're called trackers in Tiki. Once again, we start globally with the trackers in the control panel. And I've already clicked forward through here, and we can look at the
global features. We have the check mark just to activate the feature right here. And this is cool. The question mark takes you right to the doc section. Anywhere all these little question marks takes you right to the section inline editing. What is inline editing?
It'll take you right to that part of the documentation page if there is something available on it. So here we have a million features I'm not going to really go into, and lots of plugins within the trackers. And here I just discussed, I mentioned a little earlier, the field types. Tiki has like, I think, over 50 different field types. You know,
the standard drop down, of course, date and time picker, currency field files. This is for attachments, groups, item link. That's for linking two separate trackers. Item list, listing from another tracker. Very important for, and this one right here, mathematical calculation.
Extremely powerful for creating formulas. So for the people in the advanced Excel crowd, the people who do advanced formulas in Excel, this is what they're going to be really interested in. Multi-select and so on. I'm not going to go over all of them, but there's quite a few,
you know, options and configurability within trackers. Now I'm going to go do two things today. I'm going to create a demo tracker called project management with just two fields, and I'm going to demo a working example on the front end and the back end. This is the back end, okay, tracker. So we've enabled it globally. Now here we're going to create an individual
tracker. So what do we do? We just hit create and give it a name. Let's give it a name. Project management. I spell that right correctly. Features, there's a few. Sometimes comments,
I like allowing comments. Very important to tracker items. Display, I like showing the status always ascending with order and so on, and save it. Quite simple, all GUI based. This is for the low code, no code crowd. Project management, there's our new tracker created.
Now the first thing we want to do is we want to give it some fields. Let's go in and add some fields. What did we say we want to add? Field of a date and a name. Name of the project and date of the project. So similar here, add field. Click. Pop up, give it a name. Name of
project. Let's leave a text field and here's all those enabled. We talked about drop-down or files earlier. Item list, item link, these are all the enabled fields. And add the field. There it is, name of project. Now let's add one more and call it,
we call it date. And we're going to use a date and time picker, the more advanced one. And add the field. Alright, one other thing I'm going to do, actually I want the date on top
and I want it to be listed. So I'm going to click list, shown to me, otherwise it's not going to be displayed in the back end. And I want to move it. You notice how the cursor changes? I want to just drag it and drop it up there to date. Date first and then name of project.
And then I've got to save those changes. I just drag and drop, save all, go. Alright, now let's look at the items in the tracker. There shouldn't be any items. We haven't done anything, we just created it. Here we go. We're working in the back end, okay? And I'll show
you where it's best to work in the front end for users, end users. Automatically, since I gave it a status, assigns it an open status as opposed to pending and closed. Date, let's pick the date today. Done. And name of the project, let's call it new project. Ah, new article.
I'll be writing a new article on no code, low code coming up, so I want to create a new article and create. There we go. We've created a new database called a tracker.
We gave it a couple fields, and now we're even seeing it, and we've entered in information. So it's not very difficult. Pretty much anyone in an organization can do that. Now let's look at an example. Let's go to the trackers. Let's look at an example of a completed one. I have one on my site here. It's a new site. I'm rebranding a bit.
Called contact, contact us. Okay, and let's look at the fields first. What types of fields do I have here? Well, first name, last name, organization name, business email, telephone. How can we help you? And importance. Okay, these are all listed so I can see them in
the back end. It's different from the front end, and these are all mandatory. Business email, organization name, last name, and first name. Okay, let's look at it first in the back end, and let's see what we have here because there's some items I entered in here.
Just testing and others. There we go. All these fields are listed. Okay, now let's take a look at it on the front end or the wiki pages. This is important because when you put it on a wiki page, you have much more flexibility and control over the fields and the options of it.
Who gets to see what? And this is what it looks like on the front end. Okay, contact format. I put all the fields except that last one. I believe it was called fields rating, importance,
importance. Okay, and the reason why is importance is an internal field. Once the user enters in their contact information, sends it, then internally I give it an importance. And let's take a look now what it looks like. This is a GUI once again, so here is
our plugin tracker. Let's click on the puzzle and take a look at this. There it is. I chose tracker ID contact as opposed to all the other ones in my setup databases. These are the fields I've chosen. You just drag and drop these around. Action, I chose send. The default is
save, so the button says send instead of save. And there's lots of other options here as well, and advanced options. So none of this is very difficult to do. It just takes a little bit of training, that's all. And this is what the plugin looks like in the back end here,
on the wiki page. Here we go. I've got it in a fluid grid, so I'll plug it inside a plugin. So ignore the fluid grid and just look at the tracker. Tracker, field ID 4, fields 2021,
22, 23, 24, 25, action sent, and so on. And a lot of times I don't even use the button. Here's the button for tracker right there. If I were to put one in right here, it would create a new one. Let's try it. There it is. It's empty. All the fields are empty,
so let's chart the contact clients. Then it will show me some fields. Hang on a second. Ah, wrong one, contact. Then it'll show me the contact field, last name, first name, organization. I can choose them, and so on. This is quite easy. Of course, that's starting,
and then as you develop, you want to create more advanced examples, okay? So pretty much anyone in an organization can do that as well. It just takes a little bit of practice. And then let's finally take a look at, on the front end, a list of those items,
because a lot of times you're going to want to show the listing, the tracker list, not in the back end, but in the front end, because you're going to want to filter it. And I filtered it here. Organizations who have contacted Agility No Code. That's my company.
And here we see on top, we have the tracker table sorter, much like Excel. You know, you can choose which ones you want, and it'll filter right away automatically on the fly. It's a really nice feature. Importance, and here, since this is an internal list,
you know, I'm showing this field for myself. Low, medium, and unassigned. This Larry guy keeps calling me and bugging me all the time, but you know, I just don't have time for him. This Bill is a little bit nicer guy, you know, a little bit, but still these guys keep bugging
me all the time. Of course, I'm joking. So that's what a tracker list looks like, and let's take a quick look. And there you go, tracker list. Tracker list ID four, and many times, like I said, I just copy and paste it, you know, right where I want from
another page, and just paste it in and change some things. Tracker five, and fields I'll change, you know. That's how I'll do a lot of times instead of start a brand new tracker, hit the button, tracker, tracker list. So there you have it, a demo, and a creation,
and a working of databases within Tiki for the low code, no code crowd, excuse me, I keep mixing it up, no code. Okay, let's check out server now, and what roles do I do in
server? What do I do in server? There's a few different things here. Of course, you start globally once again with the control panel, and there we have a few things. Performance and security, mostly what I'm going to talk about. Server fitness check, I would love
to show you. It's a neat little thing, and I look for things, a long laundry list of things, checklist, and I just look for things that are incorrect there. I can't show it to you right now. I screwed up my site a bit to self-inflicted wounds, so I can't show you, but it's something I highly recommend. I can show you where it's at right here under the very first tab, general,
and right there, server fitness. You can click that, and it just gives you a long laundry list of items about the state of your server. So I'm going to move on to performance and security. For performance in the global settings, I really don't touch much here, actually. I go with the
default settings. I don't like to screw with this because I'm not too familiar with a lot of this. However, your server specialist or a person who has server specialist knowledge outside the IT department could very well easily set some of these if necessary. Really, the only thing I
look for is time and memory limits, PHP execution memory limit, PHP execution time, tracker item export memory limit, so exporting. Set a limit. It's good to do that, and mostly the export. I don't have them all set. Like I said, it's a new site. This way, you don't end
up in a blank screen of death forever. It stops. It times out. Under security, also, I don't touch too much. I don't have SSQ, SSL, interesting. I'll have to look into that, but I don't touch too much here either because it's best not to touch things. Smarty security is enabled.
Everything else, I don't touch. I just make sure I didn't make sure protect all sessions with HTTP PS is enabled. Anyways, I'll look into that, but I don't touch much here because it's best not to. Spam protection, you can use. I have a little security question here
on spam protection. There's CAPTCHA and RECAPTCHA, and depending on the volume of your site and how often it's, let's say, attacked, well, it might work. It might not work. Here's one thing that's really good. Site close. If you do have a problem with DDoS attack
or something like that, you can close the site right away, and it puts out a little message right away, so that's nice. Or if it's on maintenance, this is really helpful. Tokens, you can give somebody temporary token access, and so on. I don't do too much in performance and security, so I try to leave it like it is. The last thing I'll say here
about internally in Tiki about the server packages, they're using Composer. A lot of this crowd will know Composer as a package manager. I descend from the Tiki Viewpoint because Composer actually is going towards the line of WordPress and third-party plugins, and I don't
really like that too much. It adds a lot of complication. They're all open source, but still, it adds complication and unnecessary. It's done because of licensing issues, to avoid conflicts
in licensing issues. LGPL and Tiki and then all others. So it's not, you can install on your own site whatever additional packages you'd like, but it's not there as a default. Externally, what do I use outside of Tiki? Well, of course, I use cPanel. I use Softaculous
one-click installer and phpMyAdmin for selective backups. Okay, so that's it for the server. Let's move on to mobile. Mobile. Well, there's not a whole lot here that I do either, also. And the reason why, Bootstrap. I love Bootstrap. It's pretty good. It does an amazing
job of rendering on all size screens, and you'll have descending thoughts and, you know, contradictory arguments here. HTML, CSS people don't like it because it's a bit restraining. For me, since I don't touch or go outside the boundaries much, it's perfect for me. And it
resolves 95% of issues on mobile sites, so you don't need a third-party app. You don't need an Android or iOS app. And I always try to persuade clients from creating separate apps because Tiki works so well because of Bootstrap. There's no need for a third-party app, and it increases
security risk and maintenance. Now you have to maintain that app for both security and maintenance, both iOS and Android, if you're doing it. And the second thing about mobile, Progressive Web App. It solves the remaining 5% of issues which an app, an external app,
would do typically. Meaning, as long as you've downloaded the page, the wiki page, with a tracker on it once, and it's in the cache of your computer or your smartphone, then you can continue adding new entries. And once you're online, due to Progressive Web App, they'll be uploaded
automatically once you're connected online again. So this resolves the remaining 5% of apps. I'm oversimplifying again, of course, because apps today do quite a bit, send a lot of data back and forth a lot. But generally, if it's a basic app, a simple app, I try to advise clients against it.
It's just not worth the security or maintenance issues. Now, we've discussed all the five parts of the stack. Let's look at my stack quickly. I use a stack called a TCSP. Tiki. Let's go back here.
Tiki, of course, is the major part of it. cPanel, all GUI. And if you don't have cPanel, of course, you have a VPS server. Then you have VirtualMin or Webmin, which is also GUI-based.
Softaculous, we've talked about a few times. And phpMyAdmin for selective backups. You have to be careful about this because you can get into trouble with this. It'll delete certain tracker items that are linked to others, but you don't delete those other ones. You could be left hanging. So let's wrap up and let's discuss the roles of a Tiki
full-stack developer. How can this be deployed in your organization, if there's a full-stack developer at the top, let's say? Well, you can very quickly create realistic demo databases. Speed is a lot more important, I feel, in my opinion, than in
business and in operations today, fast-paced world, than a super detailed, complicated, nice full example. You can create entire digital initiatives, small and medium-sized initiatives. Or a Tiki full-stack developer can complete the groundwork for a larger project as a team member.
And this will help you to reduce costs on the correct, like a proper full front-end specialist, proper backend specialist, proper database specialist. Their salaries, if they're really good, are going to be high. And so if you have someone like a Tiki full-stack developer,
you can significantly reduce your costs. Plus, I don't think those people are going to really want to do a lot of the basic, mundane work. So those are the roles of a Tiki full-stack developer. Now let's finish up one last part of this presentation today. Groups or user roles,
other roles other than a full-stack developer. I divided this up into four parts. Default groups, typical groups, or the have-to users, innovative groups, the want-to users, and then I'm closing with unleashing innovation. Okay, start with default. Okay,
there's nothing new here. You have anonymous, which is not a group really. It's just pages or sections of your site that you label as anonymous. And anyone of 7.53 billion people with access to the internet can't see that page or site or information.
Registered and admin, those are the standard groups. You can have unlimited groups in Tiki, but be careful of what you wish for. You may get it, and that's a lot of maintenance if you go overboard and create a lot of complexity. Typical groups, these are the have-to users that I call them. And you know, we all like to think that everyone
in your organization is innovative and rah-rah, go-go, but there are a lot of people that just do their job well, but they like to stick to their job. Okay, that's fine. There's nothing wrong with that. And so you have a lot of groups such as viewers or editors or content maintainers,
data entry or reviewer of data entry to make the quality of the entry much, to review the quality of what they've entered to improve the quality. And then you've got your traditional admin, more technical, more server focused, you know, keeping things running smoothly.
Now let's look at the innovative groups or the want-to users. Okay, these are who want to use Tiki or whatever CMS you're using, but in our case Tiki. Power users, they maintain and update databases, drop down items that change the categories maybe or options they are available.
They'll improve databases by adding new fields, new drop downs, new radio buttons, new files, fields, new attachments, files, fields. They'll create new templates for web forms and so on. Or on the top level of power users, they'll just create entirely new databases for new
digital initiatives in your organization. Another way, another bunch of groups, what I call them are features maintainers. Assigning a specific part to a specific person within a specific department, blogs or news, maybe to the corporate social responsibility department, CSR.
Comments, it could be anything, HR, who knows. Calendar, that would be more HR, I think. File galleries, you know, we all like to think that we're all professional and we can, our files will be maintained, we'll all be stick to the guidelines and maintain nice
neat orderly file system, but that just doesn't happen. It's best to assign someone to kind of remind people and keep after and keep those file exchange in order. Tags or categories, nice introductory position, tagging everything so that you can be easily referenced. These are
nice maintainer features, introductory features to Tiki where people can learn and grow on and then you can switch to another one possibly and learn and grow because there's similarities within Tiki. And the last one are lower level admins. We can have someone manage the users,
groups, menus, modules, toolbars. So we're going back to our original page, original three parts, distribution of the workload. There's no reason for IT to be managing the users or the groups or the menus or modules or whatever. And there's no need for a super admin to be managing that
either. Spread out the responsibilities and the permission levels. And this way you engage more people to your website, your CMS and you empower more people with these types of innovative groups. So in closing, I just want to say the last few words here of unleashing your innovative
groups puts you on a path of course to empowerment, greater engagement of those team members that you have and advancing your skills of those team members by those features groups and different groups that you create. They'll learn slowly by practical application. And of course,
it distributes the workload from your IDT department, your outsourced web development or your internal web development company. So thank you very much for listening today. I
hope you enjoyed the rest of your day. I'll see you in the next one.