Maintain examples, every page #

Change lists, banners, menus and campaigns week by week, and recover from mistakes.

1. Swap one article in a hand-picked list: Remove an item from a manual collection and add another in its place, in the Layouts editor.
2. Reorder a hand-picked list: Drag the items of a manual collection into a new order; check the order after publishing.
3. Point a dynamic list at another section: Change the Parent location of a dynamic collection; the list fills from the new section at once.
4. Show more items in a list: Offset & number of items (dynamic collections) or more manual items; Enable pagination for long lists.
5. Replace the hero image: Change the Image URL and Image alt text of the Hero block; or upload a new image to the content the template reads.
6. Change a button's text and target: Edit Text and link of a Button / Link block, or Link text and Link URL of a Hero.
7. Rename a header menu item: The header menu prints the node's name: rename the page in the content tree and publish.
8. Take an item out of the header menu: Delete its line from MainMenuID[] (administration) or exp:ini rem (console), then Template & content.
9. Move a header menu item to the front: Reorder the lines of MainMenuID[] in the administration, or exp:ini clear and add in the new order.
10. Add a link to the footer's second line: Create a Menu item in Media > Configuration > Footer links with Title and Item URL; no cache clear.
11. Hide a footer link for a while: Hide the Menu item in the content tree; the footer lists only what the visitor may see.
12. Change a social profile address: Edit the matching field (facebook, twitter, instagram, linkedin) of the site info object.
13. Swap a seasonal layout by hand: Two mappings for the same page, the seasonal one with a higher priority: tick or untick Enabled to switch.
14. Swap a seasonal layout by date: A Time condition (from, to) on the seasonal mapping switches it at its start and end without anyone clicking.
15. Put up a temporary notice: An Alert block in the page's post_header zone, removed again after the event.
16. Rotate the featured item of a grid: In a grid_featured list, the first item is the large one: drag another item to the top.
17. Change the number of columns of a grid: Number of columns on the Design tab: 2, 3, 4 or 6.
18. Change a list from grid to list: View type on the Design tab; before explayouts_ui_api 1.3.29 the change was stored only with the next change of another field.
19. Give a section a background color: Set background color on the Design tab; the wrapper gets bg-color-<color>.
20. Adjust the spacing of a section: Use vertical whitespace on top and bottom (Design tab) instead of Spacer blocks.
21. Throw away a draft that went wrong: Discard removes the draft; the published layout is untouched.
22. Undo a published layout change: Import the export taken before the change with --strategy=overwrite --publish; the import purges the page cache itself.
23. Export layouts every week: A scheduled exp:layouts export --all keeps a history of the layouts.
24. Find forgotten drafts: exp:layouts list --drafts lists every open draft; open each and publish or discard.
25. A change did not show: Draft not published, linked zone, another layout, settings in the wrong file, compiled template, page cache, Velocity: the ten checks.
26. A new section joins the header menu: Publish the section page, find its node ID, add it to MainMenuID[], clear Template & content.
27. Retire a campaign page: Disable its mapping, keep the layout for next year, hide or archive the page.
28. Reuse last year's campaign: Import last year's export as a copy (--strategy=copy), change the texts, map it.
29. Keep block texts in two languages: Texts typed into blocks belong to the layout; for a second language, a layout per siteaccess, or text from translated content.
30. Check the links typed into blocks: Links typed into Button, Hero, Card and Image blocks do not follow moved pages; check them after restructuring.
31. Update the privacy or cookie policy: Edit the article (Privacy Policy, node 90; Cookie Policy, node 91); their layout and footer links follow.
32. A monthly look at the caches: exp:cache list shows every cache; look for growth and make sure page caching still works.
33. When an editor changed the shared layout by mistake: A change to Header / Footer or Prefooter shows on many pages; roll it back from the last export.
34. A new recipe appears in the lists: Publish the recipe below Recipes; dynamic lists show it, manual lists need it added.
35. Keep the site documentation current: After each change of menus, mappings or overrides, update the site guide written at planning time.

Related pages #

• Life-cycle examples
• Two ways to build
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.