Bold editorial · Notes for Eric
Close
A stronger presentation over the same Rails workflow.
This
revision replaces the previous conservative concepts with one focused
editorial homepage and a practical article page. All data, rights, dates
and assets are sample material.
Presentation change
Implementation pattern
Phase 1 boundary
Oversized editorial masthead
System serif type, custom CSS, top navbar.
No new backend behavior.
Asymmetric feature and two supporting stories
Bootstrap 4 row / col-lg-8 / col-lg-4; shared card partials.
Static or existing featured records. No carousel or recommendation
engine.
Topic links and library filters
Bootstrap 4 buttons, form-control, GET query/category parameters.
Reuse current browse/search capability; assess any missing feature
separately.
Article with dedicated asset panel
Article partial, card/card-header/card-body, btn-block, anchor
links.
Current content service, sessions and download endpoints.
Feature Impact branding
The actual public FI wordmark is embedded offline. Its cyan
#05E3EE
and charcoal
#211F20
were sampled from
the RGB logo. White and light-gray surfaces replace the green/cream
palette. Dark teal
#007781
is a UI derivative for readable
links and accent text; it is not represented as an official brand
specification. Cyan-filled buttons use dark text for contrast. Eric can
adjust these three CSS tokens if an approved brand guide specifies
different values.
Public Feature Impact RGB logo reference
Compatible with AdminLTE 3 / Bootstrap 4
The offline file embeds AdminLTE 3.2.0 CSS, including Bootstrap 4.6.1
styling, with a separate custom presentation layer at the end. The
supporting
bold-editorial.css
file contains the same new
styles for reference. No Bootstrap 5, AdminLTE 4, new font service or
new UI plugin is required.
Retain Eric’s current Rails asset pipeline; do not import a second copy
of Bootstrap. Existing AdminLTE 3 navbar, card, form and button classes
remain usable. This prototype uses vanilla JavaScript and native
dialogs. In production, use the existing Bootstrap 4 modal component if
that is the current pattern. The layout uses CSS Grid/Flexbox and can be
translated to Bootstrap 4 columns. Framework JavaScript is not loaded
here.
Rails partials and data
Scope presentation overrides to an Editors-specific layout wrapper in
production so the ERP and reporting portal keep their own styling. The
standalone prototype styles the whole document.
Shared partials: brand/navigation, featured article, supporting
teaser, browse card, article metadata/body, assets, usage guidance.
Content fields: current ID/slug, title, summary, category, publish
date, image variants, body, filename/MIME type, caption, credit and
permissions. Do not add new ERP fields solely for this design.
Feature labels and placement are curated presentation, not an inferred
new taxonomy. Replace fixed sample IDs with existing featured records
or a small configuration.
Keep existing article URLs/bookmarks or redirect them. Query and
category filtering should use the existing Rails scope and server-side
pagination.
Render sanitized article HTML. Use production image variants with real
dimensions and accurate alt text. Sample imagery in this file is
review resolution.
Access and downloads
The demo assumes public browsing and editor-only downloads. Retain the
actual current access policy. The login dialog collects no credentials
and creates no real account. Use existing Rails sessions, recovery and
permissions. Authorize every download on the server and preserve
existing download reporting. Client-side button visibility is not
authorization.
The sample text and JPEG download buttons create local files. They
demonstrate access and file delivery only. Production file formats,
print-ready images, expiry/embargo rules and rights must come from the
ERP. No ZIP generator, document converter or new tracking subsystem is
proposed.
Responsive behavior
Desktop: large masthead, two-column feature, three-column library and a
right-hand download panel. Tablet/mobile: the feature and cards stack;
the article heading comes first, followed by downloads and the article
body. Article, Downloads and Usage links provide direct navigation.
Controls wrap instead of creating horizontal overflow.
Keep Phase 1 contained
Visual work: typography, cream/forest/rust palette, image proportions,
spacing, layout and clearer labels. Reuse browse, categories, search,
content access, login and download services already built. No saved
lists, personalized content, new taxonomy, new integrations, WordPress
work or Story Kits.
Reference and sample content
Eric’s Rails POC supplied the white brand/account header, seasonal
feature and New Content grid. This revision keeps those jobs and gives
them a stronger editorial hierarchy. The article detail layout is
proposed because no detail screenshot was supplied. Photos are reused
from existing project prototype assets, not newly cleared publication
images. Replace sample copy, credits and rights before launch.
AdminLTE 3.2 dependencies
·
Bootstrap 4.6 grid
