phillycommunitywireless / phillycommunitywireless Goto Github PK

@HotelCalifornia could we avoid this happening in the future by using Dependabot?

Originally posted by @hawc2 in #9 (comment)

Alex requested this in Slack.

A section in the homepage would probably have to be hard-coded into the theme (themes/pcw-hugo-theme), the same way the "Contact us" section currently is. It would be great if it was customizable via a config file or front matter, probably using a Hugo menu.

Anyone can take a crack at this and make a PR, but if not I'll probably get to it in the next few weeks!

• Fork docker-UnifiBrowser
• edit config/users-template.php to add an example user
• ... ?

We should start thinking about what content should go on the site as well as the format it should take.

One thought I had was to provide weekly updates in the form of summaries of the meeting notes, but maybe that would be too much.... minutia? Either way, as it stands, I feel like visitors to the site may get the feeling that either there's no progress being made or that the project is abandoned (like with the philly mesh project).

Note: treat this less as an "issue" and more as an action item

I think it would be useful to provide a how-to guide here in the repository so that anyone who wants to can publish content. This document might look something like this:

• quick guide
  • i.e. how to add/edit content using the GitHub UI
• advanced guide
  • forking(?)
  • installing git/hugo
  • adding/editing content
  • testing locally
  • pushing/making PR

would be great if we could set up a preview of pull request changes

We need better focus indicators for our nav items and links. We're trying to use the Tachyons CSS library for styles as much as possible, but it doesn't have a lot of options for focus, so this will need to be added in a CSS file. Standardizing our "extra CSS" location would be a useful byproduct of this!

Deque's guide on focus indicators is a great place to start for preparation.

how can we add little text below each photo with attribution of credits for taking photos or other descriptors of the photos?

Setting up the public cal & getting the embed link:
https://support.google.com/calendar/answer/41207?hl=en

Then it should be straightforward to embed on site, we could put it in a new page or at bottom of main

change the hugo website so visitors can click a link and it opens a new tab

Hey @HotelCalifornia — I updated our member page with this commit, and now it looks like we're getting a page build failure with the gh-actions process you set up. See here. Any suggestions? Maybe @TGNYC has thoughts?

as seen in #15 the github action workflow fails because the PR author (dependabot) doesn't have proper permissions to push to the repo.

this works in our favour for the moment, because pull request builds shouldn't be deployed over the version from master. however, if someone with permissions were to make a PR, the workflow would successfully deploy.

the fix should be fairly straightforward, and will just require a minor rework of our github action workflow so that the separate steps (build and deploy) are only triggered both at once on master, otherwise run build only.

We should make the most important and commonly-requested information easy to access quickly. The copy should also be edited to remove unnecessary and duplicated information.

Good questions to prioritize:

• Who are we?
• How does it work?
• Is it secure / user data questions
• Why is it free? Will it always be free? Etc

Not so pressing at the moment, but something to be mindful of - the more sections we add to the navbar, the more space it will take up on mobile screens - I think the UI would be improved by replacing this list with a button that brings up a menu or something.

@timtraversy @addiebarron opening a ticket regarding our conversation to simplify the site for ongoing editing and updating. Let's aim to have scoped out what we can do by mid-August

I was experimenting with automating the build and deploy process for this site (see 8ba2070, d79487c, 889ac4e), and part of the process is to deploy to a branch other than master--- gh-pages.

@gwijthoff can you change the source branch to gh-pages? I don't have admin access to this repo, so I can't change the setting myself 😖

We meant to do an accessibility audit of our website. I imagine any issues are minor, but this is a good time to think through any revisions to design principles as we build out the site to be more public facing. @timtraversy is this something that you would be interested in looking into?