Feed journals should show the source

[msilverstar]

Title:
Feed journals should show the source

Area:
user interface, feeds

Summary:
Put the feed source link into the feed journal view for clarity.

Description:
New feeds and broken feeds have very blank journal pages, which are a bit off-putting. Even feeds with lots of content can be confusing, depending on the format of that content. Right now the source information is only on the profile page. Because there's no original content in the journals, showing the feed source right there in the journal view would make them easier to understand.

Poll #9374 Feed journals should show the source

Open to: Registered Users, detailed results viewable to: All, participants: 57

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
34 (59.6%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
2 (3.5%)

(I have no opinion)
21 (36.8%)

(Other: please comment)
0 (0.0%)

make list of allowable HTML easier to get to

[thnidu]

Title:
make list of allowable HTML easier to get to

Area:
entries and comments

Summary:
Make it easier for the user to see what HTML tags are OK to use, *while they are writing or editing a post or comment*.

Description:
In order to check "can I use this HTML tag?" or "What's the name of that tag again?", a user who is composing or editing a post can scroll down to the list given below the post... unless it's a DW-specific tag. For that, they have to (as far as I can tell)
1. open up their home page in a new tab
2. click on "Help/FAQ"
3. open one of three different pages listed there (here in the order they appear in):
- a. What Dreamwidth-specific markup/HTML tags can I use? (a short list of those three tags, with links to further information about them such as available attribute)
- b. What HTML tags can I use on Dreamwidth? (a list with detailed examples)
- c. What HTML can I use in my entry? (a simple compact list of the allowed HTML tags, plus a link to page "a" above (Dreamwidth-specific markup/HTML tags)

Two suggestions:
1. After the list of general HTML tags that you have below the composition pane for a *post*, add a list of DW's local HTML tags, with something like "Dreamwidth-specific tags:".
2. Also,
- Make a separate page with those two lists -- not just allowable general HTML and a link the user has to follow to see the DW-specific list. Include
-- the "learn more" links that you already have on "What Dreamwidth-specific markup/HTML tags can I use?",
-- and a link to the detailed list with examples that is "What HTML tags can I use on Dreamwidth?"
- Put a link to that page in the *Reply* area, maybe under the composition pane just to the right of "Check spelling during preview", something like this: [Allowable HTML]. The link should open on a separate page.

I've been hand-coding HTML for decades, but even so I appreciate having a list of the HTML that DW accepts at the bottom of the entry window. And I would appreciate even more having an easily accessible list of your site-specific HTML tags, which I often do not remember; for example, exactly how to add a userhead and link to the name of a user on another site.

Poll #9373 make list of allowable HTML easier to get to

Open to: Registered Users, detailed results viewable to: All, participants: 68

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
57 (83.8%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
11 (16.2%)

(Other: please comment)
0 (0.0%)