Currently group routes are accessed via group id like so: /groups/:group_id... but this makes for ugly urls like /groups/1 and /groups/2. They're not descriptive and they do not give you a good idea of which group you're trying to access.

Instead, we want groups' urls to be referenced by their slug like so: /group_:slug and would result in urls like /english-service and /bethanies.

Right now, post banners are rendered at full resolution. Let's update it to use Cloudinary to return a smaller image.

• Add route to create announcements for new bulletins at /:group-slug/bulletins/new/announcements
• Add link to new bulletin form to link to announcements form
• Add back button to bring user back to bulletin form
• #21 Create component to render a draggable announcement: {{announcement-editor}}
• Render a list of {{announcement-editor}} for every announcement in bulletin.announcements

When going to /groups/1/bulletins/new, the default value for publishedAt should be the upcoming Sunday.

Tests

• If going to the page on a Monday, it will default the publishedAt to the following Monday.
• If going to the page on a Sunday, it will default the publishedAt to the next Sunday.

• Bulletin validation
• Announcement validation

Fixes #150 by using an outline button.

Add auto-complete to

• Series
• Speaker

We determine whether daylight savings is in effect depending on whether moment().isDST() === true, which depends on the client.

As a result, if the user is in a region that does not follow DST, we won't know that we need to apply DST.

Caused by #7.

Currently, the groups at the end of the homepage are hard-coded. Let's load them dynamically.

• Update mirage to have more (random) groups with server.create("group"): https://github.com/openmcac/mcac-js/blob/master/mirage/scenarios/default.js#L3
• Fetch all groups from the server: Hint
• Iterate through them to create each group

Series hasMany Sermon

Default ordered by Sermon#publishedAt

Going to /groups/1/bulletins/new, the description field should be a well formatted publishedAt value (eg. November 5, 2013, 9:30am).

Tests

• Given a date (2013/11/5 9:30am), the description will be well-formatted.

You can format a date with moment.js (which is already included in the app).

Let's try to get some detailed designs for these two screens:

Things to consider:

• What should be our color scheme? My initial proposal would be purple and white... similar to Yahoo... but I'm open for other ideas. The direction I want to go is have a minimalistic design with a white background. The highlight color can be whatever you want... but let's have a couple of options that the team can choose from.
• What fonts should we use? How many different fonts and font sizes do we need? I'd suggest doing some research on Google to figure out the right balance.
• For desktop, keep your design within a 12 column, 960px grid. For more information, take a look at http://960.gs, there are photoshop templates that can give you some grid overlays.

As for the timeline, take your time. This is a big task that will take a while... just try to give us updates and prepare a little screenshot of your progress for each status meeting.

cc: @atsiang @chohinlo

If you have any questions, you can email me directly or add a comment to this issue.

When going to /sunday to view this Sunday's bulletin, convert the markdown into JavaScript.

Consider using a computed property (ie. displayServiceOrder) in the bulletin model if it's not too sluggish when creating/updating bulletins (/sunday-service/bulletins/new).

When rendering the bulletin on /sunday just render the computed property.

On second thought, we probably want to create a markdown component to render markdown for us.

No need to apply any additional styling just yet.

Requires #14 to be merged.

Let's add links to the sites of the Chinese congregations.

• Chinese: 滿地可華人宣道會 http://montreal-cac.org/
• Mandarin: 教会网站 http://mcac-m.blogspot.ca/

Show them on desktop and hide them in smaller screens.

Currently, the Sermon editor is only displayed when editing a bulletin. We should show it even when the bulletin is being created.

• Update mirage endpoints to log in and create bulletins
• Update bulletin form to always show sermon editor
• Update sermon editor to save sermon after bulletin is created

The installation instructions need to include phantomjs and ember cli

• npm install -g ember-cli
• npm install -g phantomjs

Point /sunday's canonical URL to the specific bulletin.

Specs needed for #98.

Interact with a JSONAPI-compliant endpoint at /api/v1/posts.

Manage posts

• Create a post
  • /:group_slug/posts/new
• Edit an existing post
  • /:group_slug/posts/:post_id/edit
• View an existing post
  • /:group_slug/:post_id/:post_slug
• Delete an existing post
• List the posts in a group
  • /:group_slug/posts

• Speakers HABTM Sermons
• Speaker belongs to User (linking accounts)

