diff --git a/assets/scss/front-page.scss b/assets/scss/front-page.scss index f89d9d5e..047e9025 100644 --- a/assets/scss/front-page.scss +++ b/assets/scss/front-page.scss @@ -124,10 +124,6 @@ $font-small: 0.9rem; margin-bottom: 0.5rem; @extend .clear-list; } - a { - text-decoration: underline; - color: $gray-600; - } } .events { diff --git a/config.toml b/config.toml index 370a8760..938e4d6e 100644 --- a/config.toml +++ b/config.toml @@ -23,22 +23,17 @@ googleAnalytics = "UA-141681743-1" weight = 1 url = "/about" [[menu.main]] - name = "Discussion" - identifier = "Discussion" + name = "Community" + identifier = "Community" weight = 2 - url = "/discussion" + url = "/community" [[menu.main]] name = "Events" identifier = "Events" weight = 3 - url = "/events" -[[menu.main]] - name = "Code" - identifier = "Code" - weight = 4 - url = "/code" + url = "/about/#what-we-do" [[menu.main]] name = "Contact" identifier = "Contact" - weight = 5 + weight = 4 url = "/contact" diff --git a/content/about/_index.md b/content/about/_index.md index f0e2f5aa..13374500 100644 --- a/content/about/_index.md +++ b/content/about/_index.md @@ -1,40 +1,47 @@ --- title: About -description: About NUSHackers +description: About NUS Hackers date: "2014-05-02" --- -In the jargon of the computer programmer, a hacker is someone who strives to solve problems in elegant and ingenious ways. NUS Hackers is a student-run organization committed to the spread of hacker culture & free/open-source software. We provide a support system for hackers in NUS who are currently building things (be it for charity, business or pleasure). We also hold workshops, run technical meetups, organize hackathons, and maintain open source code for the NUS community. +In the jargon of the computer programmer, a hacker is someone who strives to solve problems in elegant and ingenious ways. -## What We Do +NUS Hackers is a student-run organization committed to the spread of hacker culture and free, open source software. We provide a support system for hackers in NUS who are currently building things, be it for charity, business or pleasure. We also hold workshops, run technical meetups, organize hackathons, and maintain open source code for the NUS community. -We have weekly meetups every Friday called [Friday Hacks](/fridayhacks/). They include one or two technical talks, followed by a hacking session. +## What we do -Every semester, we run a series of technical workshops called [hackerschool](//school.nushackers.org/). We also run the Hack&Roll hackathon in the second semester of the academic year. Our coreteam members contribute to events like LadyPy and Software Freedom Day. +During the semester, our primary events include -We maintain and release open source code for the NUS community (see: our [code page](/code/)). Students and staff who have built NUS-specific projects and can no longer maintain them may come to us to host and maintain their code. +* weekly meetups every Friday called [Friday Hacks]({{< ref "/fridayhacks" >}}) that include one or two technical talks, sometimes followed by a hacking session; +* workshops on Tuesdays called Hacker Tools that cover skills that are essential to those in computing fields but are not usually taught by schools; and +* workshops on Saturdays called [hackerschool](https://school.nushackers.org/) that cover a range of technical topics, and are aimed at introducing technologies to those who have no prior knowledge. -We currently maintain [Download@NUS](//download.nus.edu.sg/) We have a team working with the NUS Computer Centre to host linux mirrors. +Near the start of each calendar year, we also run [Hack&Roll](https://hacknroll.nushackers.org/), the largest student-run hackathon in Singapore. Hack&Roll is unique for being one of the few hackathons, if not the only, that do not have a set topic for participants; instead, the aim is to simply encourage people to come and have fun building something. + +We also run smaller events for the NUS community, like Project Intern, where students who have interned share with others their experience and the benefits they have gained from interning, in a bid to encourage others to intern. + +Some of our events are recorded if consent is given by the relevant parties. Find our recordings [here]({{< ref "/recordings" >}}). ## Philosophy -We believe that hacking is necessary for good innovation. (In fact, the best computer-related startups and technologies [have all come from hackers](/why/)). As an extension to that, we think tinkering is win-win-win: you learn new things, you get to show off, and you become more attractive to employers. +We believe that hacking is necessary for good innovation. (In fact, the best computer-related startups and technologies [have all come from hackers]({{< ref "/why" >}}).) As an extension to that, we think tinkering is win-win-win: you learn new things, you get to show off, and you become more attractive to employers. -(Though, honestly, most of the time we hack because we think it's fun). +(Though, honestly, most of the time we hack because it's fun.) ## Goal -Our long term goal is to build a healthy community of passionate hackers in NUS. We think that this benefits everyone: professors benefit because they are able to source for good programmers; startups and tech companies benefit because they are able to recruit from a central pool; students benefit because they get to meet and learn from like-minded peers (and get opportunities, i.e.: from professors and tech companies). -## Management +Our long term goal is to build a healthy community of passionate hackers in NUS. We think that this benefits everyone: professors benefit because they are able to source for good programmers; startups and tech companies benefit because they are able to recruit from a central pool; and students benefit because they get to meet and learn from like-minded peers (and get opportunities from professors and tech companies). -NUS Hackers is managed by a coreteam of student-volunteers. If you'd like to request a workshop, get us to publicize your code, or ask us a question, we recommend that you [send us an email](/contact/). +## Coreteam -## Current Coreteam +NUS Hackers is managed by a coreteam of student volunteers. You can reach us by [email]({{< ref "/contact" >}}). + +### Coreteam members {{< members >}} -## Alumni -We keep a list of former NUS Hackers coreteam members [over at our alumni page →](/alumni/) +[Alumni →]({{< ref "/alumni" >}}) ## Join us -Want to help us spread the hacker culture? You can find out more [here](/join-coreteam/). + +Want to help us in spreading hacker culture? [We want you!](({{< ref "/join-coreteam" >}})) diff --git a/content/about/what-is-hacking.md b/content/about/what-is-hacking.md index 928051ef..dcd11c92 100644 --- a/content/about/what-is-hacking.md +++ b/content/about/what-is-hacking.md @@ -4,10 +4,10 @@ description: What is hacking? date: "2014-05-02" --- -### What is Hacking? +### What is hacking? -The simplest way to define hacking is: 'playful cleverness'. We usually take it to mean the act of creating interesting software, but 'playful cleverness' may be applied to all sorts of things: life, music, hardware, food. More on this → +The simplest way to define hacking is _playful cleverness_. We usually take it to mean the act of creating interesting software, but _playful cleverness_ may be applied to all sorts of things: life, music, hardware, food. [More on this →]({{< ref "/hackerdefined" >}}) ### Formerly linuxNUS -We were formerly known as linuxNUS, an open source advocate in NUS. We have since changed our name to reflect the shifting nature of our organization: we now spend more time promoting hacking, programming-for-fun, and free/open-source-software use in the NUS community. More on the name change → +We were formerly known as linuxNUS, an open source advocate in NUS. We have since changed our name to reflect the shifting nature of our organization: we now spend more time promoting hacking, programming-for-fun, and the use of free, open source software in the NUS community. [More on the name change →]({{< ref "/name-change" >}}) diff --git a/content/code/_index.md b/content/code/_index.md deleted file mode 100755 index a9c0d206..00000000 --- a/content/code/_index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Code -description: Our source code -date: "2014-06-23" ---- - -We manage an nushackers git repository on github.com. It contains things like source code of this web site and source code of our hackerschool website. Free feel to clone/fork any of those or, even better, send us pull requests! - -If you are a NUS student/staff, we also have a repository for your projects: [//code.nushackers.org](//code.nushackers.org) - use it to showcase your work! After doing so, you are welcome to contact us if you want us to maintain and publicize your code! diff --git a/content/code/in-support-of-git.md b/content/code/in-support-of-git.md deleted file mode 100644 index ab809df7..00000000 --- a/content/code/in-support-of-git.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: In Support of Git -description: In Support of Git -date: "2014-06-23" ---- - -### In Support of Git - -We use GitHub to store and share our code. GitHub, in turn, is powered by Linus Torvalds' Git - a distributed version control system. If you don't know how to use Git, and you're interested in learning it, there is an excellent tutorial from GitHub: https://try.github.io. We also organize a git workshop every semester, together with other workshops on web development: //school.nushackers.org. diff --git a/content/community/_index.md b/content/community/_index.md new file mode 100755 index 00000000..715f9720 --- /dev/null +++ b/content/community/_index.md @@ -0,0 +1,22 @@ +--- +title: Community +description: Community +date: "2014-06-23" +--- + +We host a community of like-minded, interested hackers in NUS. + +To follow what we do, follow us on: + +- [Telegram](https://t.me/nushackers) +- [Facebook](https://www.facebook.com/NUSHackers) +- [Twitter](https://twitter.com/nushackers) +- [Meetup.com](https://groups.google.com/forum/?fromgroups#!forum/nushackers) +- [Our mailing list](https://groups.google.com/forum/?fromgroups#!forum/nushackers) + +You can also join us on: + +- [Discord](https://discord.gg/Au3VJxz) +- [Our Facebook group](https://www.facebook.com/groups/nushackers/) + +If you'd like to share an ad or opportunity, please [contact us]({{< ref "/contact" >}}). We have to make sure that the content is relevant to those who are subscribed to our lists. diff --git a/content/contact/_index.md b/content/contact/_index.md index ed87b0fb..82229f8a 100644 --- a/content/contact/_index.md +++ b/content/contact/_index.md @@ -4,12 +4,6 @@ description: Contacting us date: "2014-06-11" --- -If you want to get in touch with us, feel free to send us a message via our email `coreteam [at] nushackers [fullstop] org` +If you want to get in touch with us, feel free to send us an email at `coreteam [at] nushackers [fullstop] org`. -This is ideal for things like: you’d like to request a workshop, you’d like to do a guest post on our site, you have -further questions about our membership and organization. For general discussion, -or to interact with community members, we recommend you go to our [Discussion page](/discussion/). - -__Note: If you’re about to contact us to ‘hack’ into a system, don’t bother:__ we’ll -report you to the relevant authorities, and may choose to shame you on our blog. -We’re a hacker organization, not a cracker organization. Know the [difference](/hackerdefined/). +To interact with our community or keep up-to-date with what we are doing, [join our community]({{< ref "/community" >}}). diff --git a/content/discussion/_index.md b/content/discussion/_index.md deleted file mode 100755 index b893e825..00000000 --- a/content/discussion/_index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Discussion -description: Discussion -date: "2014-06-23" ---- - -We host a community of like-minded, interested hackers in NUS. Join our mailing list - most of our organization-wide announcements and discussions are made through it. We also have a presence on Facebook with our Facebook page and our Facebook group. You can follow also follow @nushackers on Twitter - -Note - we do have a recruiter/ad policy: - -> We don't mind ads and shoutouts from trusted list-members. But if you're new to the mailing list, **you will not be allowed to post ads.** We frown on people who sign-up to spam the list. To that end, all new members are placed on moderation. -> -> **If you're dropping by, and you want to post an ad, email the coreteam here.** We vet ads for quality/relevance to the list, and approve them accordingly. We make no promises about objectiveness, by the way—our prime concern is with quality of content, not accessibility to advertisers. We approve ads that we think are interesting. What interesting means is up to us. -> -> We do this because we're most interested in maintaining the quality of list-content. We spend a lot of our time curating this list, and we think that our core responsibility is to our members. diff --git a/content/events/_index.md b/content/events/_index.md deleted file mode 100755 index 29e8456f..00000000 --- a/content/events/_index.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: Events -description: NUSHackers events -date: "2014-06-23" ---- - -We run workshops, hackathons, and other hacker-culture related things. Our main event is a weekly meetup called Friday Hacks. Check our front page for more news (and other cool things). - -We also record some of our events, including Hackerschool and Friday Hacks. Recordings can be found [here](/recordings/). diff --git a/content/fh/_index.md b/content/fh/_index.md deleted file mode 100644 index 1f060339..00000000 --- a/content/fh/_index.md +++ /dev/null @@ -1,3 +0,0 @@ ---- -title: Friday Hacks ---- diff --git a/content/fridayhacks/_index.md b/content/fridayhacks/_index.md index 41899f91..6043bf0e 100644 --- a/content/fridayhacks/_index.md +++ b/content/fridayhacks/_index.md @@ -2,42 +2,42 @@ title: About Friday Hacks description: About Friday Hacks date: "2014-06-23" -notes: | - --- -Our weekly Friday meetups are called Friday Hacks. They include one or two technical talks, followed by a hacking session. The idea is simple: get people to come share their hacks, research, or technical knowledge with the technical community in NUS. -We have up to 2 talks at each session, talks are usually 30-45 minutes long. Dinner is always served (usually pizza). Food is served at 6:30pm, talks start at 7pm. +Our weekly Friday meetups are called Friday Hacks. They include one or two technical talks, sometimes followed by a hacking session. Through Friday Hacks, we hope to get people to come share their hacks, research, or technical knowledge with the technical community in NUS. + +We have up to 2 talks at each session, with each talks being about 30–45 minutes long. Dinner is always served (usually pizza). Food is served at 6:30pm and talks start at 7pm. -We also record the talks if the speaker consents. Find our recordings [here](/recordings). +We also record the talks if the speaker consents. Find our recordings [here]({{< ref "/recordings" >}}). -![Friday Hacks #71](//i.imgur.com/sEBVHCx.jpg) +![Friday Hacks #71](/img/fh.jpg) ## Speaker FAQ **When and where do Friday Hacks happen?** -Friday Hacks happen every Friday at 6:30pm, at Seminar Room 3, level 2 of Town Plaza, University Town, National University of Singapore unless otherwise stated. - +Friday Hacks happen every Friday at 6:30pm, at [Seminar Room 5, Level 2, Town Plaza, University Town, National University of Singapore](https://goo.gl/maps/6GCDZN32Q4gPa49b8) unless otherwise stated. + +**How do I get there from outside campus, and where can I park?** +The closest MRT station is at Clementi. Take either 96 from the bus interchange towards Singapore Polytechnic, and get off 3 bus stops later. (You may also take bus 183 from the MRT station, but the bus frequency for 183 is low). -[View Larger Map](https://goo.gl/maps/PYzUn) +You can also take the NUS internal bus D2 from Kent Ridge MRT, and alight at the University Town stop. -**How do I get there from outside campus/Where can I park?** -The closest MRT station is at Clementi. Take either the 96 from the bus interchange (which is at Clementi mall) towards Singapore Polytechnic, and get off 3 bus stops later. (You may also take bus 183 from the MRT station, but bus frequency for 183 is low). As for parking: you may park at a small parking lot at UTown opposite New Town Secondary School, along Dover road. +If you are driving, you may park at a small parking lot at UTown opposite New Town Secondary School, along Dover Road. Let us know beforehand so we can guide you when you arrive. **Who is welcome to speak?** Anyone! We do give some preference to NUS students, staff and professors, but we regularly invite speakers from all parts of the industry. **Who has given a Friday Hacks talk?** -We've had speakers from Google, Quora, Palantir, Thought Works, Pivotal Labs, Nokia, RIM, and Viki, amongst many others. +We've had speakers from Google, Quora, Palantir, Thought Works, Pivotal Labs, Nokia, Carousell, and Viki, amongst many others. **What time should speakers arrive?** -People start streaming in at 6pm, but Friday Hacks are informal, so anytime between 6pm-7pm is okay. The actual event starts at 7pm. +People start streaming in at 6pm, but Friday Hacks are informal, so anytime between 6pm–7pm is okay. The actual event starts at 7pm. **What topic should I talk about?** Technical topics, of course! Talking about a weekend hack project, your research, or some ideas you recently had about tech are all great topics for a Friday Hacks talk. _The more code you show, the better!_ Note though that you should **not** give a recruiting pitch. We find that people are more receptive to pitches given at the tail end of technical talks. **What's the audience like?** -Anyone is welcomed to attend Friday Hacks, though the audience would be primarily NUS School of Computing students. From experience, we expect 30-50 students on average at every weekly meeting. +Anyone is welcome to attend Friday Hacks, though our audience is primarily NUS School of Computing students. From experience, we expect 30–50 students on average at every weekly meeting. **What tools are provided?** -We have a Windows desktop, a projector with VGA and adapters from Mini-DisplayPort, a large whiteboard, and wireless network access. Let us know in your email if you need anything else and we'll see what we can do. \ No newline at end of file +We have a Windows desktop, a projector with VGA, a large whiteboard, and wireless network access. Let us know in your email if you need anything else and we'll see what we can do. diff --git a/content/fridayhacks/schedule.md b/content/fridayhacks/schedule.md new file mode 100644 index 00000000..c2309373 --- /dev/null +++ b/content/fridayhacks/schedule.md @@ -0,0 +1,4 @@ +--- +title: Friday Hacks +layout: fridayhacks_schedule +--- diff --git a/content/fridayhacks/speak-at-friday-hacks.md b/content/fridayhacks/speak-at-friday-hacks.md index 3e8f2c97..c01ab283 100644 --- a/content/fridayhacks/speak-at-friday-hacks.md +++ b/content/fridayhacks/speak-at-friday-hacks.md @@ -6,10 +6,10 @@ date: "2014-06-11" ### If you're working on something cool, you should come give a talk! -The fastest way to do so is to [send us an email](/contact). To help us out, remember to include the following information: +The fastest way to do so is to [send us an email]({{< ref "/contact" >}}). To help us out, remember to include the following information: -* Your full name & professional affiliation or title (if you have one) -* Title of your talk. -* Date you want to speak. +* Your full name & professional affiliation or title (if you have one) +* Title of your talk. +* Date you want to speak. -Remember to check [this semester's schedule](/fh) and pick an available slot. +Remember to check [this semester's schedule]({{< ref "/fridayhacks/schedule" >}}) and pick an available slot. diff --git a/content/hackerdefined/_index.md b/content/hackerdefined/_index.md index 180a5350..8025d7b0 100644 --- a/content/hackerdefined/_index.md +++ b/content/hackerdefined/_index.md @@ -4,11 +4,11 @@ description: What is a Hacker? permalink: /hackerdefined/ --- -We have found that the best definition of hacker is this bit from Eric S. Raymond's essay How To Become A Hacker: +This excerpt from Eric S. Raymond's essay [How To Become A Hacker](http://www.catb.org/~esr/faqs/hacker-howto.html#what_is) is a very good description of what a hacker is. -There is a community, a shared culture, of expert programmers and networking wizards that traces its history back through decades to the first time-sharing minicomputers and the earliest ARPAnet experiments. The members of this culture originated the term ‘hacker’. Hackers built the Internet. Hackers made the Unix operating system what it is today. Hackers run Usenet. Hackers make the World Wide Web work. If you are part of this culture, if you have contributed to it and other people in it know who you are and call you a hacker, you're a hacker. +There is a community, a shared culture, of expert programmers and networking wizards that traces its history back through decades to the first time-sharing minicomputers and the earliest ARPAnet experiments. The members of this culture originated the term 'hacker'. Hackers built the Internet. Hackers made the Unix operating system what it is today. Hackers make the World Wide Web work. If you are part of this culture, if you have contributed to it and other people in it know who you are and call you a hacker, you're a hacker. -The hacker mind-set is not confined to this software-hacker culture. There are people who apply the hacker attitude to other things, like electronics or music — actually, you can find it at the highest levels of any science or art. Software hackers recognize these kindred spirits elsewhere and may call them ‘hackers’ too — and some claim that the hacker nature is really independent of the particular medium the hacker works in. But in the rest of this document we will focus on the skills and attitudes of software hackers, and the traditions of the shared culture that originated the term ‘hacker’. +The hacker mind-set is not confined to this software-hacker culture. There are people who apply the hacker attitude to other things, like electronics or music—actually, you can find it at the highest levels of any science or art. Software hackers recognize these kindred spirits elsewhere and may call them 'hackers' too—and some claim that the hacker nature is really independent of the particular medium the hacker works in. But in the rest of this document we will focus on the skills and attitudes of software hackers, and the traditions of the shared culture that originated the term 'hacker'. There is another group of people who loudly call themselves hackers, but aren't. These are people (mainly adolescent males) who get a kick out of breaking into computers and phreaking the phone system. Real hackers call these people ‘crackers’ and want nothing to do with them. Real hackers mostly think crackers are lazy, irresponsible, and not very bright, and object that being able to break security doesn't make you a hacker any more than being able to hotwire cars makes you an automotive engineer. Unfortunately, many journalists and writers have been fooled into using the word ‘hacker’ to describe crackers; this irritates real hackers no end. diff --git a/content/hackerdefined/related.md b/content/hackerdefined/related.md index 4ab6c194..fa871729 100644 --- a/content/hackerdefined/related.md +++ b/content/hackerdefined/related.md @@ -6,7 +6,7 @@ date: "2014-06-23" ### Related -- [About Us](/about) -- [Why We Do What We Do](/why) -- [The Hacker Attitude](/the-hacker-attitude/) -- [On The Name Change](/name-change/) +- [About us]({{< ref "/about" >}}) +- [Why we do what we do]({{< ref "/why" >}}) +- [The Hacker Attitude]({{< ref "/the-hacker-attitude" >}}) +- [On the name change]({{< ref "/name-change" >}}) diff --git a/content/join-coreteam/_index.md b/content/join-coreteam/_index.md index c16e1361..ae909e51 100644 --- a/content/join-coreteam/_index.md +++ b/content/join-coreteam/_index.md @@ -4,27 +4,19 @@ description: Join Coreteam date: "2014-06-23" --- -NUS Hackers is run by a group of student volunteers - the coreteam. Our long term goal is to build a healthy community of passionate hackers in NUS. We think that this benefits everyone: start-ups, tech companies, and professors have a central pool from which to find good programmers, and students have an easy way to meet/learn from like-minded peers. +NUS Hackers is run by a group of student volunteers—the coreteam. Our long term goal is to build a healthy community of passionate hackers in NUS. We think that this benefits everyone: start-ups, tech companies and professors have a central pool from which to find good programmers, and students have an easy way to meet and learn from like-minded peers. -## What we do - -Here's a brief overview of everything we run: - -- [Friday Hacks](//nushackers.org) -- [hackerschool](//school.nushackers.org) -- [Hack&Roll](//hacknroll.nushackers.org) -- [Code@NUS](//code.nushackers.org) -- [Download@NUS](https://download.nus.edu.sg) -- NUS Hackerspace +Our [about page]({{< ref "/about#what-we-do" >}}) has more on what we do. ## How we're structured + Coreteam is organised as a flat structure under a single president (instead of in a traditional committee/sub-committee hierarchy). Our roles and responsibilities are assigned flexibly, and as needed. ## What we look for * An understanding of our vision: a lot of what we do is thankless, and it may be easy to burn out unless you're really into the cause. -* A reasonable level of commitment: some things we do require quite a bit of time. That being said, we don't need you to be available all day everyday - we're pretty flexible with this. +* A reasonable level of commitment: some things we do require quite a bit of time. That being said, we don't need you to be available all day everyday—we're pretty flexible with this. ## Want to join us? -Just email or approach any one of us - we'll set up an interview to find out more about what you're interested in doing. This is usually an informal chat over lunch, so don't worry too much about it; it does help to take part in our events and check out the rest of this site beforehand, though. This is also an opportunity for you to get to know us better, so feel free to ask any questions, too. +Just [email]({{< ref "/contact" >}}) or approach any one of us—we'll set up an interview to find out more about what you're interested in doing. This is usually an informal chat over lunch, so don't worry too much about it; it does help to take part in our events and check out the rest of this site beforehand, though. This is also an opportunity for you to get to know us better, so feel free to ask any questions, too. diff --git a/content/name-change/_index.md b/content/name-change/_index.md index 872ac7de..a43c6299 100644 --- a/content/name-change/_index.md +++ b/content/name-change/_index.md @@ -1,46 +1,35 @@ --- -title: On The Name Change +title: On the name change permalink: /name-change/ date: "2014-06-23" -notes: | -

Related

- - --- -In August 2011, the Office of Student Affairs requested a writeup for the name change from linuxNUS to NUS Hackers. For the sake of transparency, this is that writeup: -The name change from linuxNUS to NUS Hackers took six months of debate to decide. We took into account the fact that the word ‘hacker’ has negative connotations in mainstream media, but we still felt that the name change made sense, given the following reasons: +_In August 2011, the Office of Student Affairs requested a writeup for the name change from linuxNUS to NUS Hackers. For the sake of transparency, this is that writeup._ -1) linuxNUS no longer reflects what we do. The group was originally started as a Linux user group/Open Source Software advocate. However, as time passed, we began to be involved in events that had little to do with both. Instead we began doing events that promoted and supported the more general topic of ‘hacking’: that is, playful building (and programming). In the first semester last year, we ran a series of IDA-sponsored workshops called the ‘Hack Workshop Series’, and invited external speakers to talk about the various aspects of building software for fun (‘hacking’). +The name change from linuxNUS to NUS Hackers took six months of debate to decide. We took into account the fact that the word 'hacker' has negative connotations in mainstream media, but we still felt that the name change made sense, given the following reasons: -2) Hacking best describes what we do.  The terms ‘hacking’ and ‘hacker’ that we refer to does not mean ‘unauthorized breaking-in of a computer system’. (In fact, this definition only appeared in the 1980s, and even then only in the press). We refer instead to the original usage of the word – i.e., the computer programmer subculture that originated in the 1960s at MIT, that currently powers most open source movements. The proper term for the malicious attackers one reads about in the newspaper is ‘cracker’. +**1) linuxNUS no longer reflects what we do.** The group was originally started as a Linux user group/Open Source Software advocate. However, as time passed, we began to be involved in events that had little to do with both. Instead we began doing events that promoted and supported the more general topic of 'hacking': that is, playful building (and programming). In the first semester last year, we ran a series of IDA-sponsored workshops called the 'Hack Workshop Series', and invited external speakers to talk about the various aspects of building software for fun ('hacking'). -The simplest definition of hacking is: ‘playful cleverness’ [1]. For instance, Mark Zuckerberg has described himself as a hacker, and more importantly has described Facebook as a ‘hacker-friendly’ company. By this he means people who program for fun, in the same way that he built Facebook for fun, as a University student. As there is no other word in the English language to describe this philosophy of  ‘playful cleverness in terms of building things’, we decided that the name NUS Hackers was our best option, as opposed to other alternatives. +**2) Hacking best describes what we do.** The terms 'hacking' and 'hacker' that we refer to does not mean 'unauthorized breaking-in of a computer system'. (In fact, this definition only appeared in the 1980s, and even then only in the press). We refer instead to the original usage of the word—i.e., the computer programmer subculture that originated in the 1960s at MIT, that currently powers most open source movements. The proper term for the malicious attackers one reads about in the newspaper is 'cracker'. -It is worth noting here that amongst programmers – hacking and hackers has had a long and illustrious history. Linux, the web browser Firefox, and nearly all popular programming languages in use today were created by people who identified themselves under the ‘hacker’ subculture. If you hear a programmer say ‘I hacked on my project last night’, he does not mean he broke into his own software. It instead means that he ‘worked on it for fun’. +The simplest definition of hacking is: 'playful cleverness'[^1]. For instance, Mark Zuckerberg has described himself as a hacker, and more importantly has described Facebook as a 'hacker-friendly' company. By this he means people who program for fun, in the same way that he built Facebook for fun, as a University student. As there is no other word in the English language to describe this philosophy of  'playful cleverness in terms of building things', we decided that the name NUS Hackers was our best option, as opposed to other alternatives. -3) ‘Hackers’, as used in NUS Hackers, has done more good than harm for the organization (and therefore the school). We are affiliated with the Singaporean Hackerspace, and occasionally call upon them to help out at NUS-specific events (such as teaching workshops to School of Computing students). Two of the four founders of Hackerspace.sg were NUS alumni and founders of linuxNUS. We included them in our decision making process for this name change, and they approved of it. +[^1]: From Richard Stallman, creator of the GNU operating system, and founder of the Electronic Frontier Foundation. https://stallman.org/articles/on-hacking.html -The monicker has helped us in several other ways: - -One worry that we had was that public perception would not match industry perception of the word ‘Hacker’. However, we felt that this was balanced out by the increasing centrality of the Singaporean Hackerspace. To date, companies as diverse as Nokia, Amazon, Google, Yahoo and Microsoft have held events or organized joint-events at the Hackerspace. These companies, and the acceptance of the word ‘hacker’ amongst the local professional developer crowd, lead us to conclude that our naming would send the right signals to the right people in the industry. Indeed, as the above examples have shown, this has turned out to be largely true. The net result is more opportunities – learning and commercial – for both students and industry alike. +It is worth noting here that amongst programmers—hacking and hackers has had a long and illustrious history. Linux, the web browser Firefox, and nearly all popular programming languages in use today were created by people who identified themselves under the 'hacker' subculture. If you hear a programmer say 'I hacked on my project last night', he does not mean he broke into his own software. It instead means that he 'worked on it for fun'. -I hope these reasons are clear enough to explain why we decided, after 6 months of debate, to change our name to NUS Hackers. We hope to spread the same programmer subculture that made MIT the hub of computing innovation in the US, and we hope to be the best support system possible for all hackers building things for the good of NUS. -

