christianmurphy / apereo.foundation Goto Github PK

Add ability to search page contents and tags from within the website.

So I get no styling on / when rendering locally via the Docker image. Everything else seems to work fine. Seems to be only local since https://apereo.foundation/ styles just fine.

Have not yet sufficiently troubleshot (presumably once I sufficiently troubleshoot I'll resolve some local issue I haven't discovered yet.)

See: https://www.apereo.org/content/contact-and-mail-lists

For projects mail lists could maybe be stored as metadata? see #16

Currently scattered as files on the apereo site.
E.G. https://www.apereo.org/sites/default/files/Newsletters/February%20March%202016%20Apereo%20NL.pdf
Make these an official collection.

Add incubation collection to site.
https://jekyllrb.com/docs/collections
https://www.apereo.org/incubation

Apereo.org has some nifty links to repositories, blogs, downloads, etc.
This project should keep track of some standard fields that can be shown both on the project page and can enhance other views through collection metadata.
E.G. https://www.apereo.org/projects/apereo-oae
https://jekyllrb.com/docs/frontmatter/
https://jekyllrb.com/docs/collections/

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

Give potential contributors information on how they can participate.

Currently only a few projects are listed, add the rest in.

Give a high level overview of what this site is

Would it be cleaner / simpler to use a Jekyll theme?

• http://jekyllthemes.org/themes/jekyll-material-theme/
• http://jekyllthemes.org/themes/materialize/
• http://jekyllthemes.org/themes/jekyll-theme-mdui/
• http://jekyllthemes.org/themes/materialbliss/

I don't know anything about any of these themes, but I get the idea maybe a Jekyll theme could give the site some style defaults that might reduce the amount of custom styling going on inside the site source?

While #1 was resolved, I think rightly, as, no, the apereo.github.io blog should not wholesale be included in this website, there's still an important unrealized opportunity for this website to link to, to encourage community members to find and engage in, the apereo.github.io blog site.

cf. https://github.com/apereo/apereo.github.io/issues/24

I started getting this locally:

    Liquid Warning: Liquid syntax error (line 2): Expected end_of_string but found dot in "{{ page.lang | site.lang | default: "en" }}" in /_layouts/base.html

Have not yet sufficiently locally troubleshot, but maybe it's from #38 ?

Material design lite (mdl) is being phased out in favor of https://material.io/develop/web
Consider replacing mdl with material components.

Related to #19 and #34

I'm quite open to being convinced that Apache2 is fine.

And frankly I'm personally pretty exhausted about licensing and would be pretty willing to just give up.

But if we're looking to run with what was previously discussed and worked out about how non-code content should be licensed, I think where we got is that the website content should be CC-BY (while the custom website software to the extent that it exists probably should be Apache2.)

cf. apereo/apereo.github.io#4

Mechanically maybe we come out the other end with a root LICENSE file that remains Apache2 and then a /docs/LICENSE file that is CC-BY, and more importantly marking in the generated website that content licensed under CC-BY.

Cf. Apereo website status quo licensing footer

Note also that happily since status quo website is unambiguously defaulting to CC-BY-3 most of its content can be slurped in and redesigned here per that license without asking anyone permission about anything. So much to be said for open source licensing.

What is this? Is it a sponsored project? Does it have a PMC? Committers? Is it going through incubation?

I know what it is right now. Right now it's a personal repo in which some people who happen to be members of the community are, wearing their individual contributor hats, experimenting with a very promising, wonderful, potentially radically more welcoming and inclusive and effective way to wrangle the website. This is right and proper and good. Beautiful even.

And that might get pretty far along.

But not as far as it needs to go. At some point gotta wrestle down, no seriously, what is this, how is it governed, what makes it legitimate, how does it relate to Apereo the corporation. Can Apereo's website / webmaster spend be applied to work in this context? Etc.

Cf. https://github.com/apereo/apereo.github.io/issues/22

Something similar if not identical to https://github.com/uPortal-Project/uportal-home/blob/master/.github/PULL_REQUEST_TEMPLATE.md

Should the Apereo blog be included in the website, or kept as a separate site?

Should there be some complicity to have conversations and discussions on the site itself?

See https://github.com/apereo/apereo.github.io/blob/master/.github/CODE_OF_CONDUCT.md

If there was a smaller micro-site template that was apreo branded / maintained that then individual projects could pick up and PR against to manage their own content you'd be able to standardize UI/UX while still decentralizing the management of the content generated by each project (even if it's a single page that they could manage to describe and link off to updates about their own project).

This could reduce strain on the apereo foundation to maintain the site while still maintaining brand consistency

Reduce duplication https://jekyllrb.com/docs/variables/#page-variables

If you have a Jekyll page that doesn't have a title specified in the YAML Front Matter, but the first non-whitespace line in the page is a Markdown H1 / H2 / H3, this plugin instructs Jekyll to use that first heading as the page's title.
If you have a Jekyll page that doesn't have a title specified in the YAML Front Matter, but the first non-whitespace line in the page is a Markdown H1 / H2 / H3, this plugin instructs Jekyll to use that first heading as the page's title.

https://github.com/benbalter/jekyll-titles-from-headings

This will reduce some duplication.

In https://getmdl.io they styled their header by adding an extra class with

.class-name {
  text-decoration: none;
  color: rgb(255, 255, 255);
}

Allow the Apereo site to be presented in different languages.

Committers include the committers to exising apereo projects.
Plus some highly involved individuals.

Related to #9

Use the information provided by https://help.github.com/articles/repository-metadata-on-github-pages/
to add a direct link to edit a given page on github.