Feature #39692
content design for buzz integration
| Status: | Closed | Start date: | 2012-08-10 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Ben van 't Ende | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
buzz.typo3.org will be moved to typo3.org hopefully in a code sprint at the end of this year. we need a design for the content part before we can do such migration
History
Updated by Denis Zastanceanu 7 months ago
- File buzz.jpg added
Updated by Denis Zastanceanu 7 months ago
- Status changed from New to Needs Feedback
- Assignee changed from Denis Zastanceanu to Ben van 't Ende
- % Done changed from 0 to 90
check it out.
Updated by Ben van 't Ende 7 months ago
the list view looks fine to me, but we would still need a single view. the thing i always thought about buzz as it is now that it just does not look like a blog.
Updated by Denis Zastanceanu 7 months ago
Ben van 't Ende wrote:
the list view looks fine to me, but we would still need a single view. the thing i always thought about buzz as it is now that it just does not look like a blog.
Well, I thought it should look like any single content page (using the smae content elemetns):
http://typo3.org/news/article/typo3-maintenance-guide/ or
http://typo3.org/news/article/typo3-phoenix-becomes-iks-early-adaptor/
If you have another idea, could you please get into more detail?
Updated by Robert Zierhofer 5 months ago
- Status changed from Needs Feedback to Closed
- % Done changed from 90 to 100
Closed by discussion