Dn-css - Revision history

FairyFighter: /* Colors */

2021-02-24T20:09:34Z

‎Colors

2021-02-24T20:08:44Z

‎Colors

2021-02-24T20:06:19Z

‎Colors

2021-02-24T20:05:08Z

‎Templating

2021-02-24T20:04:16Z

2021-02-24T20:02:54Z

‎Templating

2021-02-24T19:40:19Z

‎Templating

2021-02-24T19:40:05Z

‎Templating

2021-02-23T22:12:28Z

2021-02-23T22:00:25Z

‎3

@@ Line 63: / Line 63: @@
 }}
-In my opinion, to make it even ''more'' flexible/dynamic, numbers should be replaced by variables like {{color}}, {{background-color}} which will contain specific number.
+In my opinion, to make it even ''more'' flexible/dynamic, numbers should be replaced by variables like <nowiki>{{color}}</nowiki>,<nowiki> {{background-color}}</nowiki> which will contain specific number.
 == Tabels==

@@ Line 62: / Line 62: @@
 |8=dn-MR3
 }}
 == Tabels==

@@ Line 3: / Line 3: @@
 There for I would like to suggest few high level regions and reach mutual agreement on, that we all would support.
 ==Colors==
-According to many webdesigners most of websites should be able to achive good readability and modern look with usage of 5 colors only. Mostly 4 colors in same range and one as eye-catcher. I propose first 8 colors, more for the range allocations than anything else.
+According to many web designers most of websites should be able to achieve good readability and modern look with usage of 5 colors only. Mostly 4 colors in same range and one as eye-catcher. I propose first 8 colors, more for the range allocations than anything else. Pallets below are for demonstrations purposes only.
 * [[dn-TK]]
 {{dn-colors-table

@@ Line 72: / Line 72: @@
 *** Template/sub-1/sub-A
 ** Template/sub-2
 Here some of my interpretations of staged templating:

@@ Line 68: / Line 68: @@
 We all know what template is. But do we know when is a template a good template? Friendly for contributors and as functional as it gets? Example below demonstrates my idea of templating in stages. Templet call should be as straight forward as possible. This can be best seen in '''button 4'''.
 How to keep templates easy to use? I suggest using templates containing subtemplates.
-* Template
+* Template                       : this is template that Contributors will use
-** Template/sub-1
+** Template/sub-1            : these are sub templates with more complicated code
 *** Template/sub-1/sub-A
 ** Template/sub-2

@@ Line 67: / Line 67: @@
 == Templating==
 We all know what template is. But do we know when is a template a good template? Friendly for contributors and as functional as it gets? Example below demonstrates my idea of templating in stages. Templet call should be as straight forward as possible. This can be best seen in '''button 4'''.
 Here some of my interpretations of staged templating:
   No HTML buttons, all in CSS.

@@ Line 111: / Line 111: @@
 |Link4=DDDD
 }}<br/>
+----
 {{:dn-button-1|text=[[dn-css-2| NEXT]]}}

← Older revision		Revision as of 22:12, 23 February 2021
Line 112:		Line 112:
	}}<br/>		}}<br/>

−	~~==Page elements==~~	+	[[dn-css-2\| NEXT]]
−	~~A nice concept of separated text in a box! Lets make it a bit more modern:~~
−	~~===Paragraph===~~
−	~~Biggest problem I see here horizontal line. Not line but its color. If we would use standard wiki markup we can not change its color. It appears at highest level.. Then it is there no more:~~
−	~~==1==~~
−	~~111111~~
−	~~===2===~~
−	~~2222222~~
−	~~====3====~~
−	~~333333333~~
−
−	~~That's why I would consider using an alternative approach.~~
−
−	~~{{:~~dn-~~paragraph~~
−	~~\|Header=Header~~
−	~~\|Content=Some text~~
−	\|~~Pallete=RT~~
−	}}
−
−	~~===Table===~~
−	~~No HTML table here, only CSS:~~
−
−	~~===Text box===~~
−	~~===Article===~~
−	~~===Navigation===~~
−	~~===Page box===~~
−
−	~~==Layouts==~~
−	~~===Main Page===~~
−	~~This page should be attractive enough to invite people to read its content as informative as possible.~~
−	* Proposal A
−	* Proposal B

@@ Line 128: / Line 128: @@
 |Header=Header
 |Content=Some text
-|Pallete=
+|Pallete=RT
 }}