wintercms / wintercms/wn-builder-plugin

Record List Components and their Scopes.

Open
#72 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
40
Forks
15
PR merge metrics
No merged PRs in 30d

Description

I am still struggling to understand on how to work with the scope aka filtering of my records.
So it would be great to have some kind of explanation or within the plugin in the backend the option to create scopes there.
I read in the Winter CMS on how to override a component with a scope, but as there is no explanation in the wn-builder documentation, i still do not know how to implement a filtering.

I created a FAQ with the builder plugin with the simple columns "question", "answer", "category".
What i am trying to find out is how to use the scope to filer only one of the categories.

Just my 2 cents ... otherwise you guys know how much i love this project!
Greetings from this corner of the planet.

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 reading the wn-builder documentation on components and compare it with the Winter CMS guidance on overriding a component with a scope. Clarify how to filter the FAQ records to one category, and determine whether the documentation should explain the workflow or whether a backend scope-creation option is actually requested. Done means a newcomer can follow the documented filtering process.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.