Eclipse 1.1.0: A Modern, SEO-Friendly Theme for Geeklog

The Eclipse theme for Geeklog reaches an important milestone with version 1.1.0.

The first version was mainly a concept: an experiment showing what a more modern Geeklog interface could become.

Eclipse 1.1.0 is different. It is now a practical theme designed to modernize real Geeklog websites while keeping the CMS, its permissions, URLs, forms and plugin architecture intact.

For site owners maintaining long-running Geeklog installations, this means it is now possible to significantly improve the user experience, administration interface and technical presentation of the site without replacing Geeklog itself.

A modern responsive theme for existing Geeklog websites

Eclipse remains a child theme of Denim, which provides a safe compatibility foundation.

On top of that foundation, Eclipse adds a modern responsive interface for desktop, tablet and mobile devices.

The public-facing theme improves navigation, content presentation, forms, pagination, article metadata, footer controls and accessibility.

The administration area has also been extensively redesigned.

Administrators can choose between a new Modern workspace, with a responsive sidebar, dashboard and mobile-friendly navigation, or Classic Eclipse, which keeps a more traditional Geeklog administration experience.

Version 1.1.0 also expands the visual customization options with the new Vivid Red palette, available alongside the existing Eclipse palettes.

The goal is not to replace Geeklog's administration logic, but to make it easier and more comfortable to use.

Better foundations for SEO

SEO was an important part of the work on Eclipse 1.1.0.

The theme does not promise automatic ranking improvements — content quality, authority and many other factors remain essential — but it provides a much cleaner foundation for search engines and editors.

Eclipse introduces or improves:

• responsive mobile layouts;
• cleaner content presentation;
• article metadata presentation;
• accessible and semantic navigation;
• improved pagination;
• SEO assistance inside the story editor;
• slug assistance;
• better presentation of forum content;
• theme-level SEO helpers for the Forum plugin;
• reduced dependence on unnecessary third-party scripts;
• improved accessibility and keyboard navigation.

The article editor also provides SEO diagnostics intended to help authors identify common content issues before publication.

For older Geeklog sites that have accumulated years of valuable content, this makes Eclipse particularly interesting: instead of rebuilding the entire website, it becomes possible to improve the presentation and technical environment surrounding that existing content.

Plugin integration is becoming a core part of Eclipse

Eclipse 1.1.0 also goes beyond the Geeklog core.

The theme can provide dedicated presentation rules, templates and interface components for plugins so that their pages become part of the same coherent experience.

The Forum plugin currently receives the most extensive integration.

Eclipse includes dedicated Forum templates, responsive styling, blocks, topic and category presentation, moderation views, user preferences and theme-level SEO helpers.

Static Pages are also directly supported with dedicated public and administration templates, including improved editor presentation.

The Menu plugin integrates with Eclipse's navigation system, including hierarchical menus and responsive navigation.

Eclipse 1.1.0 also already contains interface support for capabilities being developed in other Geeklog plugins.

The upcoming version of the Monitor plugin is already anticipated inside Eclipse, allowing monitoring and site-status information to fit naturally into the modern administration workspace when those capabilities become available.

The same approach is being used with the Maps and Documents plugins. Eclipse already includes presentation and integration work intended to support these plugins as their modernized versions evolve.

This is an important direction for the project: Eclipse is becoming more than a standalone theme. It is progressively providing a shared presentation layer for a modern Geeklog ecosystem, where the core and plugins can offer a consistent responsive interface.

That also means future plugin improvements can be introduced without forcing every plugin to reinvent its complete visual layer independently.

Theme Studio becomes more mature

Theme Studio was already present in the previous Eclipse concept, but version 1.1.0 turns it into a much more complete and reliable administration tool.

It has been refined to better support real-world use, with improved persistence, safer update handling and stronger recovery options.

Theme Studio includes:

• palette selection, including the new Vivid Red palette;
• interface and layout settings;
• footer configuration;
• live preview;
• custom CSS support;
• configuration import and export;
• history;
• rollback;
• ZIP-based theme updates.

Settings are stored in protected JSON files outside the normal public theme directory.

The update process has also been hardened with package validation, automatic backups, integrity checks and targeted cache clearing.

The result is not a new Theme Studio, but a more mature version of the original idea, designed to make Eclipse easier and safer to customize and maintain over time.

A better editorial workflow

Eclipse 1.1.0 also pays attention to the people publishing the content.

The story editor includes improvements such as SEO assistance, slug helpers, local draft recovery, focus mode and protection against accidentally leaving a page with unsaved changes.

The aim is simple: make Geeklog more comfortable for day-to-day publishing while preserving its native editorial workflow.

Tested on Geeklog 2.1.1 and 2.2.2

One of the main goals of Eclipse is to help modernize existing Geeklog installations, not only new ones.

Version 1.1.0 has therefore been tested successfully on both:

• Geeklog 2.1.1
• Geeklog 2.2.2

Compatibility code is used only where the two Geeklog generations require different handling.

PHP 5.6 remains the parsing compatibility baseline for legacy installations, although using a currently maintained PHP version is strongly recommended for production sites.

This makes Eclipse especially useful for the large number of Geeklog sites that still contain valuable archives, discussions and community content but need a more modern interface.

From concept to something you can actually test

Eclipse 1.1.0 represents the transition from an idea to a real working theme.

It is already being used to test modernization approaches for public pages, administration, editors, forums, static pages and plugin presentation.

It also provides a foundation for the next generation of Geeklog plugins, with integrations already prepared for Monitor, Maps and Documents.

The next step is now community testing.

If you still operate a Geeklog website, especially an older one, Eclipse offers an opportunity to see how much of the existing site can be modernized without abandoning the CMS or rewriting years of content.

Testing on different Geeklog configurations, plugins, browsers and mobile devices will also help identify where the next improvements should be made.

Feedback, bug reports, screenshots and contributions are therefore very welcome.

Try Eclipse, compare it with your current theme, test your existing content and plugins, and help define what a modern Geeklog experience should look like.

Eclipse on GitHub:
https://github.com/hostellerie/eclipse