Changing home page "What's new" item shouldn't require a code rollout or cherry pick
Bug #129943 reported by
Matthew Revell
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Francis J. Lacoste |
Bug Description
Changing or adding a news item in Launchpad's home page "What's new" section currently requires a code roll out or a cherry pick.
This means that a developer and senior team member (to give permission) must be involved in what is otherwise a simple communications task.
My suggested solution is:
1. I create a new category on the Launchpad News blog - e.g. "Home page".
2. The "What's new" section draws its items from the headlines in that blog category.
3. We link the headlines to the full blog post.
4. We add a "Read the Launchpad News blog" link at the bottom of the "What's new" list.
Related branches
lp:~flacoste/launchpad/bug-129943
- Matthew Revell (community): Approve (acceptance)
- Robert Collins (community): Approve
-
Diff: 633 lines (+388/-67)11 files modifiedconfigs/development/launchpad.conf (+1/-1)
configs/testrunner/launchpad-lazr.conf (+3/-0)
lib/canonical/config/schema-lazr.conf (+5/-0)
lib/canonical/launchpad/ftests/googlesearches/blog.launchpad.net-feed.xml (+266/-0)
lib/canonical/launchpad/ftests/googlesearches/mapping.txt (+2/-0)
lib/lp/app/browser/root.py (+47/-9)
lib/lp/app/browser/tests/test_launchpadroot.py (+4/-0)
lib/lp/app/stories/launchpad-root/front-pages.txt (+45/-30)
lib/lp/app/templates/root-index.pt (+13/-27)
setup.py (+1/-0)
versions.cfg (+1/-0)
Changed in launchpad: | |
status: | New → Confirmed |
Changed in launchpad: | |
milestone: | 1.1.11 → none |
tags: |
added: qa-ok removed: qa-needstesting |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-foundations: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I agree we need a better way to do this and it would behoove us to keep the front page in sync with our other communication mediums such as the news blog and help.lp.net.
My first thought for this is to add RSS functionality that draws from a special category on the blog (that would enable us to post something only to the LP front page, or the LP front page and the visible blog page. This also would allow us to notify the Planet with no real effort should we want this) but also gracefully handles the case where the blog is offline for some reason.
Keeping our informational areas (blog, LP front page, wiki) in sync and sourced from as few places as possible will make the management of that type of communications activity much easier.