codefortucson / codefortucson-site Goto Github PK

When I click on the hamburger nav after it is hamburger'd, nothing happens. The nav menu should drop down. HOWEVER....dot dot dot...I'm on a plane right now with very slow internet so I'd love for someone else to confirm or (hopefully) disprove. I tested on Firefox at the smallest screen width I can pull to.

link is broken.

Related to #65

We don't currently have a smooth system in place for inviting new guests into our Slack channel. Some brigade websites have a Slack invite button on their front page, which presumably would send an email or notification to the Slack admins.

I think that we could benefit from incorporating this into our site.

cc: @meiqimichelle

Add a page with profiles and contact info for people and organizations we are working with in the community. (Highly recommended by CfA.)

Before we redo the Code for Tucson site, we should agree on what message we want to get across. This issue is for tracking this work.

This will follow the wireframe in #64

The site looks great! And here are a couple of things that might make it even better:

• The Cactus and Get Involved lead to the same page (home page?)
• When you navigate to other pages (Calendar, Community, or Projects) Get Involved remains highlighted
• The Google Group is not really "open conversation" ... A non-member has to send a request and become a member before posting. Do you want me to change those settings?
• The Projects (CodeForTucson repo on github) seems a bit empty. Is it possible to get maybe pdf-s of all presentations from Code For Tucson 2013 and 2014?

Thanks for all your hard work!

I think we have an old version of this site in another repo: https://github.com/CodeForTucson/codefortucson.org

We should archive/understand what's going on there/mark as deprecated.

Seeing how I'm starting to work through some site optimizations, I would like to know how much of a difference is made after implementing the changes. Therefore, I would like to take snapshots of several metrics before deploying the first set of changes and also after the final ones.

Which metrics?

• webpagetest.org before
• Google PageSpeed insights before
• webpagetest.org after
• Google PageSpeed insights after

Involves updating image paths throughout site.

Old Code for DC version is commented out in the code, but still there. Would just need to update and un-comment.

This will come after the content work in #63 is done.

Need to add the text of the CfA Code of Conduct to the webpage in a more readable manner than the github link. (https://github.com/codeforamerica/codeofconduct)

• baseurl == url in config at the moment
• this should probably be relative links, but I couldn't figure out how to make this work with gh-pages and DNS settings

Cloudflare offers DNS services for websites and can improve page load times by improving resolution time, caching assets such as images, and providing fall-back cache views if/when the actual site goes down.

The Code of Conduct link in our footer links to the Code for America template for brigade code of conducts instead of our actual code of conduct, which is here.

Can we combine these into one account so we're a bit more consolidated?

Add a link to the Strategic Plan to the website. (Highly recommended by CfA.) Move Strategic Plan to GitHub?

Using GitHub pages is convenient because it will automatically build the site's site files on each commit to the gh-pages branch. However, this also limits our ability to use functionality not provided by GitHub. The downside of using extensions is that we have to manually build the site and then checkin those files.

It might be possible to create a basic TravisCI script to build the files once we checkin to this branch, removing the need to rely on GitHub to automatically generate the site while keeping the flow simple for people wanting to make contributions without learning the whole build process.

Not enough space between articles.

Loads super slow.

I believe it is worth noting that the website breaks when loaded in SSL.

I just spoke to Dan and he had mentioned that you guys were looking to maybe put a calendar widget on the website. I know a couple of groups of people who have done that using Angular 1.x without much trouble (famous last words, right?). React and Angular 2 are also options, but having not researched calendar solutions, I'm not sure what that would involve at this point.

This is in relation to #46.

Related to #65

We don't currently have our current meetup information listed on our website, but Meetup.com has an API to embed that in other websites. We could pull in that information and add a button on our site and I believe that doing this would improve the discoverability of meetup info.

Some brigades have these embeds on their front pages.

cc: @meiqimichelle

Needed:

• name
• twitter
• facebook
• google_plus

Tasks

• separate into CSS, JS, meta, etc
• add description from config
• dynamically load titles
• add mobile support
• pull out header into include

Running PageSpeed Insights (https://developers.google.com/speed/pagespeed/insights/) on our webpage reveals a number of performance and portability issues that should be addressed.

The .hero-text container has a semitransparent background property from assets/_sass/custom.scss.

Remove Code for DC images.

Found on the Code for America repo

https://jekit.codeforamerica.org

After, include global_js in this file.

Add a page with profiles and contact info for partners we are working with inside local government. Identify new partners now that Mark has retired and Andrew has moved to the Water department. (This is highly recommended by CfA.)

Add an about us page with the profiles and contact info of the brigade leadership. (Highly recommended by CfA.)

For when we're feeling ambitious -- the site HTML/CSS is not lovely. Make it lovely by refactoring with Bourbon/Neat. This might also follow #65 .

#19 made me realize that we should find a way to standardize the way that projects are entered and rendered by the site. This will prevent our Stuff we've made section from turning into the Wild West and looking like a hackerspace WordPress blog.

A Project should have some information that is required like a name and a description, and some information that is optional like the project owner, media like presentations or PDFs, and hopefully a link to the repository.

Project
├── required
│   ├── description
│   └── name
└── optional
    ├── contact
    ├── media
    └── source code

I am not familiar enough with Jekyll to say whether custom content types are possible or easy enough to build, but I am confident that with a couple of quick Googles I can get enough information to close this issue one way or another.

There is a post for the 2015 national day of civic hacking in the _projects folder -- we could use that as a base.

There is more info about the event here: http://hackforchange.org/

Since our dependencies are currently all gems, let's add a Gemfile!

@meiqimichelle - what version of Ruby are you using for development?

Current version of Jekyll uses an unsupported Ruby version.

What do we want out initial call to action to be? How to we want to describe our group to the world?