No description
- CSS 80.3%
- Python 19.7%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
gettext reads .mo and only .mo. The feature scaffold ignored them in git and left them out of MANIFEST.in, and a released feature is a git tag and a wheel built from it, neither of which runs feature:translate --compile. So every feature shipped with its .po and nothing that reads it: the product answered in English while the workspace it was built in looked perfectly translated, which is why this survived being tested. Same shape as the stylesheets that never reached the built package: what development reads off disk, a release has to be told to carry. |
||
| src | ||
| .gitignore | ||
| MANIFEST.in | ||
| pyproject.toml | ||
| README.md | ||
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.- A minimal auth control in the public header (
layout.navhook): "Log in" / "Log out", soft against products without the auth feature. - 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