kimisgold
commented
1 month ago Hmm, this is not deliberate per se, but more the result of how Scripto is setup. Scripto itself is not attached to any site. You can create multiple projects within Scripto, and then associate those projects to a site via the site's navigation configuration. The same Scripto project can be added to the navigation of multiple sites. When that project is associated with a site, it will look at that site's theme to see if it can find a matching Scripto theme.
The page that lists all the available projects exists as a space independent of any site. In your example, https://mysite.com/scripto/1/item exists out of a site context with no site theme to refer to, whereas https://mysite.com/scripto/s/writings/1/1/item has the "writings" site. The page that lists all projects within a Scripto installation cannot be themed as it has no site theme it can match.
At the moment, you could create an index of a site's Scripto projects by creating a page that uses Script blocks. The blocks will ensure accurate links within that site's context.
If you install a custom CSS theme for your Scripto project to match the theme you're using for your Omeka site (let's say the site is called "writings"), most pages turn out as expected: for example, "https://mysite.com/scripto/s/writings/1/1/item" and "https://mysite.com/scripto/1/item" will essentially return the same content with different CSS formatting. In the unthemed version of Scripto, it's possible to access a page which lists all the projects which are part of the Scripto installation, at "https://mysite.com/scripto/project". Trying to access the same page in the custom-themed version (i.e., "https://mysite.com/scripto/s/writings/project") generates a "Page not found" response. Just wondering if this is deliberate or if there's a way to make it possible to generate a page to view all Scripto projects when using a custom theme.