bcgov / data-fp

Data Showcase for BCGOV Data based on Jekyll

data-fp

This provides the frontpage of data.gov.bc.ca.

Requirements

1. Jekyll
2. npm
3. bower
4. Grunt

There is also a Vagrant box and Dockerfile available to make setup easier.

Installation

1. Clone the repo and cd into the directory.
2. npm install
3. bower install
4. grunt build

This will initialize the site files.

Development

There is a grunt dev task that acts as a watcher for development purposes. It will trigger a rebuild of the site as files change.

By default, the site is available at http://localhost:4000.

Starting Jekyll

To serve the site using Jekyll, use the grunt serve --host=<host> --port=<port> command. By default, it uses the following options:

host=0.0.0.0
port=4000

The site will be available at http://<host>:<port>.

Content

Content is not tracked inside this repo. The site uses a custom post type called visualizations and is stored in Markdown format inside the _visualizations directory.

Visualization front-matter

The visualization post type follows this format:

---
layout: visualization
title:
published:
source:
  name: 
  url: 
iframe_url: 
order: 
---

Field	Explanation
layout	The layout used when Jekyll generates the static HTML. Leave as visualization.
title	The title of the visualization.
published	Boolean value. true shows the visualization on the front-page inside the carousel, false hides it.
source	The source of the visualization. The name provides a name, and url provides a link to the source.
iframe_url	An embeddable version of the visualization. This is included on the front-page of the site inside a carousel.
order	An optional field that determines the order of the visualizations. Ascending order.

Here is an example of a visualization:

---
layout: visualization
title: My Visualization
published: true
source:
  name: The name of my Visualization source
  url: http://link.to.my.visualization.source.com
iframe_url: http://link.to.my.visualization.frame.com
order: 100
---

data-fp's Issues

hide header/footer when scrolling the page, provide more space for visualization/features

hide header/footer when scrolling the page, provide more space for visualization/features

Add predictive search to search bar

Add predictive search of the catalogue content to both search bars, so it's similar to the BCDC search.

Add project lifecycle badge

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

search not working

when entering a search term and then selecting the magnifying glass to search, the following message appears

@ll911

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 205 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

align the header and footer style with blog

align the header and footer style with blog
https://blog.data.gov.bc.ca/

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 203 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Need to redo header to match blog site

@h3devin are you available to update the header of data.gov.bc.ca to match this
http://engage.gov.bc.ca/data/ ?

@ll911 can we simply replace the ribbon items on the blog with what we have on our data.gov site?

Ideas for next release

These are some ideas to improve the data.gov webpage for users.

motivation: https://www.apple.com/macos/sierra-preview/

Header
reduce the size of the header (see issue #32)

Carousel
Having to click on the arrows which are on either end is a bit cumbersome, and it takes some time to find the visualization you're looking for. To improve the user experience the carousel should be removed entirely and replaced with a 'single page' type experience, where the visualizations appear below each other and occupy the full page.
This will also provide more space for upcoming visualizations which won't fit in the limited space of the current carousel window. We'll just have to make sure scrolling is not used in the viz to prevent interaction with the viz when the user is trying to scroll down the page.

Text boxes below the carousel

Generally there is too much text here. Having 3 'Most popular..' sections feels sloppy and unnecessary. The popular sections should be combined to a single top 5 list.

Twitter Feed
This should match the feed used in https://blog.data.gov.bc.ca/

Include metatag with git hash

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 204 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Update to data.gov

There aa few more small changes needed, some of which (unfortunately) conflict with the last changes made.

• Add DataBC back to the title, just to the right of the bc gov logo, as it is with the current prod deployment but without the vertical yellow line next to the bc gov logo)
• return the ribbon, as in the current site:
  
  but have the ribbon items move to the hamburger as soon as the user scrolls down -as done on this pages: http://engage.gov.bc.ca/govtogetherbc/
• add 'Dataset Usage' to the ribbon to the right of 'Contact Us'. The hyperlink should go here: https://catalogue.data.gov.bc.ca/data/site-usage/dataset
  -Remove “Site Usage” from the hamburger menu and ribbon.
  -remove the magnifying glass from the header until the user scrolls down.
  
• implement #40
  It should appear at the same time the ribbon items move to the hamburger.

@ll911

#42 fine and tune

#42 fine and tune
@Mbrownshoes

1. can you provide the context for site description, so @h3devin can include in _config.template.yml file, this is required by google search and SEO
2. can you confirm the location for "Datasets Usage" tab, I thought it should beside the Catalogue, last tab should be the "Contact Us"

@h3devin seems the site title text doesn't align with the Province logo in the new header.

Add missing topics

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

Short Code	Organization Name
AEST	Advanced Education, Skills & Training
AGRI	Agriculture
ALC	Agriculture Land Commission
AG	Attorney General
MCF	Children & Family Development
CITZ	Citizens' Services
DBC	Destination BC
EMBC	Emergency Management BC
EAO	Environmental Assessment Office
EDUC	Education
EMPR	Energy, Mines & Petroleum Resources
ENV	Environment & Climate Change Strategy
FIN	Finance
FLNR	Forests, Lands, Natural Resource Operations & Rural Development
HLTH	Health
FLNR	Indigenous Relations & Reconciliation
JEDC	Jobs, Economic Development & Competitiveness
LBR	Labour Policy & Legislation
LDB	BC Liquor Distribution Branch
MMHA	Mental Health & Addictions
MAH	Municipal Affairs & Housing
BCPC	Pension Corporation
PSA	Public Safety & Solicitor General & Emergency B.C.
SDPR	Social Development & Poverty Reduction
TCA	Tourism, Arts & Culture
TRAN	Transportation & Infrastructure

NOTE See an error or omission? Please create an issue here to get it remedied.

replace new background photo as season

replace new background photo as season

It's Been a While Since This Repository has Been Updated

This issue is a kind reminder that your repository has been inactive for 201.98 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 201.98 days.

If this product is being actively maintained, please close this issue.
If this repository isn't being actively maintained anymore, please archive this repository.

Thank you for your help ensuring effective governance of our open-source ecosystem!