Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize Jekyll theme using a common framework #8

Open
mdrmike opened this issue Jul 15, 2017 · 3 comments
Open

Standardize Jekyll theme using a common framework #8

mdrmike opened this issue Jul 15, 2017 · 3 comments

Comments

@mdrmike
Copy link
Member

mdrmike commented Jul 15, 2017

This is more of a suggestion than an issue. But I'd suggest changing the theme to utilize a common framework, such as bootstrap or bulma or foundation. FWIW, We're currently using bootstrap on uncoded.org. and I plan to use it on waprolb.

This has benefit of:

  1. allows volunteers to work with tools that are useful to their personal portfolio along with public code commits.
  2. faster on-ramping of new volunteers
  3. more?
@mdrmike
Copy link
Member Author

mdrmike commented Jul 15, 2017

In Slack,

@arthursucks
said: I agree. I originally built it by hand cause I was learning but a formal framework would be a good idea.

@poproar
said: I have mixed feelings about a framework. i switched @arthur use of css files to use gh-pages native theme with overrides. the site is fairly simple. everything else is bloat. even the use of font awesome is too much for a couple icons. but don't get me wrong, I'm not saying don't do it, just keeping it real simple.

The main drawback I see of using github pages themes (or purely homegrown) is that (for most folks) its something they'll have to learn. That might create an obstacle in itself, without the benefit of learning a skill applicable to other projects. Versus using a framework, even if not known (or maybe especially), might be an appealing reason to help in itself.

@poproar
Copy link
Collaborator

poproar commented Jul 15, 2017

Good points @mdrmike. I disagree that you would not learn skills applicable to other projects. The themes provide a way to learn sass/scss (not that you cannot learn that with bootstrap or others) plus it could turn into a jekyll theme that could be shared with the OS community which would teach many skills along the way that include building a portfolio, working with gems, utilize new css features like grids, and having public code commits. It also provides the opportunity to learn traits from different frameworks instead of locking oneself into a technology.

Regardless of my opinion, I think the hosts will make the right decision. It is possible they straight up move to wordpress which has the benefits of learning another popular technology. My comments are intended for open discussion and not defensive arguing. In the end I am simply hoping to see more activity within the community.

@mdrmike
Copy link
Member Author

mdrmike commented Jul 15, 2017

Thanks @poproar! I didn't mean to suggest you wouldn't learn skills applicable to other projects. But those skills are somewhat nebulous to a volunteer (and moreso potential employers). BTW, no offense taken.

The crux of my suggestion is that building/learning a marketable skill (by that I mean buzzword on your resume) is of more value, and more likely to draw in more volunteers. There's even value in migrating to a framework.

I was just putting it out there as food for thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants