nextcloud / nextcloud/collectives

Allow any page to show recent subpages

Open
#978 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
195
Forks
51
Avg merge
1d 2h
Merged PRs (30d)
48

Description

I really like how top-level documents show a widget of subpages that were recently edited. That's a great mechanic for helping people discover new stuff that's been updated! Sadly, it seems to be only available at the top level of Collectives.

Describe the solution you'd like
I think a straightforward way to do this is to offer some kind of embed code that can sit in a template or page. Even if it's just a shortcode, like [[recent_pages]], that could be really useful for those of us who are effectively building miniature internal wikis in Nextcloud.

Describe alternatives you've considered
A more elaborate way of thinking about the problem may be to take the route that AnyType takes: shift to a structure where Pages can be represented as different kinds of structured objects (Person, Project, Organization, Species, whatever) with an internal constructor for any kind of data structure desired.

Obviously, that's a tall order and probably a lot of abstract work for non-obvious payoff, but the result is a kind of polymorphic database/wiki thing that can be structured to whatever needs an organization has.

Additional context
For my organization (We Distribute) our internal Nextcloud infrastructure is being built around various needs for research, fact-checking, discovery, and collaboration. As an independent news organization dedicated to promoting news of Fediverse development, this kind of shared knowledgebase for our organization as well as outside contributors is vital.

We really like AnyType, but I'm personally pushing for a tool that integrates with the infrastructure we already have. It doesn't necessarily have to be the crazy second thing I described, but a little more flexibility with widgets in pages and templates could be a huge deal.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the existing top-level recent-subpages widget and how pages or templates currently render reusable content; the issue names no files or tests. Define the supported page and template scope, then verify that recent subpages can be displayed outside the top level and that the requested widget behavior is covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
content, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.