Skip to content

Commit 30c90ec

Browse files
authored
Update index.adoc
Addressed VJs issues - #5 (comment)
1 parent e57a6f8 commit 30c90ec

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

en/modules/ROOT/pages/index.adoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,34 +7,34 @@ CAUTION: {wip}
77

88
This website gathers all the courses offered by the {lv} CTI.
99

10-
== What is the CTI
10+
== What is the CTI?
1111

1212
CTI stands for the Community Training Initiative and the idea is to make LabVIEW available to Anyone, Anywhere and it is as simple as that.
1313

1414
It is currently concentrating on open-source training materials and low-cost training platforms, hopefully removing the cost of entry to the world of graphical programming.
1515

16-
It currently consists of a website for the course materials (here), a downloadable virtual machine image with LabVIEW for Linux loaded (kindly hosted by https://gcentral.org/cti/[GCentral]) and firmware to convert a Raspberry Pi Pico into a https://en.wikipedia.org/wiki/SCPI[SCPI] https://en.wikipedia.org/wiki/VISA[VISA] Instrument.
16+
It currently consists of a website for the course materials (https://labviewcommunitytraining.github.io/www/en/set-up.html[here]), a downloadable virtual machine image with LabVIEW for Linux loaded (kindly hosted by https://gcentral.org/cti/[GCentral]) and firmware to convert a Raspberry Pi Pico into a https://en.wikipedia.org/wiki/SCPI[SCPI] https://en.wikipedia.org/wiki/VISA[VISA] Instrument.
1717

1818
As mentioned before everything is open-source and hosted on our https://github.com/LabVIEWCommunityTraining[github page]
1919

20-
== Why the CTI
20+
== Why the CTI?
2121

2222
A software language needs a healthy eco-system to thrive, and back in late 2022 Steve Watts wrote an article exploring the sad state of the https://forums.ni.com/t5/Random-Ramblings-on-LabVIEW/The-LabVIEW-Eco-system/ba-p/4268997[LabVIEW eco-system]. In it he highlighted the poor support available for people just starting out their careers. Which led onto the high cost of entry to anyone wanting to put on a training course, which led onto the fact that only people with considerable resources could give a LabVIEW training course... this was a wrong that needed righting.
2323

2424
This problem was raised in a CSLUG Meeting in https://www.youtube.com/watch?v=TbfEZv_zTSw[March 2023 from 56 mins] and discussed in a virtual coffee meeting in June 2023 where the VISA Pico firmware idea was discussed.
2525

26-
== Who's behind the CTI
27-
The trouble with a list of contributors is I will miss important people out, github and the discord server is the best place for up to date info.
26+
== Who's behind the CTI?
27+
The trouble with a list of contributors is important people will be missed out, github and the discord server is the best place for up to date info.
2828

2929
The initial idea was from Steve Watts who now works on hardware platforms and new course materials. The original course material was written by his daughter Poppy Watts.
3030

3131
Derrick Bommarito made the VISA firmware for Pico.
3232

3333
Georgios Tsalavoutis massively improved the Virtual Machine and gave us the logo.
3434

35-
Fabiola De la Cueva, Olivier Jourdan for re-organising the documentation.
35+
Fabiola De la Cueva, Olivier Jourdan were responsible for re-organising the documentation.
3636

37-
Nancy Henson distilled the whole idea into "Anyone can learn LabVIEW Anywhere 😊", this really focussed the focus of the project
37+
Nancy Henson distilled the whole idea into "Anyone can learn LabVIEW Anywhere 😊", this really focussed the aim of the project
3838

39-
Enrique Noé Arias, Tim Robinson, John Medland, Norm Kirchner,
39+
Enrique Noé Arias, Tim Robinson, John Medland, Norm Kirchner for all of their many and varied inputs
4040

0 commit comments

Comments
 (0)