lnug / website Goto Github PK

Where we display "Next Event" info, we should have a button that allows you to add the event to you gcal.

We also have a public calendar that we should share as this gives people info about ticket releases

https://github.com/lnug/feedback/issues/70

Old site links are in google SERPS

We need add more videos to the archive page:

• Go to the LNUG Youtube channel: https://www.youtube.com/channel/UC-qjgj2TnRoI1ZmFFaN3FeQ
• Find a talk, and add the "video" property to data/archive.json

Warning: Talk name and video titles may differ.

Hi guys,
I'm struggling to build this app on my machine, and getting some build errors.
Can anyone help me, please.

This is what I have installed
node v5.5.0
npm v3.6.0

Not sure if I'm doing anything wrong.
See attached npm-debug.log
npm-debug.log.txt

Cheers

We have a rich archive of videos on youtube and vimeo.

Each months videos should live in a playlist which can be accessed via the youtube api

The vimeo videos could be ported to youtube to be consistant.

see:
https://github.com/lnug/feedback/issues/80
https://github.com/lnug/feedback/issues/82

The speaker for the JSONata session is listed as null in the archive page (https://lnug.org/archive.html)...

  April 2017

  How Bionode.io uses Node.JS Streams to handle genomic big data - Bruno Vieira
  Automatically build and publish Node and Electron applications for Linux - Martin Wimpress
  JSONata: A declarative syntax for querying your JSON data - null

Please could you change it to 'Andrew Coleman'

Thanks!

Something similar to the new Barcelonajs site

I have now done a spring clean on the youtube channel ready for 2016!

I have:

• Fixed video titles
• Fixed Video descriptions
• Fixed incorrect / missing playlists
• Properly tagged the videos

Now I need some help backdating the videos in the archive. its not a glamorous task!

The site uses app cache to ensure the site works offline.

At the moment AppCache nanny checks for updates, when it finds an update it just refreshes the whole page. This experience is not ideal.

We should look at how this can be improved.

Initially, I would suggest showing the user a notification of some kind and asking if they would like to refresh the page to see new content.

currently we tweet them to appear in tweet lists. is not robust enough

At some point this repo was configured so that gh-pages uses the master branch (as opposed to the gh-pages branch).

At the moment we have both the source and the compiled output in the root directory of the master branch which can be confusing. Github requires that the generated markup be in the root.

When first timers want to change the sponsors page, they see sponsors.html go and change that, run the server and job done. Except that change will get overridden on the next build.

I've updated the readme to explain this but wonder if we can separate the two.

I wonder if master should just be used for the source and we have a script which pushes the generated files into a gh-pages branch.

We should add this to the landing page in a progressivly enhanced way

<script>
  ((window.gitter = {}).chat = {}).options = {
    room: 'lnug/discuss'
  };
</script>
<script src="https://sidecar.gitter.im/dist/sidecar.v1.js" async defer></script>

can we move this from the footer and bring it closer to the talks header?

thoughts @benbyford

I'm currently seeing the following:

Viewing on Chrome/Mac.

Works on my Nexus 5x.

pre-july, the archive does not display speaker names propers

example

https://github.com/lnug/lnug.github.io/blob/master/data/archive.json#L140

maxwellito should be Max Dulduc

The idea is to give people insights to upcoming speakers.

This should be dynamic, based on the current state of github.com/lnug/speakers

"We could pull in all the milestones setup in github I guess, that would give a list of the next few events. Would need to think about where in the UI it sits. Not gonna look at this till after the redesign is out."

• @simonmcmanus

Simon, when you get a chance can you rebuild the site? The second speaker has added a talk description so there's now content to pull in there...

@lnug/contributors please can we take a look

Not sure when this stopped working.

Hi @simonmcmanus

I'm getting an error when running npm run build to update the speakers - it looks like it's failing on the speclate --build script.

This worked last time I ran it, but we had all 3 speaker slots full - is it something to do with there only being one speaker confirmed so far?

I saw you did some updates recently - so I trashed my npm_modules and reinstalled - no help.

Any guidance helpful...

Thanks.

Error excerpt below:

> [email protected] html /Users/adam/Documents/community/LNUG/website
> speclate --build

Speclate v12.1.0 cli v5.0.1

Validating spec..
  ok

Generating markup..
/Users/adam/Documents/community/LNUG/website/node_modules/sizlate/lib/update-node.js:21
            if (data.length) {
                    ^

TypeError: Cannot read property 'length' of null
    at updateNode (/Users/adam/Documents/community/LNUG/website/node_modules/sizlate/lib/update-node.js:21:21)
    at /Users/adam/Documents/community/LNUG/website/node_modules/sizlate/lib/do-render.js:18:13
    at Array.forEach (native)
    at Object.module.exports [as render] (/Users/adam/Documents/community/LNUG/website/node_modules/sizlate/lib/do-render.js:17:47)
    at /Users/adam/Documents/community/LNUG/website/node_modules/speclate/lib/page/load-components.js:23:30
    at Array.forEach (native)
    at renderComponent (/Users/adam/Documents/community/LNUG/website/node_modules/speclate/lib/page/load-components.js:20:20)
    at /Users/adam/Documents/community/LNUG/website/node_modules/speclate/lib/page/load-components.js:69:46
    at tryToString (fs.js:426:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:413:12)

See the markup in:

https://github.com/lnug/lnug.github.io/blob/master/pages/layout.html

Can just be an external link:

https://github.com/lnug/feedback/blob/master/PARTICIPATING.md

moved from:

https://github.com/lnug/feedback/issues/72

seems out to me

Our audience knows what it wants to see, it would be great to provide a mechanism for the audience to suggest potential speakers.

I have suggested a google form for speed of implementaion.

The site needs some simple and fast css transitions between pages.

While the page loads data it shows the layout which can result in the footer being present and the disappearing to the bottom of the page when the content is loaded. it would be good to fix this at the same time.

@iancrowther pointed out https://daneden.github.io/animate.css/ which has a good collection of transitions. It would be a case of working out which ones we want to use and orchestrating them carefully.

Can we get a tile that is "your company here" kind of thng?

@maxwellito have you got 15 to have a go?

see the sponsors branch and visit /sponsors.html

we need a placeholder for bronze sponsorship

the site is currently showing info for the Feb event, which is cool but people probably still want to know what is going to be happening tonight at the January event.

following discussion with @iancrowther on gitter we agreed that in future these should be Twitter handles, and not as they have been the last two months, which is github handles.

Same goes for the newsletter.

cc. @jkbits1 @web-bert

At some point there was an issue with the google analytics so the code was copied to the top of the client.js file.

Its pretty ugly as the first thing in the client.js file, it should be moved into its own file or we should be able to require another module.

https://github.com/lnug/website/blob/master/client/index.js

notes:

• Please ensure tracking events still fire on first page load and when navigating between pages.
• If using an npm module please ensure we don't increase load times by loaded unnecessary javascript into the browser.

We have an out of date sitemap.

It should be deleted.

We have some amazing photos from twitter & instagram which we should make use of.

Is anyone interested in putting together an image gallery?

npm start uses mongoose but its a bit config heavy.

can we update to use https://www.npmjs.com/package/http-server

can we make sore of this? its in the footer atm and should be more prominent

we have discussed reducing the talks to 2 in the night - to allow more time for talk/banter/networking, and allow talks to finish on time

@simonmcmanus - how difficult would it be to accommodate the option of 2 or 3 talks in the website build script? If you can point me to the right direction, I'd be happy to take a look.

@simonmcmanus and I were saying that a PR should be complete and this should be reflected in the guide.

We should have a set of guides as to why a PR will be declined.

Some of the urls from the old website are still in google and giving some dodge results, try searching:

lnug sponsors

We need to add some permanent redirects to maintain that google juice.

"we will never share your data"

This should be in context to the signup form on the landing page

https://github.com/lnug/lnug.github.io/tree/master/assets/design

see #11

When I first started working on this repo we have lots of markdown files in github we wanted to pull into the website.

Currently, the website build tasks pulls the markdown files and converts to html.

I think having files across two repos just adds confusion and complexity. Those files should be moved into the pages directory as plain old html.