Meeting minutes
Setup and Review agenda
Check in for repo restructure project
<Jem> https://
<Jem> mck: one huge step moving all the examples are done.
<Jem> ... hopefully the preview can be available.
<Jem> all the contentsa are moved.
<Jem> pratices, patterns, and index are all move.
<Jem> I am fixing all the broken links.
<Jem> .. has PR for that.
<Jem> merge those fixes to "move" branch
<Jem> .. the broken links in 17 subdirectoris under pattern was found and I can finish those by tomorrow morning.
<Jem> ... no css in patterns nor in examples
<Jem> ...css available to pattern also should be available for aria practice repo.
<Jem> seth: it makes sense
<Jem> mck: once I fix all the broken links, then matching css -either shared or modified can be available to the header tag.
<Jem> .. images in production exist only in Jekyll repo. jackle repo should not be the source for the images
<Jem> ...images should be under correct folder either sub- directory/images - not that I prefer this structure, image folder should be consistent through out the site.
<Jem> patterns directory in content repo, there is no pattern.html
<Jem> ..those only exist in Jekyll folder
<Jem> one option can be having the pattern-template.js can auto generate the pattern index file. The point is having the same workflow like index.html file.
<Jem> seth: ultimately this site is built as Jekyll site.
<Jem> .. using template langague liquid in Jekyll using the loop can be done.
<Jem> that is ultimate goal.
<Jem> there is no reference to Jekyll, it is all html file.
<Jem> seth: as far as we have a distinction between content and presentation,
<Jem> gitraw can be viewed as html
<Jem> mck: I like the way how we generate index now.
<Jem> .. it would be cool if there is a way to add liquid mock up template and contents get generated automatically.
<Jem> mck: generation can happen in content repo and presentation can happen in Jekyll
<Jem> seth: so you would like to see chages in the local by using command. That is doable.
<Jem> seth: current things reference tables - custom generate script.. eventually we can have one script to generate all rather than going all different script to generate content
<Jem> mck: goal is simplicity, simplicity
<Jem> .. I have a concern about move branch.
<Jem> group is discussing missing index file and other index files under content folder.
<Jem> mck: we would need members to check netfly site with correct css and links.
<Jem> ... is preview available next week?
<Jem> seth: Alex may be able to give the answer by the end of meeting about preview.
<Jem> mck: If preview is availble till next week, I wonder whether you have a bandwith to do QA.
<Jem> seth: there are some works to be done by next Tuesday so following tuesday - Oct 4 -will be better for the review work.
<Jem> https://
<Matt_King> This example page for switch:
<Matt_King> https://
<Matt_King> This is old version with bug:
<Matt_King> https://