When creating a new bulletin, we need to populate the bulletin model with the most recent bulletin's announcements.

• Create announcements model
  • id
  • postId
  • bulletinId
  • description
  • postiion
• Create mock server endpoint @ /api/v1/announcements/latest?group_id=#{group_id}
• Add announcements to model hook of NewBulletinsRoute.

https://github.com/danielspaniel/ember-data-factory-guy

Create a reusable component to render announcement elements that can be edited and reordered.

Breakdown of tasks:

• create a component called {{announcement-editor}}
• make it a draggable li element
• add button to add an {{announcement-editor}} below the current one
• clicking on the text will turn the div into a textarea with buttons to
  • Save
  • Cancel
  • Delete

Make sure it's compatible with bootstrap-markdown.

Required for #11.

Let's find an appropriate library / widget to show a password's strength and only allow the user to change their password if the new password is strong.

Research https://github.com/soulim/ember-cli-bootstrap-datepicker and verify whether we can switch to it.

It looks ugly

Currently, when you hit / all you see is an empty page.

In our first release, the only public page that we'll have available is the bulletin (/sunday). Update the routes so that going to / will redirect the user (and change the URL) to /sunday.

• Redirect / to /sunday
• Create an integration test (in tests/integrations directory) to verify that visiting / redirects to /sunday

Useful resources:

• http://emberjs.com/guides/routing/
• http://eviltrout.com/2014/06/27/integration-testing.html

• Add route to create new bulletins at /:group-slug/bulletins/new
• Add form controls to input bulletin fields
  • Bulletin name
  • Publish date
  • Description
  • Order of service
• Add button to save bulletin
• Save the bulletin via POST /bulletins
• #24 Populate bulletin with the most recent bulletin's announcements

Mockups can be found here:

https://www.dropbox.com/sh/ojr77c626lt7wvi/AAC_n4yuac1Cia4-USxB_Wu8a/design/mockups/rendered

Most likely need to install it in index.html so that it is automatically tracking every page.

Sign up for any Google Analytics account and confirm that you can get it tracking on your personal account. After that, just replace the account IDs with XXX's and we'll put the actual one in when we have one.

Plot the offering records on a graph

The service order is expected to be in Markdown format.

We'll need to research some libraries that we can use that will render a Markdown editor in place of a textarea.

Currently, all routes have the time title. Let's incorporate https://github.com/kimroen/ember-cli-document-title to generate custom titles for various routes.

We want to have a small blurb about MCAC just to introduce ourselves while we prepare the other features of the site.

A group's index action will be their home page and should display:

• Group banner
• Profile picture
• Group name
• Short description
• Target audience
• Typical meetup time
• Posts

Add the ability to tag sermons with a set of keywords.

Examples: humility, sharing, faith, suffering

You should be able to filter sermons by tags.

Refer to this for guidelines:

http://stackoverflow.com/a/18323040/567090

Steps:

• Go to /login
• Enter username and password
• Hit the Enter key

What happens:

• Nothing

What is expected to happen:

• It'll log you in.

List Groups

• Access group list at /groups
• Add links to
  • create new group
  • show current group
  • edit current group

Create Group

• Access new group form at /groups/new
• Form fields
  • Banner uploader
  • Name
  • Slug
  • About

The new backend will give sermons a many-to-many relationship with speakers.

• Create a new selector for speakers
• Create the speaker if it doesn't already exist
• Use existing speaker
• Associate speaker to sermon

• Install third party library to provide notifications
  • https://github.com/poteto/ember-cli-flash
• Saving bulletins
  • Success message on save
  • Error message on failure

Read: http://www.ember-cli.com/#developing-addons-and-blueprints

Convert the markdown-textarea component created in #10 into a dedicated ember-cli addon so that other people can reuse/import the component in their projects.

Try to keep the code design consistent with https://github.com/plusacht/ember-bootstrap-datetimepicker.

• create new addon in new git repository ember-cli-bootstrap-markdown
• rename the component to bs-markdown-textarea
• remove old markdown-textarea component from mcac-js
• import new ember-cli-bootstrap-markdown into build via ember-cli

Let's gather information for the page we create to introduce the various fellowships at our church.

• Timothy Fellowship
• Bethany Fellowship
• AE Central
• AE South
• AE ?
• Jacob Fellowship

This is blocking #25 from being merged.