splent_feature_skin_store
Storefront skin for the SPLENT marketplace product: an App Store × PyPI look built on the splent.io brand (light UI, ink navy headings, brand blue, sparing amber accents).
A skin in SPLENT is a light feature that layers aesthetics on top of the
brand-agnostic theme: it sets the design tokens and registers one stylesheet
that cascades last. All markup lives in the content features (marketplace,
configurator); this feature only styles it.
What it provides
THEME_TOKENS(STORE_TOKENS): the splent.io palette shared with the landing page and docs — brand#1a73b2, ink#0a0f1a, amber#e9b71f, Inter type.skin_store.css(asset order 200): storefront chrome — hero, search, cards, detail sheet, terminal snippets, configurator states, collapsible SPL rows.- One account entry at the far right of the public header (
layout.nav.endhook). Anonymous visitors get "Log in". Signed-in readers get an "Account" menu built from what the product installs: My account, API tokens (when apikeys is installed), Admin panel (only for a role the admin feature lets into its dashboard) and Log out. It takes over auth's own header link, so there is never a second one, and follows auth's "Log in link in the header" setting (AUTH_NAV_LOGIN, or Settings > Access). Soft against products without auth. - A store look for auth's sign-in page when the product renders it in the
public shell (
AUTH_LOGIN_LAYOUT = "public_base.html"in the product's[tool.splent.config]): a centred card, store buttons and alerts. - Suppression of the CMS admin toolbar, which belongs to wp-admin-style products and not a public storefront (framework hook-override seam plus a CSS belt).
Usage
Select it in a product derived from marketplace_spl (optional feature
skin_store), or install it directly:
splent feature:install splent-io/splent_feature_skin_store
Tests
splent feature:test skin_store
Metadata
Release files for splent-feature-skin-store 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| splent_feature_skin_store-0.2.0.tar.gz | 15.8 kB | Without provenance | Details for splent_feature_skin_store-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| splent_feature_skin_store-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for splent_feature_skin_store-0.2.0-py3-none-any.whl |
Total release size: 32.3 kB
Release files / splent_feature_skin_store-0.2.0.tar.gz
| Download URL | splent_feature_skin_store-0.2.0.tar.gz |
|---|---|
| Size | 15.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8dbaf3c303caf375006d502ec3feade85c9c6676824e5b2b2ab9ab10ddc51ac3
|
|
BLAKE2b-256 checksum How to use checksums |
725e6caa809bf375883c41bd230003b604e34fc354c2380c93b4833050d4e462
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / splent_feature_skin_store-0.2.0-py3-none-any.whl
| Download URL | splent_feature_skin_store-0.2.0-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2f1a4605b12d7e1d50c5938d3f97b8ef430f705483be6c9caee00de6e21fcdd
|
|
BLAKE2b-256 checksum How to use checksums |
f43c579c974d76b238d5d818f8630a7f8c49601bca5df98922ac807bd47d48de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for splent-feature-skin-store 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.