New API endpoints

[rallisf1]

I've been playing with the API lately, but don't want to spam the PR I started with my other ideas so here they are:

1. I wonder how bad of an idea a /search endpoint would be as the db would practically have to search all the sections (and symbols) of the site to find the page they are in...
2. Getting a full page works well and it's great for sites where most components change among pages (e.g. landing pages), but when having a blog or a product catalog very few components change. What would be the best way to get specific sections of a page? Should that be added to the current page endpoint as another url parameter or create a new one?

Tell me your thoughts and I'll work on the PRs.

[mateomorris]

1. That sounds straightforward to me - considering Supabase has full text search https://supabase.com/docs/guides/database/full-text-search

Curious what your use case is?

2. A query parameter could work

https://primoserver.com/api/marketingsite/about?section=9jdo9

but I kinda prefer the idea of using a hash link, since it's more consistent and you could just remove the '/api' to go directly to that section on the page.

https://primoserver.com/api/marketingsite/about#section-9jdo9

[rallisf1]

Hash values don't reach the server side though. It's either a query parameter or a new endpoint.

[mateomorris]

Ah that's a bummer, I guess query param it is then

[rallisf1]

Just made a PR.

This is my final blog widget component with pagination. No page linking though. Although it's easy to add I'm not sure it will play nice with search engines, so little to no point implementing it.

News (1).json