Streamline and simplify SASS/CSS for the website.

Question

Streamline and simplify SASS/CSS for the website.

zacharysarah opened this issue 6 years ago · comments

This is a...

Feature Request
Bug Report

Problem

The SASS and CSS for the website is haphazardly organized and implemented. It's not clear which files and/or attributes control site characteristics.

For example, changing base font size for the website is prohibitively complex: #12368)

Proposed Solution

We need straightforward, easily discoverable SASS for the website and its various areas.

Streamline and simplify SASS in:
- https://github.com/kubernetes/website/tree/master/sass
- https://github.com/kubernetes/website/tree/master/static/css
- Anywhere else SASS or CSS is hiding in k/website
Work with stakeholders, especially @alexcontini and @kbarnard10 to make sure that changes make sense and have buy-in from folks affected by SASS changes.

/ref

Ravi Soni · Answer 1 · Sun Feb 10 2019 16:28:08 GMT+0800 (China Standard Time)

Hi, my name is Ravi Soni. I have experience in frontend technologies and would love implementing the proposed solution under gsoc this year. How do I get started getting comfortable with the task mentioned?

Sai Adarsh S · Answer 2 · Tue Feb 19 2019 02:45:11 GMT+0800 (China Standard Time)

Hey @zacharysarah , I'm Sai Adarsh S interested in working with Streamline and simplify SASS for the Kubernetes website as a part of GSoC 2019. I'm a Full-stack developer proficient in HTML, CSS, JS, Django, Python, Node.js & containers. Having said that I’m looking forward to contributing, Any pointers on what should I work on or how should I be proceeding next?

fejta-bot · Answer 3 · Mon May 20 2019 03:35:55 GMT+0800 (China Standard Time)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot · Answer 4 · Wed Jun 19 2019 04:23:25 GMT+0800 (China Standard Time)

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot · Answer 5 · Fri Jul 19 2019 05:09:03 GMT+0800 (China Standard Time)

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Kubernetes Prow Robot · Answer 6 · Fri Jul 19 2019 05:09:11 GMT+0800 (China Standard Time)

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.