11 |
--------------------------------------------------------------------------------
/_pages/proposal_details.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: "Proposal Details"
4 | ---
5 |
6 | We have made the Project Proposal available for viewing. Please do note that this will be subject to change as we gather feedback from our stakeholders.
7 |
8 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feedback-for-orgcomm.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feedback for OrgComm
3 | about: Provide comments or suggestions to OrgComm
4 | title: "[Feedback] Title of feedback"
5 | labels: needs-review
6 | assignees: Fishbiscuit, tlkh
7 |
8 | ---
9 |
10 | **What**
11 |
12 | The subject of your feedback
13 |
14 |
15 |
16 | **Why**
17 |
18 | The reason you would like to provide this feedback
19 |
20 |
21 |
22 | **Suggestions**
23 |
24 | Provide some suggestions on how we can take action to address this matter
25 |
--------------------------------------------------------------------------------
/_includes/sidebar.html:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/_posts/2019-03-20-meeting.markdown:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Discussion on Project Proposal"
4 | date: 2019-03-20
5 | categories: meeting minutes
6 | ---
7 |
8 | **Objective** was to clarify some finer points of the proposal and confirm on budget request.
9 |
10 | 1. Registrar will check the budget for us, he's quite open to it, just propose that we push back the supper time to 7 to make sure that we cater to those who are fasting.
11 |
12 | 2. Next Wednesday he will engage all the pillars including HASS. I told him we want them for both human library and to run mock pillar classes. I’ll prep a presentation for that and will bring in the pillar reps to this group soon
13 |
14 | 3. Open to have eventyay be our platform
15 |
16 | 4. Arrange meeting with Chin wei on what the learning workshop/journey will be like for the Freshmores
17 |
18 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | If you'd like to contribute to this project, please use the fork-and-pull
2 | model:
3 |
4 | 1. Fork this repository to your personal account.
5 | 2. Create a branch and make your changes.
6 | 3. Test the changes locally/in your personal fork.
7 | 4. Submit a pull request to open a discussion about your proposed changes.
8 | 5. We'll talk about it and decide to merge or request additional changes.
9 |
10 | ---
11 |
12 | The project is in the public domain within the United States, and
13 | copyright and related rights in the work worldwide are waived through
14 | the [CC0 1.0 Universal public domain dedication][CC0].
15 |
16 | All contributions to this project will be released under the CC0
17 | dedication. By submitting a pull request, you are agreeing to comply
18 | with this waiver of copyright interest.
19 |
20 | [CC0]: http://creativecommons.org/publicdomain/zero/1.0/
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: default
3 | ---
4 |
5 | {% capture index %}{% include index.md %}{% endcapture %}
6 | {{ index | markdownify }}
7 |
8 | {% if site.repos %}
9 |
10 |
38 |
--------------------------------------------------------------------------------
/sw.js:
--------------------------------------------------------------------------------
1 | ---
2 | layout: null
3 | ---
4 |
5 | importScripts( '{{ site.baseurl }}/cache-polyfill.js' );
6 |
7 | var filesToCache = [
8 | // root
9 | '{{ site.baseurl }}/',
10 | '{{ site.baseurl }}/index.html',
11 | // css
12 | '{{ site.baseurl }}/assets/css/main.css',
13 | '{{ site.baseurl }}/assets/css/normalize.css',
14 | '{{ site.baseurl }}/assets/css/syntax.css',
15 | // images
16 | '{{ site.baseurl }}/assets/img/octocat.png',
17 | // pages
18 | {% for page in site.documents %}'{{ site.baseurl }}{{ page.url }}',{% endfor %}
19 | // posts
20 | {% for post in site.posts %}'{{ site.baseurl }}{{ post.url }}',{% endfor %}
21 | ];
22 |
23 | self.addEventListener( 'install', function( e ) {
24 | e.waitUntil(
25 | caches.open( '{{ site.cache_name }}' )
26 | .then( function( cache ) {
27 | return cache.addAll( filesToCache );
28 | })
29 | );
30 | });
31 |
32 | self.addEventListener( 'fetch', function( event ) {
33 | event.respondWith(
34 | caches.match( event.request ).then( function( response ) {
35 | return response || fetch( event.request );
36 | })
37 | );
38 | });
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/lightning-talk-proposal.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Lightning Talk Proposal
3 | about: Propose a lightning talk (10 mins)
4 | title: "[LT] Title of lightning talk"
5 | labels: needs-review, proposal
6 | assignees: Fishbiscuit, tlkh
7 |
8 | ---
9 |
10 | **Session Title**
11 |
12 | A title captures the intent of the session and is attention-grabbing.
13 |
14 |
15 |
16 | **Abstract**
17 |
18 | Also include a short description of the highlights of your session one or two sentences.
19 |
20 |
21 |
22 | **Presenter**
23 |
24 | * Name:
25 | * Pillar:
26 | * Fifth-row/Org/Lab (if applicable):
27 |
28 | **Short bio of presenter**
29 |
30 | In a few sentences, describe yourself and why you want to hold this lightning talk
31 |
32 |
33 |
34 | **Intent/Takeaway**
35 |
36 | - Share with us what you hope your participants will take away from this session (Participants will learn ...)
37 | - Share with us if there are any prerequisites to make the most of this session (Participants will require knowledge of ...)
38 | - *italicise* the specific skills/ takeaways that are quantifiable to help us create a concept map of the sessions we are offering for our incoming Freshmores
39 |
40 |
41 |
42 | **Logistical Details**
43 |
44 | Please us know if you'll need anything other than a microphone and a set of Google slides!
45 | Please provide us with your e-mail address so we can notify you once your event has been scheduled.
46 |
--------------------------------------------------------------------------------
/_posts/2019-03-26-meeting.markdown:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Discussion on Learning Workshop"
4 | date: 2019-03-26
5 | categories: meeting minutes
6 | ---
7 |
8 | Met with Chin Wei, organiser of the upcoming Learning Workshop/Journey session.
9 |
10 | **Objective** of workshop is to imbue students with a growth mindset and the right sort of attitude to approach challenges in SUTD. Not just academic but also the opportunities here.
11 | Previous years involved a 1.5h sesssion to share about growth mindset/ attitudes that will help one make the most of SUTD. they intend to have profs to do simulation exercises with the freshmores and put them to roleplay situations where the right mindset can help them overcome/ make the most of their opportunity.
12 |
13 | **Points of alignment**
14 | Looking for ways to better engage students. Suggested having videos/ interaction with students who managed to overcome challenges/ do meaningful work in SUTD. We could have students that, through these meaningful experiences, arrive at sufficient expertise to run workshops during Discovery Week to record/present about this experience in a short 1 min video and let them promote their session during the Learning Workshop.
15 |
16 | We will continue the conversation as planning continues. We'll need to request Chin Wei to send us his material so that we can provide some synergy throughout the rest of the programme. eg. material on how one might overcome introversion could be put in the Human Library short description to encourage freshmores to come for the event
17 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/session-proposal.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Session Proposal
3 | about: Propose a session conducted by a Student Organisation (Fifth Row etc.)
4 | title: "[FRS] Title of session"
5 | labels: needs-review, proposal
6 | assignees: Fishbiscuit, tlkh
7 |
8 | ---
9 |
10 | **Session Name**
11 |
12 | A title that captures the intent of the session and is attention-grabbing.
13 |
14 | **Abstract**
15 |
16 | A short description of the highlights of your session in one or two sentences.
17 |
18 | **Student Organisation organising this session**
19 |
20 |
21 |
22 | **Session intent (what to expect)**
23 |
24 | - Share with us what you hope your participants will take away from this session (Participants will learn ...)
25 | - Share with us if there are any prerequisites to make the most of this session (Participants will require knowledge of ...)
26 | - *italicise* the specific skills/ takeaways that are quantifiable to help us create a concept map of the sessions we are offering for our incoming Freshmores
27 |
28 |
29 |
30 | **Session details**
31 |
32 | Let us know the number of participants you can handle and where you intend to hold it. (if you need a venue, do let us know what sort of venue would be ideal to book). If you have any constraints on the timing or any other matters, do specify as well
33 |
34 |
35 |
36 | **Speakers/Workshop facilitators**
37 |
38 | Share with us the background of your facilitators to provide some context for your participants.
39 |
40 |
41 |
42 | **Logistical details**
43 |
44 | Help us with the overall resourcing our events. This will give us cue as to how to budget for the event and if there are further constraints we must consider.
45 | Please provide us with your club e-mail address so we can notify you once your event has been scheduled.
46 |
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | # Base configuration
2 | exclude: [".rvmrc", ".rbenv-version", "README.md", "Rakefile", "changelog.md"]
3 | markdown: kramdown
4 | highlighter: rouge
5 |
6 | collections:
7 | pages:
8 | output: true
9 | permalink: /:path/
10 |
11 | # Title
12 | name: Discovery Week (working title)
13 | subtitle: Project Page for organising Discovery Week
14 |
15 | # When using this template with a project page set the baseurl to '/project-name'
16 | # For user/organization pages set this to an empty string
17 | # When working locally use jekyll serve --baseurl '' so that you can view everything at localhost:4000
18 | # See http://jekyllrb.com/docs/github-pages/ for more info
19 | #baseurl: ''
20 | baseurl: '/discovery-week-working-title'
21 |
22 | # Author/Organization info to be displayed in the templates
23 | author:
24 | name: OpenSUTD
25 | url: https://github.com/OpenSUTD
26 |
27 | # Point the logo URL at a file in your repo or hosted elsewhere by your organization
28 | logourl:
29 | logoalt:
30 |
31 | # Navigation
32 | # List links that should appear in the site sidebar here
33 | navigation:
34 | - text: Home
35 | url: ./
36 | internal: true
37 | - text: Programs
38 | url: programs/
39 | internal: true
40 | - text: Contributing
41 | url: contributing/
42 | internal: true
43 | - text: Proposal Details
44 | url: proposal_details/
45 | internal: true
46 | - text: Site repo
47 | url: https://github.com/OpenSUTD/discovery-week-working-title
48 | internal: false
49 |
50 | # Repo list
51 | # List repos that you would like to appear on the homepage here
52 | repos:
53 | - name: Discovery Week
54 | description: Master Repository
55 | url: https://github.com/OpenSUTD/discovery-week-working-title
56 |
57 | # Style Variables
58 | brand_color: "#2cb34a"
59 |
60 | # Offline caching
61 | offline_cache: false
62 | cache_name: DOCter-v1.1
63 |
--------------------------------------------------------------------------------
/TERMS.md:
--------------------------------------------------------------------------------
1 | As a work of the United States Government, this package is in the
2 | public domain within the United States. Additionally, we waive
3 | copyright and related rights in the work worldwide through the CC0 1.0
4 | Universal public domain dedication.
5 |
6 | Software source code previously released under an open source license and then
7 | modified by CFPB staff is considered a "joint work" (see 17 USC § 101); it is
8 | partially copyrighted, partially public domain, and as a whole is protected by
9 | the copyrights of the non-government authors and must be released according to
10 | the terms of the original open-source license.
11 |
12 | For further details, please see the CFPB [Source Code Policy][policy].
13 |
14 |
15 | ## CC0 1.0 Universal Summary
16 |
17 | This is a human-readable summary of the [Legal Code (read the full text)][CC0].
18 |
19 | ### No Copyright
20 |
21 | The person who associated a work with this deed has dedicated the work to
22 | the public domain by waiving all of his or her rights to the work worldwide
23 | under copyright law, including all related and neighboring rights, to the
24 | extent allowed by law.
25 |
26 | You can copy, modify, distribute and perform the work, even for commercial
27 | purposes, all without asking permission. See Other Information below.
28 |
29 | ### Other Information
30 |
31 | In no way are the patent or trademark rights of any person affected by CC0,
32 | nor are the rights that other persons may have in the work or in how the
33 | work is used, such as publicity or privacy rights.
34 |
35 | Unless expressly stated otherwise, the person who associated a work with
36 | this deed makes no warranties about the work, and disclaims liability for
37 | all uses of the work, to the fullest extent permitted by applicable law.
38 | When using or citing the work, you should not imply endorsement by the
39 | author or the affirmer.
40 |
41 | [policy]: http://github.com/cfpb/source-code-policy/
42 | [CC0]: http://creativecommons.org/publicdomain/zero/1.0/legalcode
43 |
44 | ## This project makes use of:
45 |
46 | * [Respond.js](https://github.com/scottjehl/Respond) by Scott Jehl, licensed under the MIT license.
47 | * [The HTML5 Shiv](https://github.com/aFarkas/html5shiv), dual licensed under the MIT or GPL Version 2 licenses.
48 | *
49 |
--------------------------------------------------------------------------------
/_layouts/default.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 | {% if page.title == null %}
8 | {{ site.name }}
9 | {% else %}
10 | {{ page.title }} - {{ site.name }}
11 | {% endif %}
12 |
13 |
14 |
15 |
16 |
17 |
21 |
22 |
23 |
24 |
52 | {% if site.offline_cache == true %}
53 |
62 | {% endif %}
63 |
64 |
65 |
--------------------------------------------------------------------------------
/cache-polyfill.js:
--------------------------------------------------------------------------------
1 | /**
2 | * Copyright 2015 Google Inc. All rights reserved.
3 | *
4 | * Licensed under the Apache License, Version 2.0 (the "License");
5 | * you may not use this file except in compliance with the License.
6 | * You may obtain a copy of the License at
7 | *
8 | * http://www.apache.org/licenses/LICENSE-2.0
9 | *
10 | * Unless required by applicable law or agreed to in writing, software
11 | * distributed under the License is distributed on an "AS IS" BASIS,
12 | * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 | * See the License for the specific language governing permissions and
14 | * limitations under the License.
15 | *
16 | */
17 |
18 | if (!Cache.prototype.addAll) {
19 | Cache.prototype.addAll = function addAll(requests) {
20 | var cache = this;
21 |
22 | // Since DOMExceptions are not constructable:
23 | function NetworkError(message) {
24 | this.name = 'NetworkError';
25 | this.code = 19;
26 | this.message = message;
27 | }
28 | NetworkError.prototype = Object.create(Error.prototype);
29 |
30 | return Promise.resolve().then(function() {
31 | if (arguments.length < 1) throw new TypeError();
32 |
33 | // Simulate sequence<(Request or USVString)> binding:
34 | var sequence = [];
35 |
36 | requests = requests.map(function(request) {
37 | if (request instanceof Request) {
38 | return request;
39 | }
40 | else {
41 | return String(request); // may throw TypeError
42 | }
43 | });
44 |
45 | return Promise.all(
46 | requests.map(function(request) {
47 | if (typeof request === 'string') {
48 | request = new Request(request);
49 | }
50 |
51 | var scheme = new URL(request.url).protocol;
52 |
53 | if (scheme !== 'http:' && scheme !== 'https:') {
54 | throw new NetworkError("Invalid scheme");
55 | }
56 |
57 | return fetch(request.clone());
58 | })
59 | );
60 | }).then(function(responses) {
61 | // TODO: check that requests don't overwrite one another
62 | // (don't think this is possible to polyfill due to opaque responses)
63 | return Promise.all(
64 | responses.map(function(response, i) {
65 | return cache.put(requests[i], response);
66 | })
67 | );
68 | }).then(function() {
69 | return undefined;
70 | });
71 | };
72 | }
73 |
--------------------------------------------------------------------------------
/_pages/programs.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: "Programs"
4 | ---
5 | **Fifth Row Sessions**
6 |
7 | We intend to adhere to these principles:
8 | 1. Equitable - Fifth Rows that want to do a workshop will have the chance to, especially if there is a proven track record of doing excellent sessions.
9 | 2. Fair - all workshops conducted well should be supported.
10 | 3. Incentivise right behaviour - we should provide funds to encourage a more hands-on approach, quality instructors, well-prepared material.
11 |
12 | We'd like to support Fifth Rows in reaching out to the Freshmores but also to help Freshmores make sense of what Fifth Rows suit them best. Specifically through clear communication and categorising our workshops into tracks based on skills taught.
13 |
14 | *Talk to your Cluster Reps or catch us during the Fifth Row Forum on 10th April 2019*
15 |
16 | **Human Library**
17 |
18 | Have speakers act as ‘books’ and you can ‘borrow’ their time. Execution-wise, have students ‘borrow’ the books for a fixed timeslot and rotate every hour. Possibly just have the professors at their office/ location of their choice and students can come by. Think of it as an informal way to Discover the people behind SUTD. Previous [human libraries](https://docs.google.com/document/d/1UvHSNurYQyQ7Fpd3hj5LVKAsEBCkx3GNzvsFQXgqCRw/edit#) held at SUTD saw not just Professors but also researchers and students being our books.
19 |
20 | *We need coordinators for this event!*
21 |
22 | **Lightning Talks**
23 |
24 | Talks that focus on the tangible SUTD experience. Get Freshmores thinking about what you others have done at SUTD and the avenues for it.
25 |
26 | *We need speakers and coordinators for this event!*
27 |
28 | **Housing Sessions**
29 |
30 | House Guardians will hold an event on the first week of school followed by [Friendzone Singapore](https://www.friendzone.sg/). The emphasis is community building in our Freshmores' new home.
31 |
32 | **Pillar Sessions**
33 |
34 | Experential session to expose to students what Pillar life will be like. Focus on a skill or lesson methodology that is representative of what we do once we enter our Pillars.
35 |
36 | **Supper makan sessions**
37 |
38 | Yes you heard that right! We will be providing supper most days of the week to encourage Freshmores to stay for workshops and activities after class. Also we hope that having the cohort gather regularly might help in building a stronger community through encouraging people to share about their day, hopes and experiences at SUTD.
39 |
--------------------------------------------------------------------------------
/_pages/contributing.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: "Contributing"
4 | ---
5 | **Overall Contribution Workflow**
6 |
7 | 1. Submit a proposal through Github Issues on our master repository
8 | 2. We will reply to your issue and review it.
9 | 3. Once it is reviewed and cleared, we will notify you.
10 |
11 | Please do note that the planning team is small and we ask for your patience. It will take time to clear sesssions with the staff but rest assured we receive all proposals.
12 |
13 | **I would like to hold a session**
14 |
15 | If you're a Fifth Row leader, a Senior or alumni and would like to hold a workshop for Freshmores.
16 |
17 | 1. Go to our [issue](https://github.com/OpenSUTD/discovery-week-working-title/issues/new/choose) templates
18 | 2. Click on "Get started" under Session Proposal
19 | 3. Please provide us the details of your session. We would like to emphasise that we would like you to *italicise* the specific skills/takeaways from your session.
20 |
21 | For examples of other workshops that are pretty good, take a look at the recent [Deep Learning Workshop](https://github.com/OpenSUTD/deeplearning-workshop-2019).
22 |
23 | Also take a look at what other Fifth Rows are [planning](https://github.com/OpenSUTD/discovery-week-working-title/issues).
24 |
25 | **I would like to be a part of the team**
26 |
27 | For visual branding:
28 | We've requested for a budget! Since we're a design school, our efforts need to not just be conceptually sound but aesthetically pleasing. To alleviate the work, possibly looking at seeking freelancers to prepare material.
29 | 1. assist session organisers to maintain a consistent visual brand throughout the event
30 | 2. produce graphics for curated tracks and programs
31 |
32 | **I would like to make a suggestion**
33 |
34 | 1. Go to our [issue](https://github.com/OpenSUTD/discovery-week-working-title/issues/new/choose) templates
35 | 2. Click on "Get started" under Feedback for OrgComm
36 | 3. Let us know how we can do better!
37 |
38 | **I would like to speak for Lightning talks**
39 |
40 | So what's a [lightning talk](https://en.wikipedia.org/wiki/Lightning_talk)?
41 | Lightning talks are designed to be short presentations between five and ten minutes long, but are usually capped at five minutes
42 | 1. Go to our [issue](https://github.com/OpenSUTD/discovery-week-working-title/issues/new/choose) templates
43 | 2. Click on "Get started" under Lightning Talk Proposal
44 | 3. Let us know your Session Title, a short Abstract, who you are, what participants should take away from your session and if you need any special logistics
45 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Discovery Week (Working Title)
2 | **Decentralised planning for the Freshmore experience**
3 |
4 | Check out [this page](https://open.sutd.dev/discovery-week-working-title/) for all the in depth details. You will even find out meeting minutes there! (it's under "Posts")
5 |
6 | Do let us know if you can think of a better name for this event! That's why it's still a working title.
7 |
8 | ## What is this?
9 | Discovery Week is a 3 week long introduction to the SUTD community. It will last from 21st May - 7 June 2019.
10 |
11 | It is currently a working title because the name is still in the midst of being decided. Afterall, it’s a 3 week event and no longer just one week!
12 |
13 | Discovery Week is organised by the team behind OpenSUTD.
14 |
15 | OpenSUTD is modelled after the idea of an Open Organisation, and we have community standards for all members to abide by in order to ensure a good enviroment for members to learn and contribute effectively.
16 |
17 | ## Contributing
18 | Details are [here](https://open.sutd.dev/discovery-week-working-title/contributing/).
19 | In general the workflow is:
20 | 1. Submit a proposal through Github Issues on our master repository
21 | 2. We will reply to your issue and review it.
22 | 3. Once it is reviewed and cleared, you will get a notification.
23 | 4. If you’re proposing a session for the event, please proceed to Eventyay to submit your proposal. This is done to collate your details and to get ready to schedule you for the event. Otherwise, if you’re making a suggestion for improvement, the workflow will diverge and tailor to the idea given.
24 |
25 |
26 | ## Timeline
27 | This is to cater to Fifth row leaders when they are planning. The detailed proposal is [here](https://open.sutd.dev/discovery-week-working-title/proposal_details/)
28 |
29 | |Week|Activities|
30 | |--|--|
31 | |20 - 24 May|Thurs: Human library, HG event|
32 | ||Fri: Fifth row sessions (after class hours)|
33 | ||Mon is public holiday|
34 | |24 - 31 May|Mon-Fri: Fifth row sessions available (after class hours)|
35 | ||Weds: Lightning talks, pillar sessions, lab visit|
36 | ||Thurs: Housing event|
37 | |3 - 7 June|Mon-Fri: Fifth row sessions available (after class hours)|
38 | ||Weds is public holiday, makeup class on Friday|
39 |
40 |
41 | ## Who's Who:
42 |
43 | Discovery Week details: Hum Qing Ze ([email](mailto:qingze_hum@mymail.sutd.edu.sg))
44 |
45 | OpenSUTD: Timothy Liu ([email](mailto:timothy_liu@mymail.sutd.edu.sg)); Joel Huang ([email](mailto:joel_huang@mymail.sutd.edu.sg))
46 |
47 | Open Regulation: Lee Gui An ([email](mailto:guian_lee@mymail.sutd.edu.sg))
48 |
49 | SAC rep coordination: Tay Kay Jin ([email](mailto:kayjin_tay@mymail.sutd.edu.sg))
50 |
--------------------------------------------------------------------------------
/Fifth-Rows/Session Template.md:
--------------------------------------------------------------------------------
1 | # Session Name
2 |
3 | Ideally have a session name that captures the intent of the session and is attention-grabbing. Also include a short description of the highlights of your session one or two sentences.
4 |
5 | **Fifth Row organising this session**
6 |
7 | # Session intent (what to expect)
8 |
9 | - Share with us what you hope your participants will take away from this session (Participants will learn ...)
10 | - Share with us if there are any prerequisites to make the most of this session (Participants will require knowledge of ...)
11 | - *italicise* the specific skills/ takeaways that are quantifiable to help us create a concept map of the sessions we are offering for our incoming Freshmores
12 |
13 | # Session details
14 |
15 | Let us know the number of participants you can handle and where you intend to hold it. (if you need a venue, do let us know what sort of venue would be ideal to book)
16 |
17 | ## Speakers/Workshop facilitators
18 |
19 | Share with us the background of your facilitators to provide some context for your participants.
20 |
21 | Your participants may want to prepare some questions regarding your SUTD experience so far.
22 |
23 | ## Logistical details
24 |
25 | Help us with the overall resourcing our events. This will give us cue as to how to budget for the event and if there are further constraints we must consider.
26 |
27 | ---
28 |
29 | **Small example below**
30 |
31 | # Cloud Study Jam in SUTD
32 |
33 | In collaboration with Google Cloud, we will be conducting a Cloud Study Jam to introduce members of the SUTD community to the basics of using Google Cloud Platform tools for Data, ML and AI.
34 |
35 | **Brought to you by ISTD Student Board**
36 |
37 | # What to expect
38 |
39 | This will be a half-day workshop intended to introduce students to using Google Cloud Platform (GCP) tools for *data* and *machine-learning* related tasks, and is open to all members of the SUTD community.
40 |
41 | Participants will learn:
42 |
43 | * the basics of Google Cloud Platform tools such as Cloud SQL, BigTable, BigQuery for managing databases
44 | * the basics of using Cloud Datalab and Cloud ML Engine to train machine-learning models
45 |
46 | There is no pre-requisite knowledge as this will be a workshop targeted at beginners.
47 |
48 | # Session details
49 |
50 | Venue: LT4 (Building 2, Level 4)
51 |
52 | Date: 15 March 2019 (Friday of recess week)
53 |
54 | Time: 1pm to 6pm
55 |
56 | Up to 30 participants only
57 |
58 | ## Your host for the day
59 |
60 | Timothy Liu: current ISTD sophomore. Check him out [here](https://www.linkedin.com/in/timothyliukaihui/?originalSubdomain=sg)
61 |
62 | ## Checklist
63 |
64 | Please bring your own laptop and a jacket if you find the classrooms cold!
65 |
66 |
--------------------------------------------------------------------------------
/_includes/index.md:
--------------------------------------------------------------------------------
1 | # What is this?
2 | Discovery Week is a 3 week long introduction to the SUTD community. It will last from 21st May - 7 June 2019.
3 |
4 | It is currently a [working title](https://en.wikipedia.org/wiki/Working_title) because the name is still in the midst of being decided. Afterall, it's a 3 week event and no longer just one week!
5 |
6 | Discovery Week is organised by the team behind [OpenSUTD](https://github.com/OpenSUTD).
7 |
8 | OpenSUTD is modelled after the idea of an Open Organisation, and we have community standards for all members to abide by in order to ensure a good enviroment for members to learn and contribute effectively.
9 | ```
10 | An Open Organization is one that engages participative communities both inside and out; responds to opportunities more quickly, has access to resources and talent outside the organization, and inspires, motivates, and empowers people at all levels to act. -Open Organisation Definition
11 | ```
12 |
13 | This is why we are making sure that our project documents are kept open so that **you** can be a part of this process.
14 | Read the "Posts" section at the bottom of this page if you're interested in going through our minutes.
15 |
16 | # Concept
17 | Adopting the model of a Conference with large-scale talks targeted at the general audience but also breakout sessions that participants can sign-up for on an individualised manner.
18 |
19 | **Emphasis on personal agency to allow for self-discovery of SUTD's ecosystem.**
20 |
21 | # Objectives
22 | 1. For Freshmores - understand the spaces (virtual and physical), avenues for resources and communities in SUTD in order to embody the desired culture
23 | Culture embodying the spirit of innovation, collaboration, having self-initiated projects, self-directed learning and broad-based skill integration
24 |
25 | 2. For SUTD - celebrate the work done by our research community, 5th rows and housing (specifically amongst seniors)
26 | Showcase the potential of UROPs and taking up research projects in SUTD, similar to LCC in an interactive/ experiential manner
27 |
28 | # But what does this mean?
29 | We will
30 | 1. **Support** Fifth Rows by providing a budget for you to hold workshops that cater to Freshmores. There's just a small catch, do follow the template we provide to facilitate preparing the event schedule.
31 | 2. **Organise** community sesions in the form of a Human Library, Lightning Talks and Housing events.
32 | 3. **Bring together** the larger graduate and research community in the SUTD ecosystem through tours and meet ups.
33 | 4. **Provide** a consistent visual branding throughout the event.
34 |
35 | If you're interested in helping in any of these objectives or simply would like to give feedback, please check out the [Contributing](https://fishbiscuit.github.io/Discovery-Week-Project-Site-Test/contributing/) page.
36 |
37 | The event is hosted on [Eventyay](https://eventyay.com/e/80f9d561/) in true [OpenSUTD](https://github.com/OpenSUTD) spirit.
38 |
--------------------------------------------------------------------------------
/_posts/2019-03-28-meeting.markdown:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Discussion with Pillar staff"
4 | date: 2019-03-28
5 | categories: meeting minutes
6 | ---
7 |
8 | We’re looking for support from the pillars to
9 |
10 | 1. recommend profs/ seniors to a human library session on W1,Thurs (23/5) concerned about the specific logistics of making this happen. Suggested having think tanks that are focused with profs from specific pillars/ topics for easier management.
11 | 2. contribute speakers for lightning talks, could be PhDs, profs that would like to share interesting projects etc on W2,Wednesday (29/5) with a focus on the SUTD experience that excite people
12 | 3. organise an experential session on what a pillar lesson might be like, subject to each pillar’s availability on the recommendations of the pillar reps. for W2, Wednesday (29/5)
13 | EPD: what lab sessions might be like at ARMs
14 | ESD: thumbles/ MSO game/ using R
15 | ISTD: lab session, maybe adapt popular sessions
16 | ASD: having them join an existing SUTDio session?
17 | Communication method:
18 | I’m asking them to let us take the lead in reaching out to the profs as they are generally more responsive towards students and i don’t want it to be a pillar head top-down thing.
19 | So I’ll want to e-mail the pillars, perhaps with a short note from the pillar heads on how this might be relevant for them and then supplement with a more targeted approach to specific profs that they recommend.
20 |
21 | Staff expressed concerns about
22 | - Space available to host their pillar activities during the allocated time slots
23 | - The expected number of faculty required
24 |
25 | ESD: concern about space available, Thumbles is held at the staffroom area and can't accomodate many people
26 | ISTD: several focus tracks make it hard to present a representative picture in just one experential session
27 | ASD: agree that having students simply visit the studios wouldn't be helpful as ASD students would be busy working and one cannot simply jump into the design process without sufficient context
28 |
29 | To address the pillars’ concerns, please include the following into the overall plan
30 | - Proposed space (for each pillar) – you can consider this point as an estimate for the possible number of sessions that can be conducted during the same time slot
31 | - Proposed number of sessions (for each pillar)
32 | - Proposed number of faculty (for each pillar)
33 |
34 |
35 |
36 | FAQ:
37 | What’s a human library?
38 | Have speakers act as ‘books’ and you can ‘borrow’ their time. Execution-wise, have students ‘borrow’ the books for a fixed timeslot and rotate every hour. Possibly just have the professors at their office/ location of their choice and students can come by.
39 |
40 | What are students concerned with?
41 | As a freshmore people don’t have enough information of what they learn at pillars.
42 | As seniors we hope that we can provide a fair representation of the pillars without being intimidating
43 |
44 | What is openSUTD?
45 |
46 | open regulation - students can easily navigate the ecosystem
47 | open notes - students can tell ahead of time what to expect in courses and have better decisions as to what to choose/moderate commitment to fifth rows etc
48 | projects - inter-batch collaboration and inspire freshmores
49 | fifth row guides - for those that want to start something
50 |
--------------------------------------------------------------------------------
/assets/css/syntax.css:
--------------------------------------------------------------------------------
1 | .highlight { background: #ffffff; }
2 | .highlight .c { color: #999988; font-style: italic } /* Comment */
3 | .highlight .err { color: #a61717; background-color: #e3d2d2 } /* Error */
4 | .highlight .k { font-weight: bold } /* Keyword */
5 | .highlight .o { font-weight: bold } /* Operator */
6 | .highlight .cm { color: #999988; font-style: italic } /* Comment.Multiline */
7 | .highlight .cp { color: #999999; font-weight: bold } /* Comment.Preproc */
8 | .highlight .c1 { color: #999988; font-style: italic } /* Comment.Single */
9 | .highlight .cs { color: #999999; font-weight: bold; font-style: italic } /* Comment.Special */
10 | .highlight .gd { color: #000000; background-color: #ffdddd } /* Generic.Deleted */
11 | .highlight .gd .x { color: #000000; background-color: #ffaaaa } /* Generic.Deleted.Specific */
12 | .highlight .ge { font-style: italic } /* Generic.Emph */
13 | .highlight .gr { color: #aa0000 } /* Generic.Error */
14 | .highlight .gh { color: #999999 } /* Generic.Heading */
15 | .highlight .gi { color: #000000; background-color: #ddffdd } /* Generic.Inserted */
16 | .highlight .gi .x { color: #000000; background-color: #aaffaa } /* Generic.Inserted.Specific */
17 | .highlight .go { color: #888888 } /* Generic.Output */
18 | .highlight .gp { color: #555555 } /* Generic.Prompt */
19 | .highlight .gs { font-weight: bold } /* Generic.Strong */
20 | .highlight .gu { color: #aaaaaa } /* Generic.Subheading */
21 | .highlight .gt { color: #aa0000 } /* Generic.Traceback */
22 | .highlight .kc { font-weight: bold } /* Keyword.Constant */
23 | .highlight .kd { font-weight: bold } /* Keyword.Declaration */
24 | .highlight .kp { font-weight: bold } /* Keyword.Pseudo */
25 | .highlight .kr { font-weight: bold } /* Keyword.Reserved */
26 | .highlight .kt { color: #445588; font-weight: bold } /* Keyword.Type */
27 | .highlight .m { color: #009999 } /* Literal.Number */
28 | .highlight .s { color: #d14 } /* Literal.String */
29 | .highlight .na { color: #008080 } /* Name.Attribute */
30 | .highlight .nb { color: #0086B3 } /* Name.Builtin */
31 | .highlight .nc { color: #445588; font-weight: bold } /* Name.Class */
32 | .highlight .no { color: #008080 } /* Name.Constant */
33 | .highlight .ni { color: #800080 } /* Name.Entity */
34 | .highlight .ne { color: #990000; font-weight: bold } /* Name.Exception */
35 | .highlight .nf { color: #990000; font-weight: bold } /* Name.Function */
36 | .highlight .nn { color: #555555 } /* Name.Namespace */
37 | .highlight .nt { color: #000080 } /* Name.Tag */
38 | .highlight .nv { color: #008080 } /* Name.Variable */
39 | .highlight .ow { font-weight: bold } /* Operator.Word */
40 | .highlight .w { color: #bbbbbb } /* Text.Whitespace */
41 | .highlight .mf { color: #009999 } /* Literal.Number.Float */
42 | .highlight .mh { color: #009999 } /* Literal.Number.Hex */
43 | .highlight .mi { color: #009999 } /* Literal.Number.Integer */
44 | .highlight .mo { color: #009999 } /* Literal.Number.Oct */
45 | .highlight .sb { color: #d14 } /* Literal.String.Backtick */
46 | .highlight .sc { color: #d14 } /* Literal.String.Char */
47 | .highlight .sd { color: #d14 } /* Literal.String.Doc */
48 | .highlight .s2 { color: #d14 } /* Literal.String.Double */
49 | .highlight .se { color: #d14 } /* Literal.String.Escape */
50 | .highlight .sh { color: #d14 } /* Literal.String.Heredoc */
51 | .highlight .si { color: #d14 } /* Literal.String.Interpol */
52 | .highlight .sx { color: #d14 } /* Literal.String.Other */
53 | .highlight .sr { color: #009926 } /* Literal.String.Regex */
54 | .highlight .s1 { color: #d14 } /* Literal.String.Single */
55 | .highlight .ss { color: #990073 } /* Literal.String.Symbol */
56 | .highlight .bp { color: #999999 } /* Name.Builtin.Pseudo */
57 | .highlight .vc { color: #008080 } /* Name.Variable.Class */
58 | .highlight .vg { color: #008080 } /* Name.Variable.Global */
59 | .highlight .vi { color: #008080 } /* Name.Variable.Instance */
60 | .highlight .il { color: #009999 } /* Literal.Number.Integer.Long */
61 |
--------------------------------------------------------------------------------
/assets/js/respond.min.js:
--------------------------------------------------------------------------------
1 | /*! matchMedia() polyfill - Test a CSS media type/query in JS. Authors & copyright (c) 2012: Scott Jehl, Paul Irish, Nicholas Zakas. Dual MIT/BSD license */
2 | /*! NOTE: If you're already including a window.matchMedia polyfill via Modernizr or otherwise, you don't need this part */
3 | window.matchMedia=window.matchMedia||function(a){"use strict";var c,d=a.documentElement,e=d.firstElementChild||d.firstChild,f=a.createElement("body"),g=a.createElement("div");return g.id="mq-test-1",g.style.cssText="position:absolute;top:-100em",f.style.background="none",f.appendChild(g),function(a){return g.innerHTML='',d.insertBefore(f,e),c=42===g.offsetWidth,d.removeChild(f),{matches:c,media:a}}}(document);
4 |
5 | /*! Respond.js v1.3.0: min/max-width media query polyfill. (c) Scott Jehl. MIT/GPLv2 Lic. j.mp/respondjs */
6 | (function(a){"use strict";function x(){u(!0)}var b={};if(a.respond=b,b.update=function(){},b.mediaQueriesSupported=a.matchMedia&&a.matchMedia("only all").matches,!b.mediaQueriesSupported){var q,r,t,c=a.document,d=c.documentElement,e=[],f=[],g=[],h={},i=30,j=c.getElementsByTagName("head")[0]||d,k=c.getElementsByTagName("base")[0],l=j.getElementsByTagName("link"),m=[],n=function(){for(var b=0;l.length>b;b++){var c=l[b],d=c.href,e=c.media,f=c.rel&&"stylesheet"===c.rel.toLowerCase();d&&f&&!h[d]&&(c.styleSheet&&c.styleSheet.rawCssText?(p(c.styleSheet.rawCssText,d,e),h[d]=!0):(!/^([a-zA-Z:]*\/\/)/.test(d)&&!k||d.replace(RegExp.$1,"").split("/")[0]===a.location.host)&&m.push({href:d,media:e}))}o()},o=function(){if(m.length){var b=m.shift();v(b.href,function(c){p(c,b.href,b.media),h[b.href]=!0,a.setTimeout(function(){o()},0)})}},p=function(a,b,c){var d=a.match(/@media[^\{]+\{([^\{\}]*\{[^\}\{]*\})+/gi),g=d&&d.length||0;b=b.substring(0,b.lastIndexOf("/"));var h=function(a){return a.replace(/(url\()['"]?([^\/\)'"][^:\)'"]+)['"]?(\))/g,"$1"+b+"$2$3")},i=!g&&c;b.length&&(b+="/"),i&&(g=1);for(var j=0;g>j;j++){var k,l,m,n;i?(k=c,f.push(h(a))):(k=d[j].match(/@media *([^\{]+)\{([\S\s]+?)$/)&&RegExp.$1,f.push(RegExp.$2&&h(RegExp.$2))),m=k.split(","),n=m.length;for(var o=0;n>o;o++)l=m[o],e.push({media:l.split("(")[0].match(/(only\s+)?([a-zA-Z]+)\s?/)&&RegExp.$2||"all",rules:f.length-1,hasquery:l.indexOf("(")>-1,minw:l.match(/\(\s*min\-width\s*:\s*(\s*[0-9\.]+)(px|em)\s*\)/)&&parseFloat(RegExp.$1)+(RegExp.$2||""),maxw:l.match(/\(\s*max\-width\s*:\s*(\s*[0-9\.]+)(px|em)\s*\)/)&&parseFloat(RegExp.$1)+(RegExp.$2||"")})}u()},s=function(){var a,b=c.createElement("div"),e=c.body,f=!1;return b.style.cssText="position:absolute;font-size:1em;width:1em",e||(e=f=c.createElement("body"),e.style.background="none"),e.appendChild(b),d.insertBefore(e,d.firstChild),a=b.offsetWidth,f?d.removeChild(e):e.removeChild(b),a=t=parseFloat(a)},u=function(b){var h="clientWidth",k=d[h],m="CSS1Compat"===c.compatMode&&k||c.body[h]||k,n={},o=l[l.length-1],p=(new Date).getTime();if(b&&q&&i>p-q)return a.clearTimeout(r),r=a.setTimeout(u,i),void 0;q=p;for(var v in e)if(e.hasOwnProperty(v)){var w=e[v],x=w.minw,y=w.maxw,z=null===x,A=null===y,B="em";x&&(x=parseFloat(x)*(x.indexOf(B)>-1?t||s():1)),y&&(y=parseFloat(y)*(y.indexOf(B)>-1?t||s():1)),w.hasquery&&(z&&A||!(z||m>=x)||!(A||y>=m))||(n[w.media]||(n[w.media]=[]),n[w.media].push(f[w.rules]))}for(var C in g)g.hasOwnProperty(C)&&g[C]&&g[C].parentNode===j&&j.removeChild(g[C]);for(var D in n)if(n.hasOwnProperty(D)){var E=c.createElement("style"),F=n[D].join("\n");E.type="text/css",E.media=D,j.insertBefore(E,o.nextSibling),E.styleSheet?E.styleSheet.cssText=F:E.appendChild(c.createTextNode(F)),g.push(E)}},v=function(a,b){var c=w();c&&(c.open("GET",a,!0),c.onreadystatechange=function(){4!==c.readyState||200!==c.status&&304!==c.status||b(c.responseText)},4!==c.readyState&&c.send(null))},w=function(){var b=!1;try{b=new a.XMLHttpRequest}catch(c){b=new a.ActiveXObject("Microsoft.XMLHTTP")}return function(){return b}}();n(),b.update=n,a.addEventListener?a.addEventListener("resize",x,!1):a.attachEvent&&a.attachEvent("onresize",x)}})(this);
7 |
--------------------------------------------------------------------------------
/COPYING.txt:
--------------------------------------------------------------------------------
1 | Creative Commons Legal Code
2 |
3 | CC0 1.0 Universal
4 |
5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
12 | HEREUNDER.
13 |
14 | Statement of Purpose
15 |
16 | The laws of most jurisdictions throughout the world automatically confer
17 | exclusive Copyright and Related Rights (defined below) upon the creator
18 | and subsequent owner(s) (each and all, an "owner") of an original work of
19 | authorship and/or a database (each, a "Work").
20 |
21 | Certain owners wish to permanently relinquish those rights to a Work for
22 | the purpose of contributing to a commons of creative, cultural and
23 | scientific works ("Commons") that the public can reliably and without fear
24 | of later claims of infringement build upon, modify, incorporate in other
25 | works, reuse and redistribute as freely as possible in any form whatsoever
26 | and for any purposes, including without limitation commercial purposes.
27 | These owners may contribute to the Commons to promote the ideal of a free
28 | culture and the further production of creative, cultural and scientific
29 | works, or to gain reputation or greater distribution for their Work in
30 | part through the use and efforts of others.
31 |
32 | For these and/or other purposes and motivations, and without any
33 | expectation of additional consideration or compensation, the person
34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she
35 | is an owner of Copyright and Related Rights in the Work, voluntarily
36 | elects to apply CC0 to the Work and publicly distribute the Work under its
37 | terms, with knowledge of his or her Copyright and Related Rights in the
38 | Work and the meaning and intended legal effect of CC0 on those rights.
39 |
40 | 1. Copyright and Related Rights. A Work made available under CC0 may be
41 | protected by copyright and related or neighboring rights ("Copyright and
42 | Related Rights"). Copyright and Related Rights include, but are not
43 | limited to, the following:
44 |
45 | i. the right to reproduce, adapt, distribute, perform, display,
46 | communicate, and translate a Work;
47 | ii. moral rights retained by the original author(s) and/or performer(s);
48 | iii. publicity and privacy rights pertaining to a person's image or
49 | likeness depicted in a Work;
50 | iv. rights protecting against unfair competition in regards to a Work,
51 | subject to the limitations in paragraph 4(a), below;
52 | v. rights protecting the extraction, dissemination, use and reuse of data
53 | in a Work;
54 | vi. database rights (such as those arising under Directive 96/9/EC of the
55 | European Parliament and of the Council of 11 March 1996 on the legal
56 | protection of databases, and under any national implementation
57 | thereof, including any amended or successor version of such
58 | directive); and
59 | vii. other similar, equivalent or corresponding rights throughout the
60 | world based on applicable law or treaty, and any national
61 | implementations thereof.
62 |
63 | 2. Waiver. To the greatest extent permitted by, but not in contravention
64 | of, applicable law, Affirmer hereby overtly, fully, permanently,
65 | irrevocably and unconditionally waives, abandons, and surrenders all of
66 | Affirmer's Copyright and Related Rights and associated claims and causes
67 | of action, whether now known or unknown (including existing as well as
68 | future claims and causes of action), in the Work (i) in all territories
69 | worldwide, (ii) for the maximum duration provided by applicable law or
70 | treaty (including future time extensions), (iii) in any current or future
71 | medium and for any number of copies, and (iv) for any purpose whatsoever,
72 | including without limitation commercial, advertising or promotional
73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
74 | member of the public at large and to the detriment of Affirmer's heirs and
75 | successors, fully intending that such Waiver shall not be subject to
76 | revocation, rescission, cancellation, termination, or any other legal or
77 | equitable action to disrupt the quiet enjoyment of the Work by the public
78 | as contemplated by Affirmer's express Statement of Purpose.
79 |
80 | 3. Public License Fallback. Should any part of the Waiver for any reason
81 | be judged legally invalid or ineffective under applicable law, then the
82 | Waiver shall be preserved to the maximum extent permitted taking into
83 | account Affirmer's express Statement of Purpose. In addition, to the
84 | extent the Waiver is so judged Affirmer hereby grants to each affected
85 | person a royalty-free, non transferable, non sublicensable, non exclusive,
86 | irrevocable and unconditional license to exercise Affirmer's Copyright and
87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the
88 | maximum duration provided by applicable law or treaty (including future
89 | time extensions), (iii) in any current or future medium and for any number
90 | of copies, and (iv) for any purpose whatsoever, including without
91 | limitation commercial, advertising or promotional purposes (the
92 | "License"). The License shall be deemed effective as of the date CC0 was
93 | applied by Affirmer to the Work. Should any part of the License for any
94 | reason be judged legally invalid or ineffective under applicable law, such
95 | partial invalidity or ineffectiveness shall not invalidate the remainder
96 | of the License, and in such case Affirmer hereby affirms that he or she
97 | will not (i) exercise any of his or her remaining Copyright and Related
98 | Rights in the Work or (ii) assert any associated claims and causes of
99 | action with respect to the Work, in either case contrary to Affirmer's
100 | express Statement of Purpose.
101 |
102 | 4. Limitations and Disclaimers.
103 |
104 | a. No trademark or patent rights held by Affirmer are waived, abandoned,
105 | surrendered, licensed or otherwise affected by this document.
106 | b. Affirmer offers the Work as-is and makes no representations or
107 | warranties of any kind concerning the Work, express, implied,
108 | statutory or otherwise, including without limitation warranties of
109 | title, merchantability, fitness for a particular purpose, non
110 | infringement, or the absence of latent or other defects, accuracy, or
111 | the present or absence of errors, whether or not discoverable, all to
112 | the greatest extent permissible under applicable law.
113 | c. Affirmer disclaims responsibility for clearing rights of other persons
114 | that may apply to the Work or any use thereof, including without
115 | limitation any person's Copyright and Related Rights in the Work.
116 | Further, Affirmer disclaims responsibility for obtaining any necessary
117 | consents, permissions or other rights required for any use of the
118 | Work.
119 | d. Affirmer understands and acknowledges that Creative Commons is not a
120 | party to this document and has no duty or obligation with respect to
121 | this CC0 or use of the Work.
--------------------------------------------------------------------------------
/_posts/2019-02-22-meeting.markdown:
--------------------------------------------------------------------------------
1 | ---
2 | layout: post
3 | title: "Discussion with Prof Pey, Registrar and Prof Dario"
4 | date: 2019-02-22
5 | categories: meeting minutes
6 | ---
7 | Meeting to clarify objectives and concept of Discovery Week.
8 | Concerns raise were:
9 | 1. We need to take note that it is Ramadan
10 | 2. Find ways to reach out to students that are disengaged
11 |
12 | Presented this:
13 | (images are overly large, to view the proper proposal please go [here](https://github.com/Fishbiscuit/Discovery-Week-Project-Site-Test/blob/gh-pages/_posts/2019-02-22-meeting.markdown))
14 | # Concept
15 | Adopting the model of a Conference with large-scale talks targeted at the general audience but also breakout sessions that participants can sign-up for on an individualised manner.
16 |
17 | **Emphasis on personal agency to allow for self-discovery of SUTD's ecosystem.**
18 |
19 | Inspiration:
20 | 1. [AWS Summit](https://aws.amazon.com/summits/singapore/), upcoming [Agenda for April](https://aws.amazon.com/events/summits/singapore/agenda/techfest/)
21 | 2. [Fintech festival](https://fintechfestival.sg/)
22 |
23 | ## Objectives
24 | 1. Freshmores - understand the spaces (virtual and physical), avenues for resources and communities in SUTD in order to embody the desired culture
25 |
26 | **Culture embodying the spirit of innovation, collaboration, having self-initiated projects, self-directed learning and broad-based skill integration**
27 |
28 | 2. SUTD - celebrate the work done by our research community, 5th rows and housing (specifically amongst seniors)
29 |
30 | **Showcase the potential of UROPs and taking up research projects in SUTD, similar to LCC in an interactive/ experiential manner**
31 |
32 | # Planning Parameters
33 | Discovery Week to **take place in the afternoons within the 1st week of term (i.e. 21 May to 24 May)?** Discover Week may tentatively begin from 2pm onwards however do avoid planning activities on Wednesday (22 May) afternoon and the timeslots for Tuesday as stated below.
34 | 
35 |
36 | Take note of Ramadan and be culturally sensitive
37 |
38 | Have a focus on engaging students that are disengaged
39 |
40 | Need to disseminate information clearly (especially academic matters) and resources/ opportunities
41 |
42 | |Key Information|
43 | |--|
44 | |Considering the constraints here, the goal of this team would be to set up sufficient channels for freshmores to have a sustained engagement during **Term 1**.
45 | Rather than relying on mass sessions, to allow them to have a conceptual idea of what might be interesting/important to them and go for it.|
46 |
47 | # Team Composition
48 |
49 | ## Collaboration
50 | - ensure consistent tone throughout all efforts
51 | - fair representation of the community
52 | - must ensure conceptual integrity throughout the events and update key documents that represent this
53 |
54 | ## Communications
55 | 1. Visual branding (guide, logos for events, copy)
56 | 2. Announcement channel (and it's management)
57 | 3. Calendaring
58 |
59 | **Let's ask for a budget for this rather than having to rely on heavy student involvement considering that it's Week 7**
60 |
61 | ## Content
62 | Overview of activities
63 | - Housing Activities
64 | - Pillar info
65 | - Human libraries
66 | - Lightning Talks
67 | - Bands
68 |
69 | # Proposed Activities
70 | ## ! Stakeholder buy-in list
71 | 1. Housing/HG/RLC for hostel access and booking of spaces
72 | 1. Calendar team that ROOT Communications is trying out
73 | 1. Indivudal research labs for access, tour guiding
74 | 2. Pillar reps for introduction to pillar life
75 | 3. Bands for open-mic
76 | 4. Location for open-mic (eg. Mont Calzone/ Crooked Cooks)
77 | 5. DSBJ app devs
78 | 6. Candidates for lightning talks
79 | - GEXP
80 | - ALP
81 | - GLP
82 | - UROP
83 | - Hackathons
84 | `need to shortlist`
85 |
86 | ## Establishing Conceptual Map
87 | 1. User Guide - Gitbook/Github Page/Wiki to explain the program
88 | 2. Demarcate events into 'Levels' based on level of technical difficulty
89 | 3. Static one-stop page to serve as event calendar
90 | 4. Working together with DSBJ app, pending their initial take-up rate and on evaluating their app's roadmap to check for alignment
91 | 5. Using [OpenSUTD](https://opensutd.github.io/OpenSUTD-static-design/) as the go-to conduit into SUTD life
92 | - Fifth Row Guides
93 | - Communication channels for queries
94 | - Knowledge/skills
95 | - Contribution guides
96 | - Proposed wiki format
97 | 7. Badges within the ecosystem so people know who is maintaining what.
98 |   
99 |
100 | ## Academics
101 | 1. Plenary session on general Pillar information
102 | 1. Class simulations conducted by actual students
103 | 1. Open Office Tours for Academic Labs
104 | 1. Lightning Talks targeted at sharing students' experiences working on research projects
105 | 1. OpenSUTD Notes and Project repository sharing, [NUS example](http://isteps.comp.nus.edu.sg/event/12th-steps/module/CS3217)
106 | ## Student Life
107 | 1. Housing
108 | - Getting to know the facilities that people can use
109 | - Getting to know people in your floor including seniors
110 | - Getting to know the academics that stay next door (but take note this must be a purely voluntary basis)
111 | 1. ROOT Cove
112 | - Easter eggs/ hunt the mouse to get people to congregate at this designate student space
113 | - Challenges people can try
114 | 1. ! SAC usage and activities. Also to understand how one can [utilise](https://github.com/OpenSUTD/SAC-student-rules) it
115 | 1. Unified Fifth Row calendar for tryouts
116 | 1. One-stop Telegram message group for information
117 | 1. Human Library
118 | 1. Lightning Talks targeted at sharing the Fifth Row experiences
119 | 1. After-party - Open Mic
120 |
121 | ## Theory of Change
122 | 
123 | Taken from [A novel approach to onboarding](https://blog.hiri.com/a-novel-approach-to-onboarding-4a6c952a3e62)
124 |
125 | |**IF**|**THEN**|
126 | |---|---|
127 | |We define our desired **culture** clearly and it's exhibited **behaviours**| A natural **transition** into university life may occur smoothly|
128 | |Freshmores are introduced to **existing communities** or given the opportunity to start their own. Every Freshmore is **inducted into the people on their floors** and shown how the **spaces in Housing** may be used|The **gap** between freshmores and seniors may be better breached|
129 | |Freshmores are prepared for upcoming projects with **tools, resources, meetups** to get inspiration from. This may result in a **guided project** that culminates in an actual product within the stipulated time|Freshmores will be able to **uncover their personal interests earlier** in the university journey|
130 | |Freshmores need to be shown the **realities of working in SUTD** and have their expectations tempered to realistic levels and the urgency of taking on a project early|We will be able to **identify talented freshmores** to carry on key initiatives and culture-building exercises|
131 | |Emphasise the **potential of projects** as a catalyst for growth|We will be able to **map the state of SUTD** on a yearly basis|
132 |
133 |
134 | ## Stakeholder Map
135 | 
136 | *Pillar Rooms meaning Learning Lab (ISTD), ESD Room, ASD Studios*
137 |
138 | ! Ensuring alignment with [Open House themes](https://openhouse.sutd.edu.sg/why-sutd/). Key objective to show them the embodiment of the 'why SUTD' statements.
139 |
140 | 1. Design-centric education focusing on human-centred solutions
141 | 2. Multi-discplinary curriculum to nurture future-ready graduates
142 | 3. Active, self-directed, collaborative and hands-on learning
143 | 4. Start-up atmosphere brimming with community spirit
144 | 5. Dedicated time to pursue your interests (Weds and Fri half days)
145 |
146 |
147 | ---
148 |
149 | # Review
150 | ## Discovery Week 2018
151 | 
152 | - Students lost interest quite quickly as they had no mental compass as to what events would be useful
153 | - better aesthetic language would be desired
154 | - students are looking for something to transition them into university life to help them cope with Freshmore term
155 | - 13 events spread over two days starting from 0930 and ending at 1630
156 |
157 | ## Other University orientation efforts:
158 | 1. USP academic camp - introduce to incoming scholars the culture expected in the programme
159 | 1. Renaissance engineering programme camp - they undergo a guided project during the camp that is meant to be hands-on
160 |
161 | ## Organisation employee orientation efforts:
162 | 1. Public Service Foundation Course (https://www.cscollege.gov.sg/programmes/pages/display%20programme.aspx?epid=vae3uj66l29irohmc3tpgfolam)
163 | 1. Valve’s employee handbook (https://steamcdn-a.akamaihd.net/apps/valve/Valve_NewEmployeeHandbook.pdf)
164 |
--------------------------------------------------------------------------------
/Concept.md:
--------------------------------------------------------------------------------
1 | Discovery Week (Working Title)
2 | ===
3 | Previous planning [document](https://docs.google.com/document/d/1A_bl4-s3VXOBQe-K85AHm5zBOxTaml8Gq43lHRpIMx8/edit#heading=h.w41sy5e44bpr)
4 |
5 | |Disclaimer|
6 | |---|
7 | |To all who are reading this document or who have stumbled across it.
8 | Activities within this document are suggestions and if you'd like to put an idea down, feel free to do it!
9 | If it is being worked on, it will be expressly stated to prevent duplicate work.
10 | If there's new work being done it will be stated too.
11 | Also if you have a better name for Discovery Week, please do suggest! It's just a working title|
12 |
13 |
14 | # Concept
15 | Adopting the model of a Conference with large-scale talks targeted at the general audience but also breakout sessions that participants can sign-up for on an individualised manner.
16 |
17 | **Emphasis on personal agency to allow for self-discovery of SUTD's ecosystem.**
18 |
19 | Inspiration:
20 | 1. [AWS Summit](https://aws.amazon.com/summits/singapore/), upcoming [Agenda for April](https://aws.amazon.com/events/summits/singapore/agenda/techfest/)
21 | 2. [Fintech festival](https://fintechfestival.sg/)
22 |
23 | ## Objectives
24 | 1. Freshmores - understand the spaces (virtual and physical), avenues for resources and communities in SUTD in order to embody the desired culture
25 |
26 | **Culture embodying the spirit of innovation, collaboration, having self-initiated projects, self-directed learning and broad-based skill integration**
27 |
28 | 2. SUTD - celebrate the work done by our research community, 5th rows and housing (specifically amongst seniors)
29 |
30 | **Showcase the potential of UROPs and taking up research projects in SUTD, similar to LCC in an interactive/ experiential manner**
31 |
32 | # Planning Parameters
33 | Discovery Week to **take place in the afternoons within the 1st week of term (i.e. 21 May to 24 May)?** Discover Week may tentatively begin from 2pm onwards however do avoid planning activities on Wednesday (22 May) afternoon and the timeslots for Tuesday as stated below.
34 | 
35 |
36 | Take note of Ramadan and be culturally sensitive
37 |
38 | Have a focus on engaging students that are disengaged
39 |
40 | Need to disseminate information clearly (especially academic matters) and resources/ opportunities
41 |
42 | |Key Information|
43 | |--|
44 | |Considering the constraints here, the goal of this team would be to set up sufficient channels for freshmores to have a sustained engagement during **Term 1**.
45 | Rather than relying on mass sessions, to allow them to have a conceptual idea of what might be interesting/important to them and go for it.|
46 |
47 | # Team Composition
48 |
49 | ## Collaboration
50 | - ensure consistent tone throughout all efforts
51 | - fair representation of the community
52 | - must ensure conceptual integrity throughout the events and update key documents that represent this
53 |
54 | ## Communications
55 | 1. Visual branding (guide, logos for events, copy)
56 | 2. Announcement channel (and it's management)
57 | 3. Calendaring
58 |
59 | **Let's ask for a budget for this rather than having to rely on heavy student involvement considering that it's Week 7**
60 |
61 | ## Content
62 | Overview of activities
63 | - Housing Activities
64 | - Pillar info
65 | - Human libraries
66 | - Lightning Talks
67 | - Bands
68 |
69 | # Proposed Activities
70 | ## ! Stakeholder buy-in list
71 | 1. Housing/HG/RLC for hostel access and booking of spaces
72 | 1. Calendar team that ROOT Communications is trying out
73 | 1. Indivudal research labs for access, tour guiding
74 | 2. Pillar reps for introduction to pillar life
75 | 3. Bands for open-mic
76 | 4. Location for open-mic (eg. Mont Calzone/ Crooked Cooks)
77 | 5. DSBJ app devs
78 | 6. Candidates for lightning talks
79 | - GEXP
80 | - ALP
81 | - GLP
82 | - UROP
83 | - Hackathons
84 | `need to shortlist`
85 |
86 | ## Establishing Conceptual Map
87 | 1. User Guide - Gitbook/Github Page/Wiki to explain the program
88 | 2. Demarcate events into 'Levels' based on level of technical difficulty
89 | 3. Static one-stop page to serve as event calendar
90 | 4. Working together with DSBJ app, pending their initial take-up rate and on evaluating their app's roadmap to check for alignment
91 | 5. Using [OpenSUTD](https://opensutd.github.io/OpenSUTD-static-design/) as the go-to conduit into SUTD life
92 | - Fifth Row Guides
93 | - Communication channels for queries
94 | - Knowledge/skills
95 | - Contribution guides
96 | - Proposed wiki format
97 | 7. Badges within the ecosystem so people know who is maintaining what.
98 |   
99 |
100 | ## Academics
101 | 1. Plenary session on general Pillar information
102 | 1. Class simulations conducted by actual students
103 | 1. Open Office Tours for Academic Labs
104 | 1. Lightning Talks targeted at sharing students' experiences working on research projects
105 | 1. OpenSUTD Notes and Project repository sharing, [NUS example](http://isteps.comp.nus.edu.sg/event/12th-steps/module/CS3217)
106 | ## Student Life
107 | 1. Housing
108 | - Getting to know the facilities that people can use
109 | - Getting to know people in your floor including seniors
110 | - Getting to know the academics that stay next door (but take note this must be a purely voluntary basis)
111 | 1. ROOT Cove
112 | - Easter eggs/ hunt the mouse to get people to congregate at this designate student space
113 | - Challenges people can try
114 | 1. ! SAC usage and activities. Also to understand how one can [utilise](https://github.com/OpenSUTD/SAC-student-rules) it
115 | 1. Unified Fifth Row calendar for tryouts
116 | 1. One-stop Telegram message group for information
117 | 1. Human Library
118 | 1. Lightning Talks targeted at sharing the Fifth Row experiences
119 | 1. After-party - Open Mic
120 |
121 | ## Theory of Change
122 | 
123 | Taken from [A novel approach to onboarding](https://blog.hiri.com/a-novel-approach-to-onboarding-4a6c952a3e62)
124 |
125 | |**IF**|**THEN**|
126 | |---|---|
127 | |We define our desired **culture** clearly and it's exhibited **behaviours**| A natural **transition** into university life may occur smoothly|
128 | |Freshmores are introduced to **existing communities** or given the opportunity to start their own. Every Freshmore is **inducted into the people on their floors** and shown how the **spaces in Housing** may be used|The **gap** between freshmores and seniors may be better breached|
129 | |Freshmores are prepared for upcoming projects with **tools, resources, meetups** to get inspiration from. This may result in a **guided project** that culminates in an actual product within the stipulated time|Freshmores will be able to **uncover their personal interests earlier** in the university journey|
130 | |Freshmores need to be shown the **realities of working in SUTD** and have their expectations tempered to realistic levels and the urgency of taking on a project early|We will be able to **identify talented freshmores** to carry on key initiatives and culture-building exercises|
131 | |Emphasise the **potential of projects** as a catalyst for growth|We will be able to **map the state of SUTD** on a yearly basis|
132 |
133 |
134 | ## Stakeholder Map
135 | 
136 | *Pillar Rooms meaning Learning Lab (ISTD), ESD Room, ASD Studios*
137 |
138 | ! Ensuring alignment with [Open House themes](https://openhouse.sutd.edu.sg/why-sutd/). Key objective to show them the embodiment of the 'why SUTD' statements.
139 |
140 | 1. Design-centric education focusing on human-centred solutions
141 | 2. Multi-discplinary curriculum to nurture future-ready graduates
142 | 3. Active, self-directed, collaborative and hands-on learning
143 | 4. Start-up atmosphere brimming with community spirit
144 | 5. Dedicated time to pursue your interests (Weds and Fri half days)
145 |
146 |
147 | ---
148 |
149 | # Review
150 | ## Discovery Week 2018
151 | 
152 | - Students lost interest quite quickly as they had no mental compass as to what events would be useful
153 | - better aesthetic language would be desired
154 | - students are looking for something to transition them into university life to help them cope with Freshmore term
155 | - 13 events spread over two days starting from 0930 and ending at 1630
156 |
157 | ## Other University orientation efforts:
158 | 1. USP academic camp - introduce to incoming scholars the culture expected in the programme
159 | 1. Renaissance engineering programme camp - they undergo a guided project during the camp that is meant to be hands-on
160 |
161 | ## Organisation employee orientation efforts:
162 | 1. Public Service Foundation Course (https://www.cscollege.gov.sg/programmes/pages/display%20programme.aspx?epid=vae3uj66l29irohmc3tpgfolam)
163 | 1. Valve’s employee handbook (https://steamcdn-a.akamaihd.net/apps/valve/Valve_NewEmployeeHandbook.pdf)
164 |
--------------------------------------------------------------------------------
/assets/css/normalize.css:
--------------------------------------------------------------------------------
1 | /*! normalize.css v2.1.3 | MIT License | git.io/normalize */
2 |
3 | /* ==========================================================================
4 | HTML5 display definitions
5 | ========================================================================== */
6 |
7 | /**
8 | * Correct `block` display not defined in IE 8/9.
9 | */
10 |
11 | article,
12 | aside,
13 | details,
14 | figcaption,
15 | figure,
16 | footer,
17 | header,
18 | hgroup,
19 | main,
20 | nav,
21 | section,
22 | summary {
23 | display: block;
24 | }
25 |
26 | /**
27 | * Correct `inline-block` display not defined in IE 8/9.
28 | */
29 |
30 | audio,
31 | canvas,
32 | video {
33 | display: inline-block;
34 | }
35 |
36 | /**
37 | * Prevent modern browsers from displaying `audio` without controls.
38 | * Remove excess height in iOS 5 devices.
39 | */
40 |
41 | audio:not([controls]) {
42 | display: none;
43 | height: 0;
44 | }
45 |
46 | /**
47 | * Address `[hidden]` styling not present in IE 8/9.
48 | * Hide the `template` element in IE, Safari, and Firefox < 22.
49 | */
50 |
51 | [hidden],
52 | template {
53 | display: none;
54 | }
55 |
56 | /* ==========================================================================
57 | Base
58 | ========================================================================== */
59 |
60 | /**
61 | * 1. Set default font family to sans-serif.
62 | * 2. Prevent iOS text size adjust after orientation change, without disabling
63 | * user zoom.
64 | */
65 |
66 | html {
67 | font-family: sans-serif; /* 1 */
68 | -ms-text-size-adjust: 100%; /* 2 */
69 | -webkit-text-size-adjust: 100%; /* 2 */
70 | }
71 |
72 | /**
73 | * Remove default margin.
74 | */
75 |
76 | body {
77 | margin: 0;
78 | }
79 |
80 | /* ==========================================================================
81 | Links
82 | ========================================================================== */
83 |
84 | /**
85 | * Remove the gray background color from active links in IE 10.
86 | */
87 |
88 | a {
89 | background: transparent;
90 | }
91 |
92 | /**
93 | * Address `outline` inconsistency between Chrome and other browsers.
94 | */
95 |
96 | a:focus {
97 | outline: thin dotted;
98 | }
99 |
100 | /**
101 | * Improve readability when focused and also mouse hovered in all browsers.
102 | */
103 |
104 | a:active,
105 | a:hover {
106 | outline: 0;
107 | }
108 |
109 | /* ==========================================================================
110 | Typography
111 | ========================================================================== */
112 |
113 | /**
114 | * Address variable `h1` font-size and margin within `section` and `article`
115 | * contexts in Firefox 4+, Safari 5, and Chrome.
116 | */
117 |
118 | h1 {
119 | font-size: 2em;
120 | margin: 0.67em 0;
121 | }
122 |
123 | /**
124 | * Address styling not present in IE 8/9, Safari 5, and Chrome.
125 | */
126 |
127 | abbr[title] {
128 | border-bottom: 1px dotted;
129 | }
130 |
131 | /**
132 | * Address style set to `bolder` in Firefox 4+, Safari 5, and Chrome.
133 | */
134 |
135 | b,
136 | strong {
137 | font-weight: bold;
138 | }
139 |
140 | /**
141 | * Address styling not present in Safari 5 and Chrome.
142 | */
143 |
144 | dfn {
145 | font-style: italic;
146 | }
147 |
148 | /**
149 | * Address differences between Firefox and other browsers.
150 | */
151 |
152 | hr {
153 | -moz-box-sizing: content-box;
154 | box-sizing: content-box;
155 | height: 0;
156 | }
157 |
158 | /**
159 | * Address styling not present in IE 8/9.
160 | */
161 |
162 | mark {
163 | background: #ff0;
164 | color: #000;
165 | }
166 |
167 | /**
168 | * Correct font family set oddly in Safari 5 and Chrome.
169 | */
170 |
171 | code,
172 | kbd,
173 | pre,
174 | samp {
175 | font-family: monospace, serif;
176 | font-size: 1em;
177 | }
178 |
179 | /**
180 | * Improve readability of pre-formatted text in all browsers.
181 | */
182 |
183 | pre {
184 | white-space: pre-wrap;
185 | }
186 |
187 | /**
188 | * Set consistent quote types.
189 | */
190 |
191 | q {
192 | quotes: "\201C" "\201D" "\2018" "\2019";
193 | }
194 |
195 | /**
196 | * Address inconsistent and variable font size in all browsers.
197 | */
198 |
199 | small {
200 | font-size: 80%;
201 | }
202 |
203 | /**
204 | * Prevent `sub` and `sup` affecting `line-height` in all browsers.
205 | */
206 |
207 | sub,
208 | sup {
209 | font-size: 75%;
210 | line-height: 0;
211 | position: relative;
212 | vertical-align: baseline;
213 | }
214 |
215 | sup {
216 | top: -0.5em;
217 | }
218 |
219 | sub {
220 | bottom: -0.25em;
221 | }
222 |
223 | /* ==========================================================================
224 | Embedded content
225 | ========================================================================== */
226 |
227 | /**
228 | * Remove border when inside `a` element in IE 8/9.
229 | */
230 |
231 | img {
232 | border: 0;
233 | }
234 |
235 | /**
236 | * Correct overflow displayed oddly in IE 9.
237 | */
238 |
239 | svg:not(:root) {
240 | overflow: hidden;
241 | }
242 |
243 | /* ==========================================================================
244 | Figures
245 | ========================================================================== */
246 |
247 | /**
248 | * Address margin not present in IE 8/9 and Safari 5.
249 | */
250 |
251 | figure {
252 | margin: 0;
253 | }
254 |
255 | /* ==========================================================================
256 | Forms
257 | ========================================================================== */
258 |
259 | /**
260 | * Define consistent border, margin, and padding.
261 | */
262 |
263 | fieldset {
264 | border: 1px solid #c0c0c0;
265 | margin: 0 2px;
266 | padding: 0.35em 0.625em 0.75em;
267 | }
268 |
269 | /**
270 | * 1. Correct `color` not being inherited in IE 8/9.
271 | * 2. Remove padding so people aren't caught out if they zero out fieldsets.
272 | */
273 |
274 | legend {
275 | border: 0; /* 1 */
276 | padding: 0; /* 2 */
277 | }
278 |
279 | /**
280 | * 1. Correct font family not being inherited in all browsers.
281 | * 2. Correct font size not being inherited in all browsers.
282 | * 3. Address margins set differently in Firefox 4+, Safari 5, and Chrome.
283 | */
284 |
285 | button,
286 | input,
287 | select,
288 | textarea {
289 | font-family: inherit; /* 1 */
290 | font-size: 100%; /* 2 */
291 | margin: 0; /* 3 */
292 | }
293 |
294 | /**
295 | * Address Firefox 4+ setting `line-height` on `input` using `!important` in
296 | * the UA stylesheet.
297 | */
298 |
299 | button,
300 | input {
301 | line-height: normal;
302 | }
303 |
304 | /**
305 | * Address inconsistent `text-transform` inheritance for `button` and `select`.
306 | * All other form control elements do not inherit `text-transform` values.
307 | * Correct `button` style inheritance in Chrome, Safari 5+, and IE 8+.
308 | * Correct `select` style inheritance in Firefox 4+ and Opera.
309 | */
310 |
311 | button,
312 | select {
313 | text-transform: none;
314 | }
315 |
316 | /**
317 | * 1. Avoid the WebKit bug in Android 4.0.* where (2) destroys native `audio`
318 | * and `video` controls.
319 | * 2. Correct inability to style clickable `input` types in iOS.
320 | * 3. Improve usability and consistency of cursor style between image-type
321 | * `input` and others.
322 | */
323 |
324 | button,
325 | html input[type="button"], /* 1 */
326 | input[type="reset"],
327 | input[type="submit"] {
328 | -webkit-appearance: button; /* 2 */
329 | cursor: pointer; /* 3 */
330 | }
331 |
332 | /**
333 | * Re-set default cursor for disabled elements.
334 | */
335 |
336 | button[disabled],
337 | html input[disabled] {
338 | cursor: default;
339 | }
340 |
341 | /**
342 | * 1. Address box sizing set to `content-box` in IE 8/9/10.
343 | * 2. Remove excess padding in IE 8/9/10.
344 | */
345 |
346 | input[type="checkbox"],
347 | input[type="radio"] {
348 | box-sizing: border-box; /* 1 */
349 | padding: 0; /* 2 */
350 | }
351 |
352 | /**
353 | * 1. Address `appearance` set to `searchfield` in Safari 5 and Chrome.
354 | * 2. Address `box-sizing` set to `border-box` in Safari 5 and Chrome
355 | * (include `-moz` to future-proof).
356 | */
357 |
358 | input[type="search"] {
359 | -webkit-appearance: textfield; /* 1 */
360 | -moz-box-sizing: content-box;
361 | -webkit-box-sizing: content-box; /* 2 */
362 | box-sizing: content-box;
363 | }
364 |
365 | /**
366 | * Remove inner padding and search cancel button in Safari 5 and Chrome
367 | * on OS X.
368 | */
369 |
370 | input[type="search"]::-webkit-search-cancel-button,
371 | input[type="search"]::-webkit-search-decoration {
372 | -webkit-appearance: none;
373 | }
374 |
375 | /**
376 | * Remove inner padding and border in Firefox 4+.
377 | */
378 |
379 | button::-moz-focus-inner,
380 | input::-moz-focus-inner {
381 | border: 0;
382 | padding: 0;
383 | }
384 |
385 | /**
386 | * 1. Remove default vertical scrollbar in IE 8/9.
387 | * 2. Improve readability and alignment in all browsers.
388 | */
389 |
390 | textarea {
391 | overflow: auto; /* 1 */
392 | vertical-align: top; /* 2 */
393 | }
394 |
395 | /* ==========================================================================
396 | Tables
397 | ========================================================================== */
398 |
399 | /**
400 | * Remove most spacing between table cells.
401 | */
402 |
403 | table {
404 | border-collapse: collapse;
405 | border-spacing: 0;
406 | }
--------------------------------------------------------------------------------
/assets/css/main.css:
--------------------------------------------------------------------------------
1 | ---
2 | ---
3 |
4 | /*
5 | Main.css
6 | ==================================
7 | Begin with generic 'mobile first' styles
8 | */
9 |
10 | /*
11 | Normalize the box model
12 | ==================================
13 | */
14 |
15 | *,
16 | *:before,
17 | *:after {
18 | -webkit-box-sizing: border-box;
19 | -moz-box-sizing: border-box;
20 | box-sizing: border-box;
21 | }
22 |
23 | /*
24 | global styles
25 | ==================================
26 | */
27 |
28 | html, body {
29 | height: 100%;
30 | }
31 |
32 | /*
33 | Typography
34 | ==================================
35 | */
36 |
37 | body {
38 | font-family: "Avenir Next", Arial, sans-serif;
39 | font-weight: 400;
40 | font-style: normal;
41 | line-height: 1.466666667;
42 | }
43 |
44 | h1,
45 | h3,
46 | h4,
47 | h5,
48 | strong {
49 | font-family: "Avenir Next Demi", "Avenir Next", Arial, sans-serif;
50 | font-weight: 600;
51 | }
52 |
53 | .site-title {
54 | font-size: 1.625em;
55 | font-family: "Avenir Next", Arial, sans-serif;
56 | font-weight: normal;
57 | color: #919395;
58 | margin: 0;
59 | line-height: 1.2941176470588236;
60 | display: inline-block;
61 | }
62 |
63 | h2 {
64 | font-weight: 400;
65 | font-style: normal;
66 | font-size: 1.375em;
67 | margin: 1.4em 0 0 0;
68 | }
69 |
70 | h4 {
71 | font-size: 1em;
72 | text-transform: uppercase;
73 | }
74 |
75 | .page-title {
76 | margin-top: .727272727em; /* 16/22 */
77 | }
78 |
79 | /*
80 | Lists
81 | --------------------------------
82 | */
83 |
84 | .main-content ul {
85 | padding-left: 1.1em;
86 | }
87 |
88 | .main-content li {
89 | margin-bottom: 1em;
90 | }
91 |
92 | li h3,
93 | li h4 {
94 | margin: 0;
95 | }
96 |
97 | li p {
98 | margin-top: 0;
99 | }
100 |
101 | /*
102 | Links
103 | ==================================
104 | */
105 |
106 | a {
107 | -webkit-transition: .2s;
108 | -moz-transition: .2s;
109 | transition: .2s;
110 | }
111 |
112 | a,
113 | a:link,
114 | a:visited {
115 | color: #0072ce;
116 | border-bottom: 1px dotted #0072ce;
117 | text-decoration: none;
118 | }
119 |
120 | a:hover {
121 | border-bottom: 1px solid #7eb8dd;
122 | color: #7eb8dd;
123 | text-decoration: none;
124 | }
125 |
126 | a:active {
127 | border-bottom: 1px solid #002d72;
128 | color: #002d72;
129 | text-decoration: none;
130 | }
131 |
132 | a:focus {
133 | border-bottom: 1px solid #0072ce;
134 | color: #0072ce;
135 | outline: thin dotted;
136 | text-decoration: none;
137 | }
138 |
139 | a.title-link {
140 | color: #75787B;
141 | border-bottom: none;
142 | }
143 |
144 | a.title-link:hover,
145 | a.title-link:active,
146 | a.title-link:focus {
147 | color: #7eb8dd;
148 | border-bottom: none;
149 | }
150 |
151 | a.skip-link {
152 | color: #0072ce;
153 | border-bottom: none;
154 | padding: .25em;
155 | }
156 |
157 | a.skip-link:hover,
158 | a.skip-link:active,
159 | a.skip-link:focus {
160 | background-color: #0072ce;
161 | color: #fff;
162 | border-bottom: none;
163 | }
164 |
165 |
166 | /*
167 | Navigation
168 | ==================================
169 | */
170 |
171 | .sidebar-nav a {
172 | display: block;
173 | padding: 10px;
174 | -webkit-transition: unset;
175 | transition: unset;
176 | }
177 | .sidebar-nav a,
178 | .sidebar-nav a:link,
179 | .sidebar-nav a:visited {
180 | border-bottom: none;
181 | color: #75787b;
182 | }
183 | .sidebar-nav li:hover,
184 | .sidebar-nav a:focus,
185 | .sidebar-nav li:active,
186 | .sidebar-nav .sidebar-nav-active {
187 | color: #75787b;
188 | border-left: 4px solid {{ site.brand_color }};
189 | background-color: transparent;
190 | border-bottom: 1px solid #babbbd;
191 | }
192 | .sidebar-nav li:hover,
193 | .sidebar-nav li:active,
194 | .sidebar-nav .sidebar-nav-active {
195 | padding-left: 0;
196 | }
197 | .sidebar-nav a:focus {
198 | padding-left: 6px;
199 | }
200 | .sidebar-nav li:hover a:focus,
201 | .sidebar-nav li:active a:focus {
202 | border-left: none;
203 | padding-left: 10px;
204 | }
205 | .sidebar-nav ul {
206 | margin: 0;
207 | padding: 0;
208 | /*border-top: 1px solid @gray-50;*/
209 | }
210 | .sidebar-nav li {
211 | list-style: none;
212 | border-bottom: 1px solid #babbbd;
213 | font-size: 1.125em;
214 | padding-left: 4px;
215 | }
216 | .sidebar-nav li:last-child {
217 | border-bottom: none;
218 | }
219 |
220 |
221 | /*
222 | Layout
223 | ==================================
224 | */
225 |
226 | .logo {
227 | display: block;
228 | }
229 |
230 | .content {
231 | padding-top: 2em;
232 | padding-bottom: 2em;
233 | }
234 |
235 | /* offset the fixed position header for jump links */
236 | section:before {
237 | display: block;
238 | content: "";
239 | height: 60px;
240 | margin: -60px 0 0;
241 | }
242 |
243 | .wrap {
244 | max-width: 1200px;
245 | margin: 0 auto;
246 | padding-left: 20px;
247 | padding-right: 20px;
248 | }
249 |
250 | header {
251 | width: 100%;
252 | border-bottom: 4px solid {{ site.brand_color }};
253 | background-color: #fff;
254 | padding: 2em 0;
255 | }
256 |
257 |
258 | /*
259 | Footer
260 | ==================================
261 | */
262 |
263 | /* for sticky footer */
264 | .container {
265 | display: table;
266 | height: 100%;
267 | width: 100%;
268 | }
269 |
270 | footer {
271 | display: table-row; /* for sticky footer */
272 | height: 1px; /* for sticky footer */
273 | border-top: 2px solid #babbbd;
274 | background: #f1f2f2;
275 | width: 100%;
276 | font-size: 0.875em;
277 | }
278 |
279 | footer .wrap {
280 | padding-top: 2em;
281 | padding-bottom: 2em;
282 | }
283 |
284 |
285 | /*
286 | Helpers
287 | ==================================
288 | */
289 |
290 | /* Hide from both screenreaders and browsers: h5bp.com/u */
291 | .hidden {
292 | display: none !important;
293 | visibility: hidden;
294 | }
295 |
296 | /* Hide only visually, but have it available for screenreaders: h5bp.com/v */
297 | .visuallyhidden {
298 | border: 0;
299 | clip: rect(0 0 0 0);
300 | height: 1px;
301 | margin: -1px;
302 | overflow: hidden;
303 | padding: 0;
304 | position: absolute;
305 | width: 1px;
306 | }
307 |
308 | /* Extends the .visuallyhidden class to allow the element to be focusable
309 | * when navigated to via the keyboard: h5bp.com/p */
310 | .visuallyhidden.focusable:active,
311 | .visuallyhidden.focusable:focus {
312 | clip: auto;
313 | height: auto;
314 | margin: 0;
315 | overflow: visible;
316 | position: static;
317 | width: auto;
318 | }
319 |
320 | /* Hide visually and from screenreaders, but maintain layout */
321 | .invisible {
322 | visibility: hidden;
323 | }
324 |
325 |
326 | /*
327 | Style
328 | ==================================
329 | */
330 |
331 | .intro {
332 | color: #75787B;
333 | }
334 |
335 | li h4 {
336 | margin: 0;
337 | }
338 |
339 | .license {
340 | font-family: "Avenir Next Demi", Arial, sans-serif;
341 | font-weight: normal;
342 | font-style: normal;
343 | }
344 |
345 | pre {
346 | max-width: 100%;
347 | font-size: 0.875em;
348 | overflow-y: scroll;
349 | background-color: #f1f2f2;
350 | padding: 10px;
351 | }
352 |
353 | /*
354 | Post list
355 | ----------------------------------
356 | */
357 |
358 | ul.posts {
359 | padding: 0;
360 | }
361 |
362 | .posts li {
363 | list-style: none;
364 | }
365 |
366 | .post-date {
367 | color: #75787B;
368 | }
369 |
370 | /*
371 | Repo list
372 | ----------------------------------
373 | */
374 |
375 | ul.repo-list {
376 | margin: .5em 0 1em 0;
377 | padding: 0;
378 | }
379 |
380 | .repo-list li {
381 | list-style: none;
382 | }
383 |
384 | .repo-list p {
385 | margin: 0;
386 | font-size: 0.875em;
387 | }
388 |
389 | .repo-list h4 {
390 | text-transform: none;
391 | }
392 |
393 | /*
394 | Helper Classes
395 | ==================================
396 | */
397 |
398 | /*
399 | Clearfix list
400 | ----------------------------------
401 | */
402 |
403 | .group:before,
404 | .group:after {
405 | content: " ";
406 | display: table;
407 | }
408 |
409 | .group:after {
410 | clear: both;
411 | }
412 |
413 | .group {
414 | *zoom: 1;
415 | }
416 |
417 | /*
418 | Desktop Styles
419 | ==================================
420 | */
421 |
422 | @media screen and (min-width: 45em) and (min-height: 32.5em) {
423 |
424 | /*
425 | Typography
426 | ==============================
427 | */
428 |
429 | /*
430 | Layout
431 | ==============================
432 | */
433 |
434 | .logo {
435 | max-width: 30%;
436 | padding-right: 20px;
437 | float: right;
438 | }
439 |
440 | aside {
441 | width: 30%;
442 | float: left;
443 | }
444 |
445 | .main-content {
446 | width: 67%;
447 | float: right;
448 | margin-bottom: 120px;
449 | }
450 |
451 | /*
452 | Navigation
453 | ==============================
454 | */
455 |
456 |
457 | /*
458 | Style
459 | ==============================
460 | */
461 |
462 | /*
463 | Repo list
464 | ------------------------------
465 | */
466 |
467 | .repo-list li {
468 | list-style: none;
469 | display: block;
470 | float: left;
471 | height: 4.0625em;
472 | max-height: 4.0625em;
473 | background-color: #E7E7E6;
474 | border-left: 1px solid #BABBBD;
475 | width: 30%;
476 | }
477 |
478 | .repo-list a:link,
479 | .repo-list a:visited {
480 | display: block;
481 | max-height: 4.0625em;
482 | background-color: #E7E7E6;
483 | border-bottom: none;
484 | padding: .625em 1em 1em 1em;
485 | }
486 |
487 | .repo-list a:hover {
488 | color: #4D5F87;
489 | background-color: #CDE3F1;
490 | }
491 |
492 | .repo-list li:first-child {
493 | text-align: center;
494 | border-left: none;
495 | line-height: 60px;
496 | padding: .625em 1em;
497 | width: 10%;
498 | }
499 |
500 | }
501 |
502 | @media screen and (max-width: 54.375em) and (min-height: 32.5em) {
503 |
504 | /* keep the repo list containers the same height, but account for the need for more height */
505 |
506 | .repo-list li {
507 | height: 6em;
508 | max-height: 6em;
509 | }
510 |
511 | .repo-list a:link,
512 | .repo-list a:visited {
513 | max-height: 6em;
514 | }
515 | }
516 |
517 | /*
518 | Mobile Styles
519 | ==================================
520 | */
521 |
522 | @media screen and (max-width: 40.5em) {
523 |
524 | .main-content {
525 | margin-top: 1.5em;
526 | }
527 |
528 | }
529 |
--------------------------------------------------------------------------------
14 |
15 | {% for repo in site.repos %}
16 |