develop clear public messaging near point-of-access to "login / register" field that presents:

• clear info on different types of login accounts and their related permissions -- especially subscriber versus non-subscriber (noting that subscription involves payment, though "no one will be turned away for lack of funds")
• link to our privacy policy and data-breach policy (to be developed!)

When resetting the database, it takes a bit to set up new content structure. Create a few fixtures to at least set up the primary content, like

• home page
• index pages
• magazine departments
• authors

It turns out that tags are used in multiple places, namely the Magazine Article and Media Library.

Rewrite the tags as an app, so it can be reused with different content types.

The current issue displays on the Home Page, but does not contain a link to the issue.

Task

When viewing the home page, the user can click on the current issue title or cover photo and will be directed to that issue.

Several Page models in our project will only need one model instance, namely:

• Home Page
• Magazine Index
• Magazine Tag Index

Since Wagtail 2.4 release, there is now a max_count property that can be added to models, to constrain the number of model instances.

Add max_count = 1 to the above mentioned models.

Several of our content types will need to have associated address information. E.g. meeting worship address, or organization mailing address.

Task

Determine a Django-centric approach to storing address information, primarily for addresses in U.S.

Similar to WordPress, it would be nice to allow the Editor to set the site slogan through the UI.

Task

Add a 'site slogan' field to site settings. This slogan value should appear on the navbar and in the page meta.

The Magazine Index page should show the three latest issues in a section called 'Featured Issues'.

Magazine Articles should be classified with keywords. This will be used for search engine metadata and article recommendations.

Task

Articles have keywords field (many-to-many relationship) using taggit.

We need a way to distinguish organizations from people when displaying authors. Add a boolean field, or some simple way to distinguish the organization. It might be as simple as using 'name' when only a given name is available.

In order to use space efficiently, we can display multiple magazine issues in the same row. This, for example, can be a three column grid with wrapping.

Task

Magazine issues, in both recent and archive sections, show up side-by-side. After a number, say three, have displayed, the next will be displayed in a new row.

The Author model contains a given_name and family_name. However, some author names have suffixes, such as "III" or "Jr."

Task

Add a suffix field to the Author model.

Mary would like to be able to export data from other systems and import them into the WF website. We need to determine what systems this includes, how their data are structured, and how to map/import the data.

There are new releases for several project dependencies, including a security release for Django core. Apply all updates.

In order to improve search engine indexing, we can publish a sitemap.

Task

Create a sitemap for the Magazine Articles and Magazine Issues.

The Home Page should have a Featured Articles section. Allow for any number of articles to be chosen and re-ordered in the Featured Articles section.

We really like the faceted search in the media library of the current website.

Set up faceted search for the Media library and/or Magazine Issue/Article models.

In order to help users keep up-to-date with WF content, we can publish content feed(s).

Task

Create one or more feeds for Magazine content:

• Issues
• Articles
• Combined?

Magazine Author page should show name and related articles.

Task

Create 'Author' page listing all content from a given author. Content should be posted in reverse chronological order. On related content pages, provide a link to the Author page (e.g. on the Article page, link to the Author).

Shape out the initial Meeting data type, including the possibility of meetings having relationships to:

• one another
• memorial minutes
• news items
• events
• other content types

Currently, the Home Page columns are at a 50/50 ratio. However, the right-hand column does not need so much space.

Task

Adjust the home page columns to a 8/4 ratio.

On each individual MM page, display any WGs it sponsors.
On each individual WG page, display the MM that sponsors it.

The Home Page should show the cover photo and title for the latest magazine issue. Clicking the title or cover photo should take the user to the magazine issue page for that issue.

Magazine issues should only be created under the Magazine Index Page. Magazine Articles should only be created under a Magazine Issue. Add 'parent page types' constraints to Magazine Issue and Magazine Article models.

We left off last live code session with a couple of missing elements regarding magazine Article Authors.

Task

Add the following Magazine Article Authors improvements:

• Show the Authors on the Article page
  • authors should be listed like given_name family_name, given_name family_name
• Inside for loop, check for forloop.last and show 'and' before the last item

Useful resource(s)

See the article Django Template Tags and Filters for examples of forloop.last.

Magazine Articles have one or more authors. The authors will have a first and last name.

Task

• Add Author model (or perhaps Person).
• Add slug field to Author model
• Author model fields should include first and last name.
• Add authored_by relationship to Magazine Article model (many-to-many).
• Display authors on Magazine Article
• Add convenient UI for inline selection (and possibly creation) of Author from Article edit page
• Magazine Author page should show name and related articles.
• Magazine Author page should use slug in URL

The Community app contains the following:

• Annual Sessions
• Photos
• Directory of Meetings
• Upcoming Events
• Quaker Nonprofit Organizations
• Online Worship
• Friends Everywhere
• Western Friend Connect

All of those are 'sections' on the Community Index page.

It would be user-friendly to provide a UI for managing the site navigation menu. This would, for example, allow the Editor to add URLs to any internal or external page. Discuss with @marycklein whether it would be important to manage menu hierarchy. If so, consider adding the wagtail-menus plugin.

When searching for authors while adding an article, searching by the last name doesn't return expected results. The field seems only to search for authors who's given name starts with the search string.

Task

Fix the article author search, so that it performs a fuzzy search across given and family names.

We want users to subscribe to the magazine and pay a recurring fee.

Task

• Create a monthly recurring subscription feature
• Ideally, subscription options would populate directly from Braintree
• Allow users to manage their subscription from the User Profile section

Implementation details

• set up plans in Braintree sandbox UI (cannot be done via API)
• enable email receipts
• update subscription form to include first and last name (maybe optional)
• support both recurring and one-off subscriptions
• modify server endpoint to create Customer with payment method when submitting the subscription form
• create a webhook endpoint to receive subscription notifications from Braintree
• create an interface to allow subscribers to manage their subscription
• configure Braintree email notifications for customer subscription events

The Magazine Index Page Archive Issues section should be paginated.

Task

Magazine issues are paginated in the Archive issues section.

In each LibraryItem are several fields, including genre, topic, etc. Currently, the fields are rendered only as text in the LibraryItem template.

Task

Allow users to click on a library item "facet", such as genre, and be taken to a listing of all other library items with the same value for that facet.

Events sometimes span multiple days. Add an optional end datetime field for community events.

We need an initial User Profile page, to serve as the foundation for further work.

Task

Create a basic User Profile page with the ability to edit:

• first name
• last name
• password

Will want to be able to select pre-established "groups" of registrants and send messages to them.

Add an intro text area to the Home Page. The text should be editable via a rich text field.

We need to handle user registration, login, logout, forgot password, etc.

Task

Add user authentication routes and templates to project. If desirable, add crispy forms to easily style the forms with Bootstrap classes.

Events currently have only starting date. It is important for people to know what time the event starts, so they can plan their daily schedule.

Add a time component to the event start date.

Mary would like to specify the order that departments display on the Magazine Issue page. This ordering will be specified once, and apply to all Magazine Issues.

See whether a drag and drop UI is possible.

The LibraryItem topic field currently only allows a single selection. Discuss with @marycklein whether she wants the field to be a multi-select.

Task

If the topic field should be multi-select, define an easy way for multiple values to be selected. Consider also renaming the field, or ManyToMany relationship, to topics.

Possibly related to #604

The Magazine Index Page should show all issues except the latest three in a section called 'Archive Issues'.

Similar to WordPress, it would be nice to allow the Editor to set the site name through the UI.

Task

Add a 'site name' field to site settings. This site name value should appear on the navbar and in the page meta.

Create a media library content type using streamfield to get feedback from @marycklein

Add a basic navigation menu with header and link to the Magazine Index.

We agreed to use an existing, mature CSS framework to help style the frontend pages. To this end, I am recommending we continue working with Bootstrap, but move to Bootstrap 4.

Departments will need to have a top-level page for each department. On that page will be listed all articles published for that department.

The title field is missing from the Home Page template.

Task

Add the title field as an H1 element on the Home Page template.

Add a simple user registration flow. We can enhance the flow later.

Task

Use django-registration package to add simple user registration flow.

It would be cool to manage the Navigation Menu through the Settings UI. E.g. to have a NavigationMenu content type, allowing one instance, that has a stream field that allows you to select various structs containing a page reference or url and a title.

Currently, the registration form contains first and last name fields that aren’t required. Make sure the fields are required.

Original issue

Would be helpful to encourage new registrants to share their Monthly Meeting if they have one.