hackergarten / hackergarten.github.io Goto Github PK

http://hackergarten.net#event-606878155 isn't a valid URL format.
It should be http://hackergarten.net/#event-606878155 with the extra slash in it

Hi all
I know Hackergarten moved to @[email protected]... but not everyone else ;-)
Would it be an idea to change the Twitter(x-whatever) section to display tweets with hashtag #Hackergarten to make Hackergarten-SoMe-Activities a bit more visible on the site?
Cheers from Zurich
Peter

The hackergarten label is used to determine all issues on GitHub, that can be done at a Hackergarten event. These issues are displayed on the hackergarten website. In my opinion, all issues of the hackergarten website could be solved at a hackergarten.

Unfinished AngularJS code is shown while AngularJS is being loaded:

I would suggest to convert the existing json structure part of the achievements to a similar way as the links section:

From now:

 "achievements": [
      "Achievement without link",
      "<a href='http:/somehost.somedomain'>Awesome work</a>"
    ]

To something like this:

 "achievements": [
      {
        "title": "Achievement without link"
      },
      {
        "title": "Awesome work",
        "url": "http:/somehost.somedomain/"
      }
    ]

It would be nice to have a section that lists the projects that received the most contributions on hackergartens events.

We can harvest the github accounts from the achievement links; create a new page with alphabetical order; link it at the home page.

If there are no achievements, the achievement link should be shown.

just because we can – and love it

Same as with canceled events done here: c380fc1

The event promoted as next event is on 7th June, but the next event is tomorrow (7th May)!

It looks like these branches are leftover from merged pull requests:

• addKarakunAsHackergartenSponsor
• hackergarten-basel-june-2018
• hackergarten-bs-nov+dec2017
• madmas-fix-build

There are a lot of old events using the old event format with the title and location properties. The new event format uses venue and address properties. If we are going to migrate the events from the old to the new format, we can streamline the generateTitle function in the eventlist.js file and the feed generation code in the gulpfile.js file.

There we can publish material for printing, like the logo, posters, signs (to show the way to the event), info material etc.

Sometimes it happens that a previously announced meetup has to be canceled. just removing it from the events.json is one solution, but the event will be not listed anymore so visitors do not have the information, that the event was canceled. Adding the word CANCELED to the title and keep it listed is another solution. I would prefer a special state in the JSON file so a canceled event can be displayed in a different format using CSS, e.g. with a strike through and grayed out the title.

This is just to verify that the changes added in #366 work correctly.

The events.json file contains all the information needed for the map popup. It needs to be enriched by the geocoordinates using the address data.

Instead of having to manually create the locations array (locations.js) file, we could retrieve the lat/long coordinates from a geocode api like geoapify.

Could be done by removing the row for the first two section and using the bootstrap visibility classes instead to have the same behaviour without the white space.

We have some meet-ups, and hackergarten is direction we actually should go.

I would not like to copy ideas. But can I export brand, work as franchise, whatever suits your better.

The first step to try would be some event this month that will be announce on http://hackergarten.net/

This is not in hurry and is to be done when ready, possibly August and/or November

favicon is missing - I can not find the hackergarten.net tab because there are to many tabs open. Maybe one of https://github.com/hackergarten/hackergarten.github.io/tree/master/src/media can be modified to be used.

As of today, the event feed contains all events since 2010. In my opinion it should be enough to add only upcoming events to the feed because past events are of no interest and slow down parsing the feed.

With the changes of #86 is seems to be obvious that the attribute title is not appropiate anymore, we should refactor that :)

What do you think about that ?

The URL property of achievement is optional, but the schema validation requires this property:

[[12](https://github.com/hackergarten/hackergarten.github.io/actions/runs/3393744962/jobs/5641443017#step:4:13):[22](https://github.com/hackergarten/hackergarten.github.io/actions/runs/3393744962/jobs/5641443017#step:4:23):44] Using gulpfile ~/work/hackergarten.github.io/hackergarten.github.io/gulpfile.js
[12:22:44] Starting 'default'...
[12:22:44] Starting 'generate-xml'...
[12:22:44] Starting 'validate-events'...
[12:22:44] ✖ events.json has 1 validation error(s)
[12:22:44]    › Error: Missing required property: url
[12:22:44]      at /5/achievements/3 against schema /items/properties/achievements/items/required/1
[12:22:44] Schema validation failed for 1 file(s) / 1 file(s)
[12:22:44] 'validate-events' errored after 106 ms
[12:22:44] Error in plugin 'gulp-json-schema'
Message:
    There was schema validation error
Details:
    domainEmitter: [object Object]
    domainThrown: false
[12:22:44] 'generate-xml' errored after 108 ms
[12:22:44] 'default' errored after 109 ms

The schema validation should be modified in a way that the URL property of achievement is optional. The URL property a link is still required.

"venue" / "address" attributes do not seem a particularly good fit for a remote event.

As we have a slack community now, we should let us notify on that about travis CI builds.

Pros:

• easier to modify (no HTML stuff around)
• JSON can be read e.g. by a mobile app
• history of event modifications separated of website modifications

Cons:

• one more file to manage
• JavaScript is needed to display the events (or SSI)

This could be done at our next Hackergarten in Lucerne if this idea is accepted!

The current implementation to randomly select the background image works but the browser initially tries to find an image for the function name provided. See screenshot:

On a mobile device like a smartphone the website is displayed the same way like on a desktop computer (but everything really small and to read, you have to zoom and move around a lot). The website should be more mobile friendly.

One more idea for the next Hackergarten… ;-)

Every hack is numbered. If you enter a new hack between two future hacks, you have to reorder the numbers manually. They can be calculated by the JavaScript dynamically, we don't need the hack number in the JSON file.

As we have HTTPS working for hackergarten.net now, we should use that for our RSS fee, too!

If using HTML in achievements-modal the HTML is displayed in plain text.

We may have been affected by an update to settings in embedded timelines. See https://twittercommunity.com/t/deprecating-widget-settings/102295.

There is no licence declared. Can we use the logo/pictures for other hackergarten's (meetup etc.)?

The README file should contain information what a user has to modify to get an event listed on the hackergarten website.

The next event is marked green. But if the next event is canceled or rescheduled, it is still marked green. I would expect the next event that is not canceled or rescheduled to be marked green instead.

When using the multi-column-view (default on wider screens like desktops, notebooks, tablets): The left column is much shorter than the right column. What about moving the sponsor block from the right column to the left one below the download block?

The section should describe how to get started with a Hackergarten session. Useful for people that want to run their own Hackergarten but have not had the chance to participate in one.

I think it would be nice if there is a section on the website were all the Hackergarten locations are listet. Something like "Find a Hackergarten near you". Ideally with information how to find the location, e.g. description, picture from the street, maps.

As we have the https://github.com/hackergarten/contributions to collect potential topics someone could work on during hackergartens, we should show a hint to it on the homepage and try to motivate ppl to use it to collect and prepare stuff.

The website http://www.hackergarten.net/ shows links like How to become a Hacker instead of showing our website. I get complaints regularly from visitors to Hackergarten Lucerne. Either show the Website on the www subdomain, too or redirect to the non-www domain (preferred). This should be a DNS configuration issue.

• DNS hackergarten.net: 185.199.110.153
• DNS www.hackergarten.net: 66.96.149.32

Like in the Twitter widget: A click on the Mastodon toot should open the toot on the Mastodon instance to be able to interact (fav, boost, answer, etc.) easily.