use web components instead of material design

[btopro]

then we could provide design assets for the site that other apereo projects could easily repurpose for their own microsites

[ChristianMurphy]

It's a promising idea.
What components are you envisioning?

[btopro]

some basic ones...

• apereo-project which if you set project="sakai" display="stats" it could present sakai stats w/ the appropriate logo and branding / color consistency of that project. then a grid of apereo-project's gets really easy to build and present
• really all the assets, we've been repurposing things from static websites like https://odl.science.psu.edu/ (which has a lot of web components in it) into other sites.
• app-layout / polymer elements implementing paper would net the whole material UI stuff anyway

Could also get a more 'edit the file and your done' approach instead of Jekyll which requires a build routine (yes I realize my own approach requires a build routine to get going but once you have the components it's all static + json files)

[btopro]

project listing

click a project

click access which shows the project's micro-site that could contain documentation, community org structure, etc.

These screens are from something I'm calling HAXCMS which is a lightweight system for stamping out micro-sites using https://github.com/LRNWebComponents/json-outline-schema to structure the sites.

Kicking ideas around w/ stuff to steal from things i'm already working on actively so I can justify working on this some as well ;)

[ChristianMurphy]

https://github.com/LRNWebComponents/json-outline-schema

😆 It looks like we've been solving similar problems, checkout https://github.com/vfile/vfile-reporter-folder-json
Opened https://github.com/LRNWebComponents/json-outline-schema/issues/2 to see if there is opportunity to collaborate on a structured json representation of a site.

[btopro]

ha, that'd be awesome. We've been wiring stuff up to json outline schema for a few months and just bothered to document it and write it up recently. I think we have much to discuss on IM i'll jump on slack :p

[ChristianMurphy]

I think using paper components in the layouts could be a good starting point.
I'm open to more advanced components making their way in.
Pull requests are welcome!

[apetro]

Love the idea of Paper components in layouts as starting point. Baby steps, preferably without leaving folks like me (hey, I'm comfortable editing a Markdown file) behind. Make it better, and then make it more better.

[btopro]

we had an early prototype of a content player which would wrap everything it output in a https://www.webcomponents.org/element/PolymerElements/marked-element tag so that it could load HTML or markdown and play nice on the render side. This was problematic at times (horay parsers!) but if done correctly (only wrapping when it's pure markdown) then it would work well and bridge the UX / knowledge gap.