+**3) 'Hackers', as used in NUS Hackers, has done more good than harm for the organization (and therefore the school)**. We are affiliated with the Singaporean Hackerspace, and occasionally call upon them to help out at NUS-specific events (such as teaching workshops to School of Computing students). Two of the four founders of Hackerspace.sg were NUS alumni and founders of linuxNUS. We included them in our decision making process for this name change, and they approved of it. -
+The monicker has helped us in several other ways: + +- Silicon Valley startups that have just moved to Singapore frequently contact us for access to programming talent, from searches for 'Hackers in Singapore'. They are used to the term 'hacker' to mean 'good programmer'.  Examples of these include Federico Folcia, co-founder of Roomorama, and Vinnie Laura, creator of SuperHappyDevHouse. We have always been happy to point them to our student-members, or direct them to the programmer community outside the school. +- Members of the NUS Hackers coreteam were invited to participate in and assist with the promotion of Startup Roots[^2]—an internship program for startups that originated from Silicon Valley. As a result of this event, we have a working relationship with James Chan of Neoteny Labs (an incubator based in Singapore, headed by Joi Ito, current head of the MIT media lab). The Startup Roots program explicitly looked for 'student hackers'. +- We have had funding from IDA for the Hack Workshop Series two semesters ago. Last semester (after the name change), we were given a hackspace at the Garag3 incubator. Our working relationship with e27 is orthogonal to our working relationship with Hackerspace: we will be assisting at the upcoming Developer Camp, as well as passing on code competition opportunities organized by them to our student-members. +- NUS Hackers was called upon to facilitate at LadyPy, a not-for-profit programming course for women by the Singapore Python User group. Again, looking for us was a logical decision—the organizers assumed that the most likely place to find Python-proficient programmers was at a hacker organization—something which might not have happened if our name was 'linuxNUS'. As a result of this workshop, we are now planning to work with the Singapore Python User group to bring the same set of workshops to NUS. -
+[^2]: This link used to point to https://sg.startuproots.org/, but it seems to no longer exist. (2019-08-11) -[1] From Richard Stallman, creator of the GNU operating system, and founder of the Electronic Frontier Foundation. //stallman.org/articles/on-hacking.html   ↩ +**One worry that we had was that public perception would not match industry perception of the word 'Hacker'.** However, we felt that this was balanced out by the increasing centrality of the [Singaporean Hackerspace](https://hackerspace.sg/about/). To date, companies as diverse as Nokia, Amazon, Google, Yahoo and Microsoft have held events or organized joint-events at the Hackerspace. These companies, and the acceptance of the word 'hacker' amongst the local professional developer crowd, lead us to conclude that our naming would send the right signals to the right people in the industry. Indeed, as the above examples have shown, this has turned out to be largely true. The net result is more opportunities—learning and commercial—for both students and industry alike. -
-
+I hope these reasons are clear enough to explain why we decided, after 6 months of debate, to change our name to NUS Hackers. We hope to spread the same programmer subculture that made MIT the hub of computing innovation in the US, and we hope to be the best support system possible for all hackers building things for the good of NUS. diff --git a/content/name-change/related.md b/content/name-change/related.md index 4ab6c194..fa871729 100644 --- a/content/name-change/related.md +++ b/content/name-change/related.md @@ -6,7 +6,7 @@ date: "2014-06-23" ### Related -- [About Us](/about) -- [Why We Do What We Do](/why) -- [The Hacker Attitude](/the-hacker-attitude/) -- [On The Name Change](/name-change/) +- [About us]({{< ref "/about" >}}) +- [Why we do what we do]({{< ref "/why" >}}) +- [The Hacker Attitude]({{< ref "/the-hacker-attitude" >}}) +- [On the name change]({{< ref "/name-change" >}}) diff --git a/content/the-hacker-attitude/_index.md b/content/the-hacker-attitude/_index.md index 3e8246ad..6daaf06c 100644 --- a/content/the-hacker-attitude/_index.md +++ b/content/the-hacker-attitude/_index.md @@ -3,46 +3,46 @@ title: The Hacker Attitude description: The Hacker Attitude date: "2014-06-23" --- -Five things. Again taken from Eric S. Raymond's How To Become a Hacker: +An excerpt from Eric S. Raymond's [How To Become a Hacker](http://www.catb.org/~esr/faqs/hacker-howto.html#believe1). -1. The world is full of fascinating problems waiting to be solved. +## 1. The world is full of fascinating problems waiting to be solved. Being a hacker is lots of fun, but it's a kind of fun that takes lots of effort. The effort takes motivation. Successful athletes get their motivation from a kind of physical delight in making their bodies perform, in pushing themselves past their own physical limits. Similarly, to be a hacker you have to get a basic thrill from solving problems, sharpening your skills, and exercising your intelligence. If you aren't the kind of person that feels this way naturally, you'll need to become one in order to make it as a hacker. Otherwise you'll find your hacking energy is sapped by distractions like sex, money, and social approval. -(You also have to develop a kind of faith in your own learning capacity — a belief that even though you may not know all of what you need to solve a problem, if you tackle just a piece of it and learn from that, you'll learn enough to solve the next piece — and so on, until you're done. +(You also have to develop a kind of faith in your own learning capacity—a belief that even though you may not know all of what you need to solve a problem, if you tackle just a piece of it and learn from that, you'll learn enough to solve the next piece—and so on, until you're done.) -2. No problem should ever have to be solved twice. +## 2. No problem should ever have to be solved twice. Creative brains are a valuable, limited resource. They shouldn't be wasted on re-inventing the wheel when there are so many fascinating new problems waiting out there. -To behave like a hacker, you have to believe that the thinking time of other hackers is precious — so much so that it's almost a moral duty for you to share information, solve problems and then give the solutions away just so other hackers can solve new problems instead of having to perpetually re-address old ones. +To behave like a hacker, you have to believe that the thinking time of other hackers is precious—so much so that it's almost a moral duty for you to share information, solve problems and then give the solutions away just so other hackers can solve new problems instead of having to perpetually re-address old ones. Note, however, that "No problem should ever have to be solved twice." does not imply that you have to consider all existing solutions sacred, or that there is only one right solution to any given problem. Often, we learn a lot about the problem that we didn't know before by studying the first cut at a solution. It's OK, and often necessary, to decide that we can do better. What's not OK is artificial technical, legal, or institutional barriers (like closed-source code) that prevent a good solution from being re-used and force people to re-invent wheels. (You don't have to believe that you're obligated to give all your creative product away, though the hackers that do are the ones that get most respect from other hackers. It's consistent with hacker values to sell enough of it to keep you in food and rent and computers. It's fine to use your hacking skills to support a family or even get rich, as long as you don't forget your loyalty to your art and your fellow hackers while doing it.) -3. Boredom and drudgery are evil. +## 3. Boredom and drudgery are evil. -Hackers (and creative people in general) should never be bored or have to drudge at stupid repetitive work, because when this happens it means they aren't doing what only they can do — solve new problems. This wastefulness hurts everybody. Therefore boredom and drudgery are not just unpleasant but actually evil. +Hackers (and creative people in general) should never be bored or have to drudge at stupid repetitive work, because when this happens it means they aren't doing what only they can do—solve new problems. This wastefulness hurts everybody. Therefore boredom and drudgery are not just unpleasant but actually evil. To behave like a hacker, you have to believe this enough to want to automate away the boring bits as much as possible, not just for yourself but for everybody else (especially other hackers). -(There is one apparent exception to this. Hackers will sometimes do things that may seem repetitive or boring to an observer as a mind-clearing exercise, or in order to acquire a skill or have some particular kind of experience you can't have otherwise. But this is by choice — nobody who can think should ever be forced into a situation that bores them.) +(There is one apparent exception to this. Hackers will sometimes do things that may seem repetitive or boring to an observer as a mind-clearing exercise, or in order to acquire a skill or have some particular kind of experience you can't have otherwise. But this is by choice—nobody who can think should ever be forced into a situation that bores them.) -4. Freedom is good. +## 4. Freedom is good. -Hackers are naturally anti-authoritarian. Anyone who can give you orders can stop you from solving whatever problem you're being fascinated by — and, given the way authoritarian minds work, will generally find some appallingly stupid reason to do so. So the authoritarian attitude has to be fought wherever you find it, lest it smother you and other hackers. +Hackers are naturally anti-authoritarian. Anyone who can give you orders can stop you from solving whatever problem you're being fascinated by—and, given the way authoritarian minds work, will generally find some appallingly stupid reason to do so. So the authoritarian attitude has to be fought wherever you find it, lest it smother you and other hackers. (This isn't the same as fighting all authority. Children need to be guided and criminals restrained. A hacker may agree to accept some kinds of authority in order to get something he wants more than the time he spends following orders. But that's a limited, conscious bargain; the kind of personal surrender authoritarians want is not on offer.) -Authoritarians thrive on censorship and secrecy. And they distrust voluntary cooperation and information-sharing — they only like ‘cooperation’ that they control. So to behave like a hacker, you have to develop an instinctive hostility to censorship, secrecy, and the use of force or deception to compel responsible adults. And you have to be willing to act on that belief. +Authoritarians thrive on censorship and secrecy. And they distrust voluntary cooperation and information-sharing—they only like ‘cooperation’ that they control. So to behave like a hacker, you have to develop an instinctive hostility to censorship, secrecy, and the use of force or deception to compel responsible adults. And you have to be willing to act on that belief. -5. Attitude is no substitute for competence. +## 5. Attitude is no substitute for competence. To be a hacker, you have to develop some of these attitudes. But copping an attitude alone won't make you a hacker, any more than it will make you a champion athlete or a rock star. Becoming a hacker will take intelligence, practice, dedication, and hard work. -Therefore, you have to learn to distrust attitude and respect competence of every kind. Hackers won't let posers waste their time, but they worship competence — especially competence at hacking, but competence at anything is valued. Competence at demanding skills that few can master is especially good, and competence at demanding skills that involve mental acuteness, craft, and concentration is best. +Therefore, you have to learn to distrust attitude and respect competence of every kind. Hackers won't let posers waste their time, but they worship competence—especially competence at hacking, but competence at anything is valued. Competence at demanding skills that few can master is especially good, and competence at demanding skills that involve mental acuteness, craft, and concentration is best. -If you revere competence, you'll enjoy developing it in yourself — the hard work and dedication will become a kind of intense play rather than drudgery. That attitude is vital to becoming a hacker. +If you revere competence, you'll enjoy developing it in yourself—the hard work and dedication will become a kind of intense play rather than drudgery. That attitude is vital to becoming a hacker. diff --git a/content/the-hacker-attitude/related.md b/content/the-hacker-attitude/related.md index 4ab6c194..fa871729 100644 --- a/content/the-hacker-attitude/related.md +++ b/content/the-hacker-attitude/related.md @@ -6,7 +6,7 @@ date: "2014-06-23" ### Related -- [About Us](/about) -- [Why We Do What We Do](/why) -- [The Hacker Attitude](/the-hacker-attitude/) -- [On The Name Change](/name-change/) +- [About us]({{< ref "/about" >}}) +- [Why we do what we do]({{< ref "/why" >}}) +- [The Hacker Attitude]({{< ref "/the-hacker-attitude" >}}) +- [On the name change]({{< ref "/name-change" >}}) diff --git a/content/why/_index.md b/content/why/_index.md index 620229da..321f0a88 100644 --- a/content/why/_index.md +++ b/content/why/_index.md @@ -1,43 +1,51 @@ --- -title: Why We Do What We Do -description: Why We Do What We Do +title: Why we do what we do +description: Why we do what we do date: "2014-06-23" --- -We spend a lot of our time working on NUS Hackers. Sometimes so much that we have to fight to balance it with our schoolwork. And we do this for no co-curricular points, whatsoever. +We spend a lot of our time working on NUS Hackers—sometimes so much that we have to fight to balance it with our schoolwork. And we do this for no co-curricular points whatsoever. -Here's an interesting question to ask: why do we do what we do? +_Why_ do we do what we do? -There are two answers to the this question. The first - the simple one - is that we do it because it's fun. Hackers take pleasure in building things. We're no exception to this: we enjoy creating things for people to use (or really just creating things that we think are cool, and then showing them off to our peers). It's the same sort of pleasure you get when you make a birthday present for a friend, and you see the delight spread over her face when she takes it out of the box. +There are two answers to the this question. The first—the simple one—is that we do it because it's fun. Hackers take pleasure in building things. We're no exception to this: we enjoy creating things for people to use (or really just creating things that we think are cool, and then showing them off to our peers). It's the same sort of pleasure you get when you make a birthday present for a friend, and you see the delight spread over her face when she takes it out of the box. + +The more complicated answer is that we think a hacker culture is _the_ most important element one can have in a tech community. That's an audacious statement to make, on the face of it. It implies that without a hacker culture, you can't foster superb technological innovation; that institutions won't produce the best programmers they might potentially be able to produce; that you can't really do great tech startups. But why do we think this is so? + +## The importance of hacking -The more complicated answer is that we think a hacker culture is the most important element one can have in a tech community. That's an audacious statement to make, on the face of it. It implies that without a hacker culture, you can't foster superb technological innovation; that institutions won't produce the best programmers they might potentially be able to produce; that you can't really do great tech startups. But why do we think this is so? -

