tomeshnet / tomesh.net Goto Github PK

@garrying brought up that we have had moments where a long-form content would be lovely on the site:

• field testing
• benchmark results
• maybe even recaps from big events (makerfestival, attending HOPE)

Could we switch to using Bundler and a Gemfile?
That feels more current with current Jekyll practices (e.g., https://jekyllrb.com/docs/quickstart/)

Difficult right now to find how to get a mesh node up...

Thoughts:

• Make clear from 'get involved' and elsewhere on site what equipment we have
• Have instructions on the website? (currently: in tomesh.101/tutorial, groundupworks presentation
• Separate page with instructions and hardware, used as part of virtual mesh night?

Use custom homeserver https://matrix.tomesh.net when using mobile clients

Create content for "Join the Network" parent of Get Involved page referenced in #152

@garrying, @darkdrgn2k, @Shrinks99 and I discussed how the the global nav needs to be updated to account for the map, but also wanted to revisit it more generally (see #152).

Thoughts:

• Add map to global nav (see also #151)
• (potentially) remove Timeline
• (potentially) remove Contact
• discuss secondary navigation

Potential order:
About | Map | Events | Get Involved | Contact

Was discussed awhile ago as an improvement for events

Currently emails going to root daily, maybe we should stop spamming our admin.

I would suggest:

• redirect output to /dev/null

Loooong ago we set up a tinyletter as a first step as a one-way "announce" style mailing list for tomesh events and news.

Talking with @benhylau I've recently re-visited, and happy to share access (pls) to at least a few people, will shortly PR documents with details.

We should also add to the website as a signup!

cc @darkdrgn2k as I know you've mentioned one in the past!

A few points on moving towards SVGs: https://css-tricks.com/icon-fonts-vs-svg/

"Manual Position" isn't clear in describing that it's initiating the node submission process. Maybe we can revise to Submit Your Node

The button is to allow a manual marker. Alternative methods of adding a marker are to search for an address or to use browser gps positioning which are accessible through buttons above the manual button

Perhaps it's a design flaw that it's not understandable or maybe instructions?
@Shrinks99 thoughts?

"Node Name" initial value is UnNamed. This could be a good case for using the placeholder attribute in providing some guidance on how to label the node

Do we have an idea of what we want node names to be?

Additional Bug Fix:

• css id customMarker should be set to height: 95px; to avoid large area of "dead" map where you cannot click and drag.

• add <br/> before this line to wrap better.

Proposing the following changes on website to give a better onboard experience:

• Add a project page with links to specific Matrix chat rooms (Matrix is the primary way we are using to coordinate, we should make that clear)
• Have some text that answers the questions: what is a node, can I host one? even if it's not a simple "this is a node it's 50 bucks and you can point the antenna there to get internet" that people may be hoping for
• Present this Matrix community somehow so people can get a better sense of what we do: https://chat.tomesh.net/#/group/+tomesh:tomesh.net
• Retire Wekan or at least don't feature it as prominently

Do we want to add in secondary nav in order to:

About:

• add timeline under about
• add code of conduct to top nav
• make meeting notes and governance docs more present on site

Get Involved:

• surfacing current projects under get involved (like hardware! prototype node!)

Working from @darkdrgn2k's map codebase (currently accessible at http://map.tomesh.net):
https://github.com/darkdrgn2k/TOMeshNodeMap

We want to have:

• Finalize Schema
• Commit Initial Node List
• new page for map (available at /map)
• add Map to global navigation

We've removed the announcements from the homepage for now (in this commit) and intended to revisit whether we want the functionality once we launch the next version of the site.

Filing an issue so we don't lose the thread.

Clicking on the button from Chrome on Android gives error Unable to launch event.

• offset 2 needs to be revised

• Remove contact page
  • Redirect to home page
• Put an icon for each option that was removed in the header

it would be awesome to link to the new page from #169: https://tomesh.net/build-a-node/

Redesign announcements to be persistent block

• Current idea: full-width block attached to the navigation bar, with short text and relevant link
• Might need a different display for homepage
• Question: Does it make sense an announcement to have a linkable page?

• Add persistent announcement block if an announcement is present and in date range
• Small viewport behaviour
• Styling

I think there are a couple urgent things:

• Indicate the event is passed on event page, similar to #100 (can this be handled with callouts? alerts? similar to bootstrap) (to be handled separately)
• Small write up!!
• update event with final bio
• update timeline to include event
• deal with media coming out of event (below)
  • CC 4.0 BY-NC-SA licensed on our accts

Pictures
https://www.flickr.com/photos/glennmcknight/albums/72157675518024343

Videos
First presentation: https://www.youtube.com/watch?v=f9utcVcAVCQ
Second presentation: https://www.youtube.com/watch?v=O1idjfeB3EM
Third: ?
Fourth: ?

Audio
https://soundcloud.com/gmcknight/mesh-toronto-panel-discussion

As @garrying pointed out in PR #32 there is no way to navigate back to the proposed Event Page from an individual Event. We gotta like add some IA to this website with the expanding content.

[edited out of date sitemap image out]

And we would need global navigation. These are pretty typical patterns for that...

This was broken off PR #13, would like to have a separate page where people can view all the events we have (currently only the 1-2 upcoming ones are shown on the front page).

This issue was raised by @patcon, currently there is no quick way to visit the website page for an event based on the description we publish in our ics.

Would be great to include a link in our description.

@benhylau not sure if this is a CaLDAV or ics issue? (Assuming we should handle it in ics tho)

I think the project information and possibly some way to communicate the skill sets each one needs would be beneficial to have on the website. It is currently still a challenge for new people joining the tomesh to discover projects, and eventually finding something that matches with their interests and skills. Here is a pad we have thrown together as an emergency answer to "what is the status and how can I help?"

https://cryptpad.fr/code/#/1/view/5WwseaPrSrnmkDuNVcBiTw/zqwAlbdxT0t9BHfSEFunbT7kB9Se5oAW-sHix6kK4Qo

Look into using illustration or other type of imagery. Consider looking for photos with more person presence.

This is to track the deployment of Let's Encrypt on the server.

Installation

• Install Let's Encrypt on web server
• Configure tomesh.net DNS
• Determine an email for notices and lost key recovery
• Generate certificate files
• Configure NGINX to use SSL
• Configure server block to use https
• Set up auto renewal

Post Installation

• Decide on redirecting http to https
• Check crontab weekly job
• Check that publish.sh from jekyll-hook doesn't cause issues

Hoping to have these things for the conference, aiming to launch by December 1:

• a page (maybe tomesh.net/state-of-our-networks) dedicated to the conference where a schedule, registration, location info etc... could go?
• have some sort of registration (a form [ugh I know]) to collect basic registration details (we need to have a sense of workshop attendees)
• redirect the event listing to the page automatically (possible?)

Considerations:

• Moving Have More Questions prompt to footer
• Replace Have More Questions with Timeline link and intro paragraph to lead into Timeline

Since the addition of Timeline to the navigation (#106), the menu is not fitting items nicely. The temporary fix is to allow for horizontal scrolling. A suggestion is to update the nav to be a panel, invoked by a button. A few points to be mindful of:

• The new design pattern should only be visible at the $on-palm breakpoint
• Accommodates all menu items
• Hit areas of all menu items are at an adequate size (~44px, referencing iOS Human Interface Guidelines)
• Clear active, and focus states
• Clear affordance to invoke and toggle display of menu items

From @garrying PR #15 ...

I think we should pull the email into the footer.html file so that is shown on every page!

We should have a license indicated on our website before we start putting much more content up there.
Something like `(C) Toronto Mesh. Content and documentation licensed under XXX. 2016 Code licensed under XXXX." They should be added to our repository as well!

My preference for content would be Creative Commons 4.0 (CC BY-SA 4.0 International for text/content.

For code however I am unsure, looks like all of the site stuff (Jekyll, Skeleton, Font Awesome) are MIT license, I've tended toward stronger GPL variants but don't have a strong preference.

Thoughts?

(actually, should say I've be up for an anti-copyright attribution too ✨ but don't know how to do that for code)

1. Generate .ics from event announcement collection.
2. Show fa-calendar-plus-o on the announcement and link to .ics file.

• Possibly introduce sub-headings (brief, medium sized paragraph) to text-only pages to help frame content
• Sourcing images for content pages (?)

Suggested to include subtle transitions on hover, active, and focus states.

@Shrinks99 is interested in updating branding, finalizing a logo (yay!).

Preliminary thoughts from our discussion:

• Colour palette
• Distinguish footer (maybe different footer?) (possible PR #179)
• Add more graphics throughout

I'm thinking something like a banner "This event is in the past" at the top of old events... could be handled as a conditional?

A few questions outstanding regarding how explicit we should be with documentation of our setup:

• jekyll-webhook
• webserver config
• server monitoring
• server backups
• add server.md for tomesh.net to service_setup

Following up on #77

Related to #84

Coordinate with funding workgroup on implementation.

Copy should mention #welcome along with #general.

Picking up the conversation from PR #25:

We ( @garrying and @YKCzoli ) discussed leaving meeting minutes on github as markdown is rendered nice enough and they are a bit of a deep dive into tomesh. I think we could have an 'About' and 'Contribute' page with those details.

Thoughts?

Reference: https://jekyllrb.com/docs/continuous-integration/

Outlines tasks that need to be done to add Monitoring information to the website map

• Add CJDS to server (Docker container?)
• Run Pinging script on server to generate json file
• Run Walker script on server to generate json file
  • Finish rewrite of walker script in python
• Host Prometheus Server and Grafana
• Display information on map (MapMonitoring-Links branch)

For events like: https://tomesh.net/2016-11-03/virtual-mesh/

Clicking on the location link #virtualmesh:tomesh.net opens another tab of the page itself. I am guessing this happens when posts don't have a locationMap attribute. The behaviour is awkward, I think we should have it not as a link instead.

By the way, can locationMap be a virtual location? Or should we add another key to allow for virtual locations like: https://chat.tomesh.net/#/room/#virtualmesh:tomesh.net

We've created some draft copy for a timeline page here and discussed adding it to showcase the projects we are working on.

• Current working title (in main navigation): Timeline
• Create timeline Collection
• Timeline content: Small (Tweet-size), Medium (400 words?), Large (long-form)
  • Setup Front-matter to represent different sized content
  • Stick to chronological sorting for now
• Create top-level page in repository
• Reference for CSS/JS: https://webdesign.tutsplus.com/tutorials/building-a-vertical-timeline-with-css-and-a-touch-of-javascript--cms-26528
• Account for image and text content

• Add Timeline to top navigation
• Create Timeline page
• Create collection for Timeline events
• Create Timeline event post template (front matter, format)
• Display Timeline posts on page
• CSS/JS