localgovdrupal
Show published/ last updated dates on pages
PaulB raised this at Product Group and in Slack
Is there anything on the board about adding published/last updated dates to webpages? Is this feature already available?
Stephen:
It's easy enough to add this sort of functionality; just need to adjust the display options One thing we can do is make sure they display nicely when enabled
To do
- Discuss need at content group
- Decide what needs to be shown and where on the page
- Decide whether dates are shown on every page or selected ones (Paul suggests selected ones)
Previously covered:
https://localgovdrupal.slack.com/archives/C020SJRQX2M/p1715595382053479 https://github.com/localgovdrupal/localgov_project/issues/160
@willguv I've an updated PR for this here: https://github.com/localgovdrupal/localgov/pull/735
Nice one Mark, can you grab a couple of screenshots or let me know the composer command to install this?
Here's a screenshot
There's more details in the PR description: https://github.com/localgovdrupal/localgov/pull/735#issue-2375729488
It doesn't appear anywhere. It's a block but you'll need to decide where you want to place it yourself.
You can go to Admin > Structure > Blocks and place it in any region
It will need to be optional as we don't know if council web teams have put sensitive or information they may not want to be public.
@andybroomfield That's the handy thing about this being a block, councils can decide what pages/content types they want it on.
I guess we could create a custom field either that would be shown to the public listing updates and leave the revisions field for just internal use.
Reading the original issue, perhaps we just want to add a configuration option to enable this per content type.
For example,
Last updated: 5th May 2024
or including time? 17:21 5th May 2024
But probably only on certain content types.
Questions:
- is this a theme setting or a non-theme site-wide setting? Good question!
- Do we want to set the time / date display optionally? Yes!
- Do we want this to also be optional per node? Yes!
@finnlewis @markconroy @andybroomfield feels like this is a common need around showing the provenance of info, but it won't be needed that often.
If this is true, we could provide something like:
- a sub module that can be installed, or part of core that's switched off
- once enabled, there's a setting at the node level on specific content types, maybe those showing important service or policy info eg Service pages, Guides, Step by Steps, Publications
I can ask the Content Group about if you like?
I can ask the Content Group about if you like?
I think that's a good idea. To add it to a few content types will probably mean recreating that field in each of those modules which will take a bit of coordinating, so ideally we'd like to get the request right first time.
