|
|
|
Feedback ID:
|
14
|
Status:
|
Closed
|
|
Product:
|
News Articles
|
Implemented?
|
Yes
|
|
Created On:
|
7/22/2005
|
Created By:
|
Bradley Molzen
|
|
Details:
|
News Articles still needs some updating to a more generic "DNN Style" of skinning for the default look/feel of modules that should be able to fit into any website skin.
For Example, the "categories" tab still has the big green bar in it, but isn't templatable. An admin would have to modify css before releasing the module.
Just being picky. :-)
|
|
|
 By
Jack Hoelz
@
7/23/2005
|
|
|
|
By
Dana Janssen
@
7/28/2005
|
|
Shouldn't you consider the CSS stylesheets as part of a template? Even the DNN 'template' pages call upon stylesheets to actually define elements. I agree that News Articles could be organized in an easier to modify fashion, but I found little difference between skinning for News Articles and skinning for DNN.
|
|
|
|
By
Dharmesh Shah
@
7/28/2005
|
|
I would also suggest that the "default" look-and-feel for the modules is more "neutral" in tone and color-scheme (for example, using gray). As it stands, a large majority of users would need to make some changes to the CSS files or templates before the module could be deployed. It would be nicer to have something that could be implemented immediately (and then tweaked later).
|
|
|
|
By
p speth
@
8/17/2005
|
These would be on my wish list for all Module developers.
1> Style sheets should never be overwritten by an upgrade.
This could be handled by keeping the style sheets separate by default.
They could also have a version number appended to the name.
2> Elements in a module (like links) should be assigned unique classes so
their styles can be modified via CSS without affecting the rest of the site.
3> With Each upgrade a document should be included that documents the modules
unique styles, and provides a version history for these.
|
|
|
|
By
Darren Neese
@
8/28/2005
|
|
sounds like a good suggestion
|
|
|
|
By
Dharmesh Shah
@
8/30/2005
|
|
I also agree that there should be a way to change the CSS that survives an upgrade (this way, upgrades can be applied easily without worrying about changes to the color/style being overwritten).
|
|
|
|
By
ray chance
@
12/5/2005
|
|
yes - I hate green anyway
|
|
|
|
By
Jason Koskimaki
@
12/31/2005
|
I would like to see a default template system modularized. So it is it's own separate dll so that all the components use this single template system rather than have copies for each one.
Also, with this, a developer who wants to add templates to his own module could directly download and use Scott's template module and API rather than searching for and copying all the needed code.
|
|
|
|
By
Robert Axford
@
2/10/2006
|
Absolutely.
All modules by all developers should be designed to display nicely in a simple manner using the dnn default.css rather than any custom one.
All too many modules come pre-skinned in an innappropriate manner.
I believe DNN itself should also be designed like that... to display in just a simple plain style rather than those awful skins it comes with. It's much harder to change from an ugly complicated skin than it is to change from something plain and simple.
|
|
|
|
By
Michael Flanakin
@
7/3/2006
|
pspeth,
1. You shouldn't modify the CSS that comes with a product. Instead, override it in your own CSS file (i.e. portal.css). This will ensure you don't lose content with updates. Sometimes these updates are necessary.
2. Actually, the links should theoretically try to integrate as much as possible with the existing DNN CSS setup as possible. This helps ensure there's no need to override custom settings to get thigns to look like DNN expects.
3. Couldn't agree with you more.
|
|
|
|
By
Rob Poretti
@
11/17/2006
|
Yes. Please sub-class common DNN classes where you can and remove all hard wired stylings.
Thank-you!
|
|
|
|
By
Alex Shirley
@
11/22/2006
|
Yes I would like to under search facility
a) Display the summary field as well as the title after a search.
b) Change the colour of the footer.
Alex
|
|
|
|
By
Scott McCulloch
@
9/4/2008
|
The latest release has templating for search and a very generic layout for the archives page (the replacement for syndication + categories). The new "Standard" template should be a much better fit for all skins.
Closing item.
|
|
|
|
|
|
|
|