The Importance of Hacking

Every great innovation that has happened in the history of computing has happened in the context of a hacker culture. Either it began as a small project, started by the hacker with a habit of starting small projects, or it came from a condensation of hackers in the same space, working with each other on similar ideas. -You don't have to look very far back for examples of this effect. Ken Thompson invented Unix on the side because he was sick of working on Multics. (His friend, Dennis Ritchie, helped him with his Unix project and so created the C programming language).  Later on, in the same tradition, Richard Stallman wrote the first components of the GNU operating system in response to the diminishing hacker culture in MIT, and Linus Torvalds wrote the Linux kernel at 21 because he thought it was cool to have news on display in the terminal in his bedroom. Steve Jobs and Steve Wozniak started out selling hacked Blue Boxes. Bill Gates and Paul Allen thought they would invent and sell new programming languages.  Mark Zuckerberg hacked together small, cool projects in his spare time before launching his social network. (All five came from hackerish communities - the first four from computer clubs). The list goes on and on. +You don't have to look very far back for examples of this effect. Ken Thompson invented Unix _on the side_ because he was sick of working on Multics. (His friend, Dennis Ritchie, helped him with his Unix project and so created the C programming language). Later on, in the same tradition, Richard Stallman wrote the first components of the GNU operating system in response to the diminishing hacker culture in MIT, and Linus Torvalds wrote the Linux kernel at 21 because _he thought it was cool_ to have news on display in the terminal in his bedroom. Steve Jobs and Steve Wozniak started out selling hacked Blue Boxes. Bill Gates and Paul Allen thought they would invent and sell new programming languages. Mark Zuckerberg hacked together small, cool projects in his spare time before launching his social network. (All five came from hackerish communities—the first four from computer clubs). The list goes on and on. -{{< imglink src="/img/2011/01/nerdpol-ken-den.jpg" alt="Ken Thompson and Dennis Ritchie at the PDP-11 in 1972" >}} Ken Thompson and Dennis Ritchie at the PDP-11 in 1972[/caption] +{{< imglink src="/img/2011/01/nerdpol-ken-den.jpg" alt="Ken Thompson and Dennis Ritchie at the PDP-11 in 1972" >}} _Ken Thompson and Dennis Ritchie at the PDP-11 in 1972_ Something important, it seems, happens when you put a bunch of hackers together in a communal environment. Part of it is that hacking in itself is such an important part of being a good programmer. In the same way that people who love to draw tend to draw better than those who don't, hackers love to program, and so they tend to be better at it than those who merely code to pay the bills. -It would seem that if more people were to get hooked on hacking, we'd get better programmers. And this is true - it is one of the reasons we're so interested in spreading the hacker culture in NUS: -
Spreading the hacker culture = more hackers = better programmers in Singapore.
+It would seem that if more people were to get hooked on hacking, we'd get better programmers. And this is true—it is one of the reasons we're so interested in spreading the hacker culture in NUS: + +> Spreading the hacker culture = more hackers = better programmers in Singapore. + But there's an added element at play here: because hackers start so many projects for the fun of it, over time they'd begin to learn from the failures. Hackers tend to have a better idea of what works (and what doesn't) when building software for people to use. It's no coincidence that many of the best startups are done by people who have a history of building things for fun. Hacking, as it is, is a hobby that very quickly shapes the way you think about products and markets, a nice side-effect of wanting as many people as possible to use the cool things you make in your spare time. -

Hacker Culture as Catalyst

+ +## Hacker culture as catalyst + So if hacking were so important, what's the best way to see it spread? We think the answer to this is rather straightforward: create a community of hackers. Both MIT and Stanford have existing hacker communities, and it's rather easy to hack with the support of a community (it may also be an explanation for the high level of technological innovation there, but that's just idle speculation on our end). We usually refer to this community of hackers as 'a hacker culture'. Almost everything we do as an organization is to create, advance or spread this idea. And we think that there are a couple of added benefits of hacking in a community, as compared to hacking without one. -The first is economical: if hackers tend to be better programmers than most, then Singaporean companies (or more importantly, Singaporean startups, where quality of talent counts the most) would have a better available pool of talent. As much as traditional hacker culture is opposed to close-minded money-making and crass commercialism, the fact remains that great companies are limited by the quality of the engineering talent they attract. And it's also no coincidence that both Google and Facebook are built from the ground-up to be as hacker friendly as possible. +The first is economical: if hackers tend to be better programmers than most, then Singaporean companies (or more importantly, _Singaporean startups_, where quality of talent counts the most) would have a better available pool of talent. As much as traditional hacker culture is opposed to close-minded money-making and crass commercialism, the fact remains that great companies are limited by the quality of the engineering talent they attract. And it's also no coincidence that both Google and Facebook are built from the ground-up to be as hacker friendly as possible. We're interested in this because most startups, out of necessity, tend to be hacker-friendly. And more successful hacker-friendly companies are a net-win for all of us. The second reason: if we think of programming as the act of translating your ideas into code, then the best programmers are the ones who are not only good at translation, but who have the best ideas. Putting hackers together is one way to get good ideas. Putting hackers together who are all working on different things usually works out to be the best way to get good ideas. -

The Why

+ +## The why + We are interested in spreading hacker culture for most of the benefits we've outlined above. We think that a hacker culture creates better engineering talent, because people who code for fun tend to be better at it. We think that if you cluster hackers together, you get these beneficial effects faster (the same way some teachers encourage studying together, so as to maximize the peer pressure to do well in school). We think if you have a high enough density of hackers, you get better ideas, because no two hackers look at the same engineering or social problem the exact same way. -Our motivations aren't entirely selfless, I must admit. Some of us are doing it because - while we love programming - we want to get better at it. Some of us are doing this because we're also doing startups of our own, and what better place for inspiration than a hacker organization? Still others want to share this incredible hobby with others - because hobbies tend to be more fun when you have people to share it with (ask any golfer and he'll probably tell you the same). +Our motivations aren't entirely selfless, I must admit. Some of us are doing it because—while we love programming—we want to get better at it. Some of us are doing this because we're also doing startups of our own, and what better place for inspiration than a hacker organization? Still others want to share this incredible hobby with others—because hobbies tend to be more fun when you have people to share it with (ask any golfer and he'll probably tell you the same). Will we succeed? Maybe. Maybe not. Either way you look at it, we love what we're doing, and we think it's worth giving it a try. diff --git a/data/projects.yml b/data/projects.yml index f2015979..d120691f 100644 --- a/data/projects.yml +++ b/data/projects.yml @@ -3,14 +3,14 @@ projects: description: Interesting talks for hackers from all walks of life url: /fridayhacks logo: static/img/friday-hacks-logo.svg + - name: Hacker Tools + description: Workshops on skills essential to everyone + url: '#' + logo: static/img/code-logo.svg - name: hackerschool description: Hacking workshops for everyone url: //school.nushackers.org logo: static/img/hacker-school-logo.svg - - name: OSS@nushackers - description: Code repository for NUS Hackers - url: //github.com/nushackers - logo: static/img/code-logo.svg - name: Hack&Roll description: 24-hour hackathon for students url: //hacknroll.nushackers.org diff --git a/layouts/section/fh.html b/layouts/_default/fridayhacks_schedule.html similarity index 100% rename from layouts/section/fh.html rename to layouts/_default/fridayhacks_schedule.html diff --git a/layouts/_default/section.html b/layouts/_default/section.html index 0082bfea..938f33d7 100644 --- a/layouts/_default/section.html +++ b/layouts/_default/section.html @@ -12,7 +12,7 @@

{{ .Title }}

{{ else }} diff --git a/layouts/index.html b/layouts/index.html index 9de23bdc..bca2be92 100644 --- a/layouts/index.html +++ b/layouts/index.html @@ -25,7 +25,7 @@

Upcoming events

-

Friday Hacks

+

Friday Hacks

    {{ partial "friday_hacks_li.html" . }} @@ -34,7 +34,7 @@

    Friday Hacks

-

Hackerschool

+

Hackerschool

    {{ range $index, $event := $.Site.Data.hacker_school.events }} diff --git a/layouts/section/archive.html b/layouts/section/archive.html index f00248c3..887bd827 100644 --- a/layouts/section/archive.html +++ b/layouts/section/archive.html @@ -2,6 +2,7 @@
    +

    {{ .Title }}

    {{ $paginator := .Paginate (where .Site.Pages "Type" "post") 15 }} {{ range $paginator.Pages.GroupByDate "2006"}}

    {{ .Key }}

    @@ -20,10 +21,6 @@

    {{ .LinkT {{ end }} {{ template "_internal/pagination.html" . }}

    -
    {{ end }} diff --git a/static/_redirects b/static/_redirects index 2c286aec..864cf08f 100644 --- a/static/_redirects +++ b/static/_redirects @@ -8,3 +8,8 @@ https://nushackers.netlify.com/* https://www.nushackers.org/:splat 301! # Shortcut to mailing list /ml https://groups.google.com/forum/#!forum/nushackers 302 + +# Moved URLs +/discussion /community +/fh /fridayhacks/schedule +/events /about/#what-we-do diff --git a/static/img/fh.jpg b/static/img/fh.jpg new file mode 100644 index 00000000..a4b9f2ce Binary files /dev/null and b/static/img/fh.jpg differ diff --git a/static/js/toggleShowMore.js b/static/js/toggleShowMore.js index 156d1291..98acfe2f 100644 --- a/static/js/toggleShowMore.js +++ b/static/js/toggleShowMore.js @@ -43,7 +43,7 @@ eventsByListIndex[index] = hiddenEvents; if (!futureEvents.length) { - list.parentNode.appendChild(NO_EVENTS_NOTICE); + list.parentNode.appendChild(NO_EVENTS_NOTICE.cloneNode(true)); } // Remove button if nothing more to show if (!hiddenEvents.length) { @@ -69,4 +69,4 @@ }); }); }); -})(); \ No newline at end of file +})();