jekyll-theme-isotc211 0.5.9 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6a97ab90aa68b7a0a1be2b559322d789da9df61e33d0a98c2bd37ec4c81a1221
-  data.tar.gz: ba0c76651e5ea1393f00be92c855a7b5910437982c01dcad18c6c91957bc180e
+  metadata.gz: 482d1d5747fe0dadc1c23bba86430df036e18fe766f4c7342a547197a072b771
+  data.tar.gz: 59e2cd6ae9a73341a09fca839debb43ed37072ba8f8f64b4dcc083e5204b483d
 SHA512:
-  metadata.gz: ab7be9ae97a0da72b3c2057e82c0d36d5d92e7141930063f1606e3e17e0927ebf882d54529bc78ddc10950f74ccfdd257d08ba9cbbc77e4aecfb71ae572ebe42
-  data.tar.gz: bdc1faaba3de5b2b668aa4aaf836c25e577e91e50939d413744c783d15bbd34e9ea293125ff2ff50ca2ce012d9bd3e2174da91b57a67e0a096b6737ae9d385fe
+  metadata.gz: 7b651ba082ef22a067a3aef87f62a3b4cf87a901174629460f0601bdf9f0335f710709a006d1e2c40ce789eb969776d5bf9760f385d1f7d354df8bad91908f17
+  data.tar.gz: 0a7663f06a5cda88124909a96efdd466d8c231fbfe5a1ad832f13407f4ec135c336482d14d6fc6832af85272cd4f9ca17934247c5dd74d28d7f09d43ce445d2a

data/README.md

@@ -1,73 +1,83 @@
-# ISO/TC211 theme by Ribose
+# jekyll-theme-isotc211
 
-This is a theme used across ISO/TC211 sites powered by Ribose,
-including https://www.isotc211.org
-and resource sites such as https://geolexica.org/, https://def.isotc211.org/.
+Modern Jekyll theme for ISO/TC 211 resource sites — Vite 7, Tailwind CSS v4,
+dark mode, Inter font, responsive design.
 
+Used by [www.isotc211.org](https://www.isotc211.org),
+[registry.isotc211.org](https://registry.isotc211.org), and
+[standards.isotc211.org](https://standards.isotc211.org).
 
-## Configuring site
 
-Theme relies on accompanying helper plugin
-(note: plugin gem version should match theme version):
+## Installation
 
-```
-group :jekyll_plugins do
-  gem "jekyll-theme-isotc211-helpers"
-  # ...
-end
+Add to your Gemfile:
+
+```ruby
+gem "jekyll-theme-isotc211", "~> 1.0"
 ```
 
-Other recommended plugins to add to your Gemfile:
+And to `_config.yml`:
 
+```yaml
+theme: jekyll-theme-isotc211
 ```
-group :jekyll_plugins do
-  gem "jekyll-theme-isotc211-helpers"
 
-  # ...
-  gem "jekyll-data"
-  gem "jekyll-asciidoc"
-  gem "jekyll-external-links"
+Your site also needs `jekyll-vite`:
+
+```ruby
+group :jekyll_plugins do
+  gem "jekyll-vite"
 end
 ```
 
-Configuration keys:
-
+And a `package.json` with Vite + Tailwind:
+
+```json
+{
+  "private": true,
+  "type": "module",
+  "devDependencies": {
+    "@tailwindcss/postcss": "^4",
+    "@tailwindcss/typography": "^0.5",
+    "postcss": "^8",
+    "tailwindcss": "^4",
+    "terser": "^5",
+    "vite": "^7",
+    "vite-plugin-ruby": "^5"
+  }
+}
 ```
-title: <site title to be used in meta and in body>
-title_html: <if specified, is used in body instead of title>
 
-font_awesome_kit_url: <url to your FA kit, free kits are OK with stock theme version>
 
-google_analytics:
-  id: UA-XXXXXX-X
+## Configuration
 
-committee:
-  id: <numerical committee ID>
-  name: <full committee name>
-  home: <committee homepage, probably on iso.org>
-  links:
-    - url: /about
-      title: About
-    - url: /strategic-policy
-      title: Strategic Policy Statement
-    - url: /faq
-      title: FAQ
+```yaml
+title: "Resource site for ISO/TC 211 Geographic information/Geomatics"
+title_html: "ISO/TC&nbsp;211"
+brand_sub: "Harmonized Resources Maintenance Agency"
+description: "Resource site description"
 
-# Builds browsable resource pages
-resource_listings:
-  schemas:
-    # Source directory containing resources, relative to site source root.
-    # Each subdirectory within will be treated as a resource
-    resource_root: 'schemas'
+header_logo: "/assets/iso-red.svg"  # Optional, defaults to iso-red.svg
 
-    # The path, under which resource browser will be available to site visitors
-    index_url: 'schemas'
+google_analytics:
+  id: UA-XXXXX-Y
 
-    # These control resource index & individual resource pages
-    index_title: "Schemas"
-    resource_label: "schema"
+committee:
+  id: 211
+  name: Geographic information/Geomatics
+  home: https://committee.iso.org/home/tc211
+
+nav:
+  - title: About
+    url: /about/
+  - title: Blog
+    url: /posts/
 
-always_show_committee_link_on_landing: yes
+footer_links:
+  - title: Geodetic Registry
+    url: https://geodetic.isotc211.org/
+  - title: Schemas
+    url: https://schemas.isotc211.org
 
 awards:
   - title: 2010 Lawrence D. Eicher Leadership Award
@@ -75,116 +85,72 @@ awards:
 
 social:
   links:
-    - url: https://twitter.com/<account>
-    - url: https://github.com/<org>
-    - url: https://www.facebook.com/groups/<group ID>/
-    - url: https://www.linkedin.com/groups/<group ID>
-
-# Committee site maintainer
-powered_by:
-  title: <organization name>
-  url: <organization site>
-  logo_path: /assets/<logo-filename.svg>
-
-# Primary navigation
-nav:
-  items:
-    - id: home
-      url: /
-      title: Home
-      description: Standard resource links & latest news
-    - id: news
-      url: /posts
-      title: News & Articles
-
-# Footer navigation (example)
-footer_nav:
-  - url: <committee site URL>
-    title: ISO/TC XXX
-```
-
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub
-at https://github.com/riboseinc/jekyll-theme-isotc211.
-
-This project is intended to be a safe, welcoming space for collaboration,
-and contributors are expected to adhere
-to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
-
-
-## Theme development
+    - url: https://twitter.com/ISOTC211
+    - url: https://github.com/ISO-TC211
 
-Generally, this directory is setup like a Jekyll site. To set it up,
-run `bundle install`.
-
-To experiment with this code, add content (projects, software, specs)
-and run `bundle exec jekyll serve`. This starts a Jekyll server
-using this theme at `http://localhost:4000`. 
-
-Put your layouts in `_layouts`, your includes in `_includes`,
-your sass files in `_sass` and any other assets in `assets`.
-
-Add pages, documents, data, etc. like normal to test your theme's contents.
-
-As you make modifications to your theme and to your content, your site will
-regenerate and you should see the changes in the browser after a refresh,
-like normal.
+favicon_svg: "/assets/favicon.svg"
+favicon_ico: "/assets/favicon.ico"
+```
 
-When your theme is released, only files specified with gemspec file
-will be included. If you modify theme to add more directories that
-need to be included in the gem, edit regexp in the gemspec.
 
-### Building and releasing
+## Layouts
 
-#### Manual test during development
+| Layout | Description |
+|--------|-------------|
+| `default` | Full page: head, header, main, footer, Vite JS |
+| `base` | Raw content pass-through |
+| `home` | Content + optional news roll |
+| `page` | Generic content page |
+| `post` | Blog post with illustration support |
+| `posts` | Blog index |
+| `base-page` | Content page with header (for resource browser) |
+| `resource-index` | Resource directory listing |
+| `resource-page` | Two-pane BlueprintJS resource browser |
 
-When you’re working on visual aspects of the theme, it’s useful
-to see how it would affect the end result (a site *built with* this theme).
+Sites can override any layout by creating a file with the same name in their
+own `_layouts/` directory.
 
-Here’s how to develop the theme while simultaneously previewing the changes
-on a site. The sequence would be as follows, assuming you have a local copy
-of this repo and have a Jekyll site using this theme:
 
-1. For the Jekyll site, change Gemfile to point to local copy
-   of the theme (the root of this repo) and run `bundle`.
+## CSS
 
-   For example, you’d change `gem "jekyll-theme-isotc211"`
-   to `gem "jekyll-theme-isotc211", :path => "../jekyll-theme-isotc211"`.
-   The relative path assumes your site root and theme root are sibling directories.
+The theme provides these CSS files in `_frontend/css/`:
 
-2. Run `bundle exec jekyll serve` to start Jekyll’s development server.
+| File | Content |
+|------|---------|
+| `header.css` | Fixed glassmorphic header, brand bar, navigation |
+| `footer.css` | Footer grid, links, social icons |
+| `typography.css` | Section labels, headings, meta text |
+| `page.css` | AsciiDoc documentation prose defaults |
+| `home.css` | Sections, blog list, awards, about page |
 
-3. Make changes to both theme and site directory contents.
+Sites can add their own CSS files and import them in their
+`_frontend/entrypoints/application.js`.
 
-4. If needed, kill with Ctrl+C then relaunch the serve command
-   to apply the changes you made to the theme
-   (it may not reload automatically if changes only affect the theme and not the site
-   you’re serving).
 
-4. Once you’re satisfied, release a new version of the theme — see below.
+## Migration from v0.x
 
-5. (To later bump the site to this latest version: revert the Gemfile change,
-   update theme dependency version to the one you’ve just released,
-   run `bundle --full-index` to update the lockfile,
-   and your site is ready to go.)
+1. Remove `font_awesome_kit_url` from `_config.yml`
+2. Remove `_sass/` directory from site
+3. Replace `jekyll-plugin-frontend-build` with `jekyll-vite` in Gemfile
+4. Add Vite config files (`vite.config.ts`, `postcss.config.js`, `config/vite.json`)
+5. Update `nav` config from `nav.items` array-of-objects to flat `nav` array
+6. Update `footer_nav` to `footer_links`
+7. Remove Babel config if present
 
-#### Releasing
 
-Make sure theme works: build script is under construction,
-so use good judgement and thorough manual testing.
+## Development
 
-1. First, update version number in .gemspec within this repo’s root.
+```sh
+bundle install
+```
 
-2. Then, execute `./develop/release`. This does the following:
+Point a site to the local theme via Gemfile:
 
-   * Builds new gem version
-   * Pushes gem to rubygems.org
-   * Creates new version tag in this repository
-   * Pushes changes to GitHub
+```ruby
+gem "jekyll-theme-isotc211", path: "../jekyll-theme-isotc211"
+```
 
 
 ## License
 
-The theme is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+MIT

data/_config.yml

@@ -1,98 +1,42 @@
-title: "An ISO TC 211 site"
+# Theme defaults — sites override these in their own _config.yml
+title: "ISO/TC 211 Site"
+title_html: "ISO/TC 211"
+brand_sub: "Geographic information/Geomatics"
+description: "An ISO/TC 211 resource site"
 
 email: open.source@ribose.com
 
-description: >-
-  Welcome to this ISO/TC 211 site.
-
-# The protocol + domain name of the site
-# url: "https://geolexica.com"
-
-includes_dir: .
-
 markdown: kramdown
 
-permalink: /blog/:month-:day-:year/:title/
-
-# font_awesome_kit_url: <url>
-
-# google_analytics:
-#   id: UA-XXXXX-Y
-
-# Used for copyright notice and possibly more.
-org:
-  name: International Organization for Standardization
-  website:
-    url: https://www.iso.org/
-    title: www.iso.org
-  email: copyright@iso.org
-  address: |-
-    Chemin de Blandonnet 8
-    CP 401
-    1214 Vernier, Geneva
-    Switzerland
-
-# Social profile navigation
-# social:
-#   links:
-#     - url: https://twitter.com/…
-#     - url: https://github.com/…
-#     - url: https://www.facebook.com/groups/…
-#     - url: https://www.linkedin.com/groups/…
-
-# committee:
-#   id: <number>
-#   name: <full name>
-#   home: <committee’s external home page URL>
-#   links:
-#     - url: /about
-#       title: About
-#     - url: /strategic-policy
-#       title: Strategic Policy Statement
-#     - url: /faq
-#       title: FAQ
-
-# Main site navigation.
-# Layouts and pages can specify priority nav items
-# using frontmatter key nav_items
-# pointing to an array listing nav item IDs.
-nav:
-  items:
-    - id: posts
-      url: /posts/
-      title: News & Articles
-
-always_show_committee_link_on_landing: no
-# Switching this to “yes” will enable the Committee site link
-# to appear on landing page even when expandable menu is collapsed.
-
-# Footer navigation
-footer_nav:
-  - url: https://committee.iso.org/home/tc211
-    title: ISO/TC 211
+plugins:
+  - jekyll/vite
+  - jekyll-feed
 
 collections:
   pages:
     output: true
     permalink: /:path/
 
+committee:
+  id: 211
+  name: Geographic information/Geomatics
+
+social:
+  links: []
+
+nav: []
+footer_links: []
+
 exclude:
   - Gemfile
   - Gemfile.lock
-
-  - babel.config.js
   - package.json
   - package-lock.json
-  - monitor.sh
   - node_modules
-
-  - github_deploy_key.enc
-  - deploy.sh
-  - monitor.sh
-
-  - .sass-cache/
-
-  - vendor/bundle/
-  - vendor/cache/
-  - vendor/gems/
-  - vendor/ruby/
+  - vendor
+  - .sass-cache
+  - vite.config.ts
+  - postcss.config.js
+  - bin
+  - _frontend
+  - config/vite.json

data/_frontend/css/footer.css

@@ -0,0 +1,117 @@
+/* ── Site Footer ─────────────────────────────────── */
+
+@layer components {
+  .site-footer {
+    background: #f8fafc;
+    border-top: 1px solid rgb(229 231 235 / 0.6);
+    padding: 3rem 0;
+    transition: background-color 0.2s;
+  }
+  .dark .site-footer {
+    background: #020617;
+    border-top-color: rgb(255 255 255 / 0.06);
+  }
+
+  .site-footer__inner {
+    max-width: 80rem;
+    margin: 0 auto;
+    padding: 0 1rem;
+  }
+  @media (min-width: 640px) {
+    .site-footer__inner { padding: 0 1.5rem; }
+  }
+  @media (min-width: 1024px) {
+    .site-footer__inner { padding: 0 2rem; }
+  }
+
+  .site-footer__grid {
+    display: grid;
+    grid-template-columns: 1fr;
+    gap: 2rem;
+    margin-bottom: 2rem;
+  }
+  @media (min-width: 768px) {
+    .site-footer__grid { grid-template-columns: repeat(3, 1fr); }
+  }
+
+  .site-footer__logo {
+    display: flex;
+    align-items: center;
+    gap: 0.625rem;
+    text-decoration: none;
+  }
+  .site-footer__logo img { height: 1.75rem; }
+  .site-footer__logo-text {
+    font-size: 0.875rem;
+    font-weight: 700;
+    letter-spacing: -0.025em;
+    color: #1e293b;
+  }
+  .dark .site-footer__logo-text { color: #e2e8f0; }
+
+  .site-footer__tagline {
+    font-size: 0.875rem;
+    color: #64748b;
+    margin-top: 1rem;
+    line-height: 1.625;
+  }
+
+  .site-footer__heading {
+    font-size: 0.75rem;
+    font-weight: 600;
+    color: #0f172a;
+    text-transform: uppercase;
+    letter-spacing: 0.05em;
+    margin-bottom: 1rem;
+  }
+  .dark .site-footer__heading { color: #fff; }
+
+  .site-footer__links {
+    list-style: none;
+    padding: 0;
+    margin: 0;
+    display: flex;
+    flex-direction: column;
+    gap: 0.625rem;
+  }
+
+  .site-footer__link {
+    font-size: 0.875rem;
+    color: #64748b;
+    transition: color 0.15s;
+    text-decoration: none;
+  }
+  .dark .site-footer__link { color: #94a3b8; }
+  .site-footer__link:hover { color: #0f172a; }
+  .dark .site-footer__link:hover { color: #fff; }
+
+  .site-footer__bottom {
+    padding-top: 2rem;
+    border-top: 2px solid #e3000f;
+    display: flex;
+    flex-direction: column;
+    align-items: center;
+    gap: 1rem;
+  }
+  @media (min-width: 640px) {
+    .site-footer__bottom { flex-direction: row; justify-content: space-between; }
+  }
+
+  .site-footer__copy {
+    font-size: 0.875rem;
+    color: #94a3b8;
+  }
+  .dark .site-footer__copy { color: #475569; }
+
+  .site-footer__social { display: flex; gap: 0.75rem; }
+
+  .site-footer__social-link {
+    color: #cbd5e1;
+    transition: color 0.15s;
+    text-decoration: none;
+  }
+  .dark .site-footer__social-link { color: #475569; }
+  .site-footer__social-link:hover { color: #64748b; }
+  .dark .site-footer__social-link:hover { color: #94a3b8; }
+  .site-footer__social-link svg { width: 1.25rem; height: 1.25rem; }
+}