pghnaz / pghnaz.org Goto Github PK

Cf. http://2017.manual.nazarene.org/paragraph/p200/s6/

See https://github.com/pghnaz/branding.

Add 11ty to dev dependencies (https://www.11ty.io/docs/getting-started/#install-eleventy-into-package.json)

Include information for CSS custom properties and comments.

The current site navigation mirrors http://nazarene.org/.

• Who We Are
• Find A Church
• Organization
• Calendar
• Give
• News
• Contact Us

This is all well and good, but I’m inclined to follow a more modern story-board design approach using call-to-action prompts. The story-board should lead users on a journey, continuously calling them to a single action and inviting them to other actions along the way. The target user should be someone unfamiliar with our district or the Church of the Nazarene, but it should still make sense to someone who knows us better.

1. Make “Find a Church” the only call-to-action button/link in the top navigation for the homepage.

2. Then have a diptych inviting people to give (link to online giving form) or attend an event (link to calendar); reiterate “Find a Church” for people to attend a service or other local church event near them or support a local ministry through giving.

3. Then have a triptych introducing people to our auxiliaries (SDMI, NMI, NMI); reiterate “Find a Church” for people to get involved locally.

4. Then have an at-a-glance introduction inviting people to meet our leaders (link to District Officers or District Organization) and check out our other district ministries (links to MCNC and PDCD); reiterate “Find a Church” for people to get involved in the unique ministry opportunities near them.

5. Tie the user and our people back to the mission (link to mission), vision (vision page?), and legacy (link to history?) of God’s work among us in western PA since 1898.

6. Then put a site-map-like inside navigation panes in the footer.

Add instructions for contributing and installing locally.

This keeps the theme files all in one place.

Create a layout that lists contact information for all local churches, Mt. Chestnut Nazarene Center, Eastern Nazarene College, and the Global Ministry Center.

Make it searchable and sortable/filterable by name, city, county, zone, and year organized.

@czechju, we talked about transforming some of the info in the District Journal into a more user-friendly (and maintainable) format. If we wanted a publicly available roll of clergy, I was thinking we could do something similar to what we’re doing with local churches by creating a src/clergy/ directory and then a json file for each member of clergy.

The information in the District Journal was originally intended to be publicly available, but I see no reason to insist on publishing personally identifying information like email, address, or phone numbers on the site (not without a members-only login or something). I suppose if we wanted to keep the sensitive info in Git (perhaps for Board of Ministry use), we could make a private repo in GitLab for free and then use the GitLab API for querying the JSON key-value pairs we want to render on the public site.

{
  "name": "First M. Last",
  "roleCode": "PAS",
  "yearGranted": 2019,
  "membership": "Church Name"
}

The following rolls of ministry are outlined in the District Journal.

• Ordained Elders
• Ordained Deacons
• Licensed Ministers
• Tenured Evangelists
• Commissioned Evangelists
• Registered Evangelists
• Evangelism Service, Retired
• Registered Song Evangelists
• Commissioned Song Evangelist
• Retired Song Evangelists, Non-Credentialed
• Consecrated Deaconesses (grandfathered only)
• Licensed Deaconesses (renewals only)
• Commissioned Ministers of Christian Education
• Licensed Directors of Christian Education
• Ministers and Laypersons Serving Connectional Interests
• Commissioned Ministers of Music

Include when and where to use inline JSDoc blocks.

• Create directory; git init
• README.md
• “Set up repository” Project
• Add LICENSE
• Add Code of Conduct
• Set up Eleventy
• “Create initial content” Project

• Copyright
• Brand assets (new)
• Privacy Policy
• Terms of Use

@czechju, in order to migrate to GitLab, you’ll need to create a GitLab account with the same email address (not necessarily the username) as your GitHub account.

cf. https://docs.gitlab.com/ee/user/project/import/github.html

Use local church GeoJSON data with the Google Maps API data layer (cf. https://developers.google.com/maps/documentation/javascript/datalayer). Add GeoJSON data for Eastern Nazarene College and Mt. Chestnut Nazarene Center.

Format fullCalendar to use the public calendars for the district, SDMI, NMI, and NYI.

This should be the page that appears when a user selects a link from the Church Contact Directory in pghnaz/caimhoff#24.

Let’s face it, no one should have to learn how to install Node.js for the first time alone. And the command line is not for everyone.

@czechju, I’m following up on this from #20. This will be JSON data, probably as an array. For example:

"services": [
  {
    "name": "Sunday School",
    "day": "Sunday",
    "time": "10:00"
  },
  {
    "name": "Sunday Morning",
    "day": "Sunday",
    "time": [
        "09:00",
        "11:00"
    ]
  },
  {
    "name": "Youth Group",
    "day": "Wednesday",
    "time": "19:00"
  }
]

Do you think this should be something we load in the GeoJSON files in src/data/churches/? Or would you prefer to store this in a separate file, say, src/content/churches/LOCAL_CHURCH_NAME/services.json as an 11ty directory data file?

I’m concerned about storing too much data in the GeoJSON files that are not related to the map. But if we’re going to render a map anyway on local church pages, I suppose it’s more a matter of preference than performance. It’s easy enough to keep it in the GeoJSON for now until we decide that we want it in a separate data file. Thoughts?

@czechju smacked me over the face with inspiration on our last conference call.

Especially on wider screens, the negative space next to the data is begging to be filled with a graphic of some kind. On smaller screens, the graphic could appear above or below the text. And on any screen size, a photo or a logo, or an avatar, or a text graphic, of some kind would go a long way to help break up the page visually and add personality to the local church information.

@czechju, we’ve talked about adding badges for active local church ministries (e.g., Children’s Bible Quizzing, Youth Quizzing, Caravan) and possibly recognitions (e.g., WEF giving).

It’d be great if we could use this thread to establish which badges we’ll include in the initial launch, and then to brainstorm about what they should look like. I’m imagining text based graphics, similar to these: https://discourse.gohugo.io/badges.

And, of course, we’ll actually need to gather the relevant data for the local churches.

The following pages from the main site mirror the structure of nazarene.org/

• Who We Are
• About
• Articles of Faith (use WP REST API from nazarene.org?)
• Beliefs
• Core Values
• Mission
• History
• FAQ
• How to Know Jesus
• District Officers
• District Assembly
• District Boards and Standing Committees (separate pages or include on “District Officers” page?)
• District Auxiliary Organizations (separate pages)
• Education and Clergy Development
• ENC
• Global Partners
• Contact Us

That is churches currently without an assigned pastor. Make sure to invite people to contact the district office about possible candidates.

Should the metadata for local churches live in 11ty data files (cf. https://www.11ty.io/docs/data-global/)?

Is there a reason to create .md files for the individual church pages?

Each local church GeoJSON properties object does not include empty values. The wiki should include a detailed explanation of every property with an example and proper styles (e.g., punctuation for phone numbers, street addresses, etc.)

Also include a link to https://geojson.io/ for testing coordinates.