01 · Overview

Executive summary

The Drupal 7 site was configured with a simplified publishing workflow. The former Article type is shown as Content; the authoring form uses Body text and an optional Screenshot image upload, and the navigation includes an Add New Content link. The Content teaser display was changed so front page entries include the full body and image.

The pfSense dashboard screenshot supplied by the site owner was uploaded and published as node 3. Node 1 was later replaced temporarily by a list of published Content posts at the owner’s request. After the owner said UNDO, the original SEND CODE page was restored from its saved revision.

02 · Configuration inventory

Current site state

This report does not contain the Drupal login password.

03 · Content model

Configure the Content type and entry form

Rename and simplify the content type

1. Open Structure → Content types and edit Article.
2. Change its display name to Content; retain machine name article. Save.
3. In Manage fields, retain Body as the main text editor. Configure Automatic Nodetitles for this type to generate titles without showing a title field.

Install and configure automatic titles

Automatic Nodetitles was installed from the Drupal project source and enabled. Its Content/Article settings hide manual title entry and generate node titles. This is a legacy Drupal 7 module version; verify compatibility and support status before migrating or updating it.

Add a screenshot field

1. Go to Structure → Content types → Content → Manage fields.
2. Under Add new field, enter label Screenshot; choose the Image field type and Image widget; save.
3. Keep Public files only for content meant to be public. Save Field settings.
4. Keep the field optional and allowed extensions png, gif, jpg, jpeg; save the field instance settings.

04 · Navigation

Add the Add New Content menu button

1. Open Structure → Menus → Main menu → Add link.
2. Set link title to Add New Content and path to node/add/article; enable and save the link.
3. Open Structure → Blocks and place the Main menu block in a visible region such as Header; save block placement.
4. Open the page and verify the link goes to the Content creation form.

If the theme’s built-in Main menu and a separate Main menu block are both visible, the link may appear twice. Remove one block placement if only a single button is wanted.

05 · Publishing workflow

Create and publish a Content post

1. Choose Add New Content or open Content → Add content → Content.
2. Write the post in Body. Example caption used for node 3: “pfSense Status Dashboard — system information, interface status and traffic graphs.”
3. Under Screenshot, select a PNG/JPG/GIF and press Upload. Wait for Drupal to show the file name, size, preview, and Remove control.
4. Review Publishing options. Leave Published checked to make the item live; choose whether to promote it to the front page.
5. Press Save. Confirm the success message and inspect the node page.

Completed example: node 3 contains the caption and uploaded dashboard image.

06 · Full post display

Show full Content posts on the front page

The site’s Default front page field is blank in Site information, so Drupal’s default node feed is shown at /automation/. At the time of inspection, the “Number of posts on front page” setting was 10.

1. Open Structure → Content types → Content → Manage display.
2. Select the Teaser view mode, used by the front page overview.
3. Set Body formatter to Default instead of Summary or trimmed. This removes the 600-character trim.
4. Set Screenshot formatter to Image; the saved option was Original image.
5. Save. Visit /automation/ and verify the post body and image display in the feed.

Drupal’s default feed lists nodes promoted to the front page. The Content teaser formatting applies to the Article/Content type.

07 · Revision recovery

Node 1 replacement and undo

At the site owner’s request, Basic page node 1 (“SEND CODE”) was temporarily edited to show published Content posts. A revision was saved first, and the page was removed from the front page feed to prevent duplication. The owner later requested UNDO. Drupal restored the original revision from 26 October 2026, 15:48, creating a new current revision and keeping later revisions in history.

1. Open Content → Find content, locate SEND CODE, and choose Revisions (or visit ?q=node/1/revisions).
2. Identify the desired prior version by timestamp and revision log. Choose revert.
3. On Drupal’s confirmation page, press Revert.
4. Open ?q=node/1 and verify the page title and HSSP interface.

The temporary listing was not left active. Current node 1 is SEND CODE, and the listing revision is retained for reference.

<?php $query = db_select('node', 'n'); $query->fields('n', array('nid')); $query->condition('n.type', 'article'); $query->condition('n.status', NODE_PUBLISHED); $query->orderBy('n.created', 'DESC'); $result = $query->execute(); $ids = $result->fetchCol(); $posts = node_load_multiple($ids); foreach ($posts as $post) { $render_array = node_view($post, 'teaser'); print drupal_render($render_array); } ?>

08 · Verification

Acceptance checks

09 · Operations

Security and maintenance

• Do not place passwords, API keys, private network details, or administrator-only diagnostics in public post text or images.
• Use Public files only for assets intended for public access.
• The Drupal 10 upgrade was discussed but not done. Plan a migration separately and take a full database/files backup first.
• The site already has the PHP filter enabled, and the original node 1 used PHP to operate the HSSP interface. Restrict PHP-format editing to trusted administrators; permission to edit PHP content can enable server-side code execution.
• Drupal content revisions help recover node edits, but they are not a substitute for a full site backup.

10 · Documentation scope

Source and coverage notes

This report uses the verified Drupal screens and actions from the conversation: Manage Fields, Manage Display, Site information, Modules, the new-content form, node 3, node 1 edit, and revision history. The supplied MKV is 1 hour 41 minutes long; the Movavi preview timed out during screen capture, so the report does not claim independent visual review of the video.

Drupal.org describes Views as a contributed module for constructing lists and states that the Drupal 7 release requires Chaos Tool Suite. Views was not enabled when the site module list was inspected. References: Views for Drupal 7 · Drupal 7 Views release information.

This is one self-contained HTML file. Styles, navigation, expandable code note, and print layout are embedded; no external assets or JavaScript libraries are required.