Hi Anselm, On Tue, Mar 10, 2020 at 2:57 PM Anselm Lingnau <[email protected]> wrote:
> Fabian Thorns wrote: > > > Please share any thoughts, ideas, considerations and comments in this > > thread or reach out to me personally in case you don't want to speak up > in > > public. If you'd like to help with item or learning material development, > > please reachout to me or Markus directly, too. > > This looks like fun. I could totally see myself writing a manual for this > exam > under the auspices of the tuxcademy project. > Awesome :) As far as the choice of topics is concerned, I would personally welcome > something that asks for awareness of the common security issues > surrounding > web applications, and also something that mentions architectural patterns > such > as single-page applications, which are IMHO much more important from a > practical POV than, e.g., WebAssembly (of all things). There doesn't seem > to > be a mention of REST, either. > Adding awareness of single-page applications and RESTful APIs is definitely worth some more thoughts. What do others think? If the plan is indeed > > > to cover the most important aspects for the topic and teach just enough > > feature to implement a simple sample app in a course. > > then IMHO the CSS content stipulated (especially by objectives 033.2 and > 033.4) is over the top – it would take a lot of time to teach compared to > most > of the rest of the material. Instead it might be more practical to cover > the > essentials of a popular free CSS framework such as Bootstrap. > We tried to avoid frameworks as much as possible since it is complicated to pick the "right" framework and frameworks tend to be changing more than the actual base standards. That's why we tried to focus on core CSS features. Based on the same rationale I would probably lose the <video> and <audio> > parts of 032.3 – they don't add a lot conceptually, tend to bog one down > with > deciding what codecs one should support, and frankly don't make sense > unless > the “sample app” at the end includes video or audio content (which, having > personally written web applications that deal with video and audio, I > would > consider to be incompatible with the adjective “simple”). If that makes > the > “embedded resource” portion too light, then <img srcset="…"> might be more > useful to pad the objective, especially with a view to responsive design. > Or > one could talk about SVG a bit. > Good point, more opinions on this? > Finally, seriously, Express? Cringe. I can understand why this looks > attractive if you're already talking about client-side JavaScript, You got it :) but if I do > write a manual it'll probably have an extra chapter on Django just so > people > get to see how this is done properly ;^) > What about Laravel? Spring? Rails? I'm sure we don't want to open that can of worms, and you (along with Ingo and Jeroenn) got the benefit of introducing candidates to the overall principle of server-side development without introducing another language. JavaScript is set as *the* frontend development language, adding another programming language would certainly be beyond an Essentials exam. Fabian -- Fabian Thorns <[email protected]> GPG: F1426B12 Director of Certification Development, Linux Professional Institute
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
