feat(example): refactor p/demo/blog

[louonezime]

This PR is linked to the #4088 for scratching the old /p/demo/blog to make it better but still have it be compatible with the gnoblo-cli.

This is currently in /p/lou/blog as to start with a completely fresh package, the git diff is nicer to read this way.

These are the features:

Base:

• Blog rendering with use of mux
• Filtering of tags through query --> :tag/<tagname>
• Sorting alphabetically --> ?sort=alpha&order=asc
• Sorting from last updated --> ?sort=update&order=asc

Added/modified:

• Listing of all tags
  • Add sorting options
  • Number of posts
• Listing of all authors
  • Add sorting options
  • Number of posts
• Listing in time ranges (start – end) --> ?start=<time>&end=<time>
  • time.RFC3339, // rfc3339 format
  • "2006-01-02", // date only
  • "2006-01", // year and month
  • "2006", // year only
• Filtering of authors like it has already been done for tags (through query) --> :author/<authorname>
• Toggle grid and list mode for Rendering (using gno-columns) --> ?mode=grid or ?mode=list
• Adding pagination
• Updating comments based on comment ID
• Switching to seq.id as indexes
• Improve error handling and messages throughout the package.
• Pinning comments
• Resolve users via r/sys/users registry.

Further (not mentioned in issue):

• Filtering of commenters like it has already been done for tags (through query) --> :commenter/<commentername>
• Sorting from most/least recent (for posts and filters) --> ?sort=recent&order=asc
• Toggle time format -- Is it necessary?
• Add likes to comments
• Add replies to comments
• Add likes to posts -- Is it necessary?
• Mention method to simulate a link to a specific author/ commenter (will link to :author or :commenter)
• Make sorting/toggling options customizable (to disable/ or select)
• Add a customizable option for rendering previews (at home, to add actions)
• Add tests
  • Base of testings with uassert and urequire
  • For all scenarios
• Add moderation
  • Formatting, checking user validity and resolving
  • Assert users
  • Try using authorizable package
• Fix total replies for comments size + reply id are relative to comments
• Add more documentation
  • More doc.gno
  • Add comments
  • Document customisation of rendering
  • Document custom of toggling/sort headers
• Add realm example for the use of the package

Package created to support:

• feat(example): query module #4477

[Gno2D2]

🛠 PR Checks Summary

🔴 Pending initial approval by a review team member, or review from tech-staff

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• The pull request description provides enough details

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🔴 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: louonezime/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🔴 Requirement not satisfied
└── 🔴 If
    ├── 🔴 Condition
    │   └── 🔴 Or
    │       ├── 🔴 At least one of these user(s) reviewed the pull request: [jefft0 leohhhn n0izn0iz notJoon omarsy x1unix] (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🔴 Else
        └── 🔴 And
            ├── 🟢 This label is applied to pull request: review/triage-pending
            ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
            └── 🔴 On no pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

The pull request description provides enough details

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)
    └── 🟢 Not (🔴 Pull request author is user: dependabot[bot])

Can be checked by

• team core-contributors

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[leohhhn]

I think it's better to have this as an option in the render func, no? you then allow the user to render it however they want instead of having to toggle it :)

Also, imagine the blog instance is saved somewhere else except the specific realm its made in, maybe that other instance/realm wants to do something else to it, and with a toggle like this it's dependent on who has the power to change the display mode

[louonezime]

Thanks for the suggestion, but just to clarify then (seeing as though this would change the Render function):

Are you thinking of moving away entirely from how p/demo/blog works (with Render(path string) and internal route handling via mux), and instead have rendering logic be completely controlled externally — like the caller deciding list/grid and rendering themselves per route?

Or do you still see the value in keeping built-in routing/rendering (like RenderPosts, RenderPost, etc.) with query params like ?mode=list)?

(if that makes sense)

[leohhhn]

Or do you still see the value in keeping built-in routing/rendering (like RenderPosts, RenderPost, etc.) with query params like ?mode=list)?

This :)

[louonezime]

4677828

[jefft0]

The slug is being used as part of a path. If the slug has a space like "my slug", then the markdown converter gets confused. Either escape non-path characters in the slug when creating a path, or forbid them in the slug.

[louonezime]

93b96d7

[jefft0]

I see the commit to address this issue. It's better, but still not quite right. I add a post where the slug is "slug/1".
In the post, it shows the escaped "slug%2F1" . When you hover over the title, the URL is "http://127.0.0.1:8888/r/lou/blog:posts/slug/1" and when you click the title, it shows a 404 error. Maybe the URL should be "http://127.0.0.1:8888/r/lou/blog:posts/slug%252F1". Have the do the escaping at the right level.

[louonezime]

sorry, didn't see this:
2d465d4

is this what you meant?

[jefft0]

Yes, now the link to the post works. If you want, you can also make the slug in the rendered post appear as the user originally entered it. For example, I originally set the slug to "slug/1" not to "slug%252F1". It's up to you.

[jefft0]

The realm page has options to filter the blog posts. As we discussed in the dev call, the Render function has a CPU limit. In this video, I did a stress test to demonstrate this limit. I also discuss possible mitigations, including warning the user when getting close to the limit.
https://www.loom.com/share/518211ca05664ac6b00a83704fcce34b

[leohhhn]

Hey @louonezime, can you please take a look at the CI and why it's failing?