harmen/hypha
1
0
Fork 0
Code Issues 142 Pull requests 4 Projects Releases Packages Wiki Activity

Minimal tag-based index #298

New issue
Open
opened 2020-04-08 12:18:05 +00:00 by matthijskooijman · 1 comment
matthijskooijman commented 2020-04-08 12:18:05 +00:00 (Migrated from github.com)
Copy link

For rubrics at de stadsbron, a minimal version would be:

  • A fixed system page like the current index page
  • Which shows articles with one tag, which is specified through an URL parameter
  • Articles are displayed using a title and excerpt (needs #290), no image yet.
  • This page can then be linked from the tags displayed on any other page
  • This should be sorted by descending publication date, which is done by loading the page XML for each page displayed (this is inefficient, but removes the need for migrating these dates to the index initially).

Some code for this is probably already present in the https://github.com/PlanBCode/hypha/tree/datatype-tag_list branch (of which this is a slimmed down version).

Later improvements:

  • Pagination
  • Include a featured image for articles
  • Include text pages and other datatypes
  • Put a sort date in the index (copy of the publication date for articles) to allow sorting on that (requires running a migration for existing articles).
  • Allow visitors to customize sorting behaviour.
  • Create a new datatype to show such an index, to allow adding a header, footer, custom sorting, etc. This is #127.
  • More complex tag filter, might be needed to generate a front page. This might require some kind of "lang:taglabel" format, since not all tags might be available in all languages. This is essentially #310.
  • Support hierarchical tags. This is #377.
For rubrics at de stadsbron, a minimal version would be: - [x] A fixed system page like the current index page - [x] Which shows articles with one tag, which is specified through an URL parameter - [x] Articles are displayed using a title and excerpt (needs #290), no image yet. - [x] This page can then be linked from the tags displayed on any other page - [x] This should be sorted by descending publication date, which is done by loading the page XML for each page displayed (this is inefficient, but removes the need for migrating these dates to the index initially). Some code for this is probably already present in the https://github.com/PlanBCode/hypha/tree/datatype-tag_list branch (of which this is a slimmed down version). Later improvements: - [ ] Pagination - [x] Include a featured image for articles - [x] Include text pages and other datatypes - [ ] Put a sort date in the index (copy of the publication date for articles) to allow sorting on that (requires running a migration for existing articles). - [ ] Allow visitors to customize sorting behaviour. - [ ] Create a new datatype to show such an index, to allow adding a header, footer, custom sorting, etc. This is #127. - [x] More complex tag filter, might be needed to generate a front page. This might require some kind of "lang:taglabel" format, since not all tags might be available in all languages. This is essentially #310. - [ ] Support hierarchical tags. This is #377.
matthijskooijman commented 2020-05-06 14:09:48 +00:00 (Migrated from github.com)
Copy link

For now, the plan is to maybe not extend the current tag page (much) further, but instead implement #87 to generate homepages and tag-based "dossier" pages. The code that generates the lists for #87 should probably be based on the current tag index, though, and could maybe be reused by the current tag index to generate the actual content.

Also, for now the idea is to just create these "dossier" pages separately, without linking the tags on a page to these pages (they would still go to the current tag index system page). On the longer term, we could maybe add (manual) per-tag configuration for this (e.g. "when you click this tag, go to (text)page").

For now, the plan is to maybe *not* extend the current tag page (much) further, but instead implement #87 to generate homepages and tag-based "dossier" pages. The code that generates the lists for #87 should probably be based on the current tag index, though, and could maybe be reused by the current tag index to generate the actual content. Also, for now the idea is to just create these "dossier" pages separately, without linking the tags on a page to these pages (they would still go to the current tag index system page). On the longer term, we could maybe add (manual) per-tag configuration for this (e.g. "when you click this tag, go to <this> (text)page").
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
hypha-117
combined
Render-links-in-article-comments
base64-subject
hypha-119
festival-translation
Issue/66-paste-from-word
issue/306-Install-new-hypha-fail
datatype-tag_list
testtranslation
clarify-comment-rules
wymeditor-css
newtext-more
newtextservicemethods
pr219
searchfunctie
default_datatype
koppelting
No results found.
Labels
Clear labels   
Component: User interface

   
Component: Wymeditor

   
Help wanted

   
Level: Difficult

Structural changes, need discussion

  
Level: Easy

Under 4 hours of work

  
Level: Moderate

Under 16 hours of work

  
Pagetype: Festival

   
Pagetype: Mailinglist

   
Pagetype: Peer reviewed article

   
Pagetype: Text

   
Privacy GDPR AVG

   
status: has conflicts

   
Status: Needs changes

   
Status: Needs discussion

   
Status: Needs review

   
Status: Ready to merge

   
Status: Waiting for response

   
Type: Bug

   
Type: Enhancement

   
Type: Question

   
Usecase: De Stadsbron

   
Usecase: Koppelting

   
Usecase: MeetjeStad

   
Value: Coders

Enhancement of codebase, API, documentation

  
Value: Security

   
Value: Users

Improve user experience, add new features

  
Value: Visitors

Improve navigation, styling

No labels
Component: User interface
Component: Wymeditor
Help wanted
Level: Difficult
Level: Easy
Level: Moderate
Pagetype: Festival
Pagetype: Mailinglist
Pagetype: Peer reviewed article
Pagetype: Text
Privacy GDPR AVG
status: has conflicts
Status: Needs changes
Status: Needs discussion
Status: Needs review
Status: Ready to merge
Status: Waiting for response
Type: Bug
Type: Enhancement
Type: Question
Usecase: De Stadsbron
Usecase: Koppelting
Usecase: MeetjeStad
Value: Coders
Value: Security
Value: Users
Value: Visitors
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harmen/hypha#298
No description provided.