#stylesheet — Public Fediverse posts

#Development #Launches
CSS-DOS · An entire ‘80s PC implemented in pure CSS https://ilo.im/16epfr

_____
#CSS #Stylesheet #PC #MSDOS #Windows #DOOM #WebDev #Frontend

#Development #Launches
CSS-DOS · An entire ‘80s PC implemented in pure CSS https://ilo.im/16epfr

_____
#CSS #Stylesheet #PC #MSDOS #Windows #DOOM #WebDev #Frontend

#Development #Launches
CSS-DOS · An entire ‘80s PC implemented in pure CSS https://ilo.im/16epfr

_____
#CSS #Stylesheet #PC #MSDOS #Windows #DOOM #WebDev #Frontend

#Development #Launches
CSS-DOS · An entire ‘80s PC implemented in pure CSS https://ilo.im/16epfr

_____
#CSS #Stylesheet #PC #MSDOS #Windows #DOOM #WebDev #Frontend

@jschauma
I've just looked at my first site. Started 1 January 1998. Abandoned at some point after 30 March 2000, when the "Whats New" page announced "Reworked all source (html) files for the site. They are now HTML4.0 compliant and use a style sheet."

The site documented all the tricks and tips I could offer on the "Recorder" accessory found in Windows v3.11 for Workgroups.

Tried running it discover that back then Internet Explorer must have been case insensitive. My file naming style was somewhat inconsistent.

If there's unbelievable interest I'll correct the mixed case file names and upload it somewhere.

#html #stylesheet #windows #workgroups #recorder #internetexplorer #history #www

@jschauma
I've just looked at my first site. Started 1 January 1998. Abandoned at some point after 30 March 2000, when the "Whats New" page announced "Reworked all source (html) files for the site. They are now HTML4.0 compliant and use a style sheet."

The site documented all the tricks and tips I could offer on the "Recorder" accessory found in Windows v3.11 for Workgroups.

Tried running it discover that back then Internet Explorer must have been case insensitive. My file naming style was somewhat inconsistent.

If there's unbelievable interest I'll correct the mixed case file names and upload it somewhere.

#html #stylesheet #windows #workgroups #recorder #internetexplorer #history #www

@jschauma
I've just looked at my first site. Started 1 January 1998. Abandoned at some point after 30 March 2000, when the "Whats New" page announced "Reworked all source (html) files for the site. They are now HTML4.0 compliant and use a style sheet."

The site documented all the tricks and tips I could offer on the "Recorder" accessory found in Windows v3.11 for Workgroups.

Tried running it discover that back then Internet Explorer must have been case insensitive. My file naming style was somewhat inconsistent.

If there's unbelievable interest I'll correct the mixed case file names and upload it somewhere.

#html #stylesheet #windows #workgroups #recorder #internetexplorer #history #www

@jschauma
I've just looked at my first site. Started 1 January 1998. Abandoned at some point after 30 March 2000, when the "Whats New" page announced "Reworked all source (html) files for the site. They are now HTML4.0 compliant and use a style sheet."

The site documented all the tricks and tips I could offer on the "Recorder" accessory found in Windows v3.11 for Workgroups.

Tried running it discover that back then Internet Explorer must have been case insensitive. My file naming style was somewhat inconsistent.

If there's unbelievable interest I'll correct the mixed case file names and upload it somewhere.

#html #stylesheet #windows #workgroups #recorder #internetexplorer #history #www

@jschauma
I've just looked at my first site. Started 1 January 1998. Abandoned at some point after 30 March 2000, when the "Whats New" page announced "Reworked all source (html) files for the site. They are now HTML4.0 compliant and use a style sheet."

The site documented all the tricks and tips I could offer on the "Recorder" accessory found in Windows v3.11 for Workgroups.

Tried running it discover that back then Internet Explorer must have been case insensitive. My file naming style was somewhat inconsistent.

If there's unbelievable interest I'll correct the mixed case file names and upload it somewhere.

#html #stylesheet #windows #workgroups #recorder #internetexplorer #history #www

@neve
Do I use any tools to keep track of plot lines, character details, research, future ideas?

I do my initial drafting in Scrivener, so I keep all my related research materials there. Character details are in a Style Sheet--a carryover from when I was a copyeditor.

Future ideas live in a folder on the laptop where I drop info, plus a blank book I carry around in case inspiration strikes.

#Writephant #scrivener #stylesheet #inspiration #futureideas

@neve
Do I use any tools to keep track of plot lines, character details, research, future ideas?

I do my initial drafting in Scrivener, so I keep all my related research materials there. Character details are in a Style Sheet--a carryover from when I was a copyeditor.

Future ideas live in a folder on the laptop where I drop info, plus a blank book I carry around in case inspiration strikes.

#Writephant #scrivener #stylesheet #inspiration #futureideas

@neve
Do I use any tools to keep track of plot lines, character details, research, future ideas?

I do my initial drafting in Scrivener, so I keep all my related research materials there. Character details are in a Style Sheet--a carryover from when I was a copyeditor.

Future ideas live in a folder on the laptop where I drop info, plus a blank book I carry around in case inspiration strikes.

#Writephant #scrivener #stylesheet #inspiration #futureideas

@neve
Do I use any tools to keep track of plot lines, character details, research, future ideas?

I do my initial drafting in Scrivener, so I keep all my related research materials there. Character details are in a Style Sheet--a carryover from when I was a copyeditor.

Future ideas live in a folder on the laptop where I drop info, plus a blank book I carry around in case inspiration strikes.

#Writephant #scrivener #stylesheet #inspiration #futureideas

@neve
Do I use any tools to keep track of plot lines, character details, research, future ideas?

I do my initial drafting in Scrivener, so I keep all my related research materials there. Character details are in a Style Sheet--a carryover from when I was a copyeditor.

Future ideas live in a folder on the laptop where I drop info, plus a blank book I carry around in case inspiration strikes.

#Writephant #scrivener #stylesheet #inspiration #futureideas

#Development #Techniques
Printing the web · Making webpages look good on paper https://ilo.im/164eym

_____
#Print #Layout #Stylesheet #Content #Webpage #Browser #WebDev #Frontend #HTML #CSS

#Development #Techniques
Printing the web · Making webpages look good on paper https://ilo.im/164eym

_____
#Print #Layout #Stylesheet #Content #Webpage #Browser #WebDev #Frontend #HTML #CSS

#Development #Techniques
Printing the web · Making webpages look good on paper https://ilo.im/164eym

_____
#Print #Layout #Stylesheet #Content #Webpage #Browser #WebDev #Frontend #HTML #CSS

#Development #Techniques
Printing the web · Making webpages look good on paper https://ilo.im/164eym

_____
#Print #Layout #Stylesheet #Content #Webpage #Browser #WebDev #Frontend #HTML #CSS

it's amazing how much #homestar talksay has infected my vocabulary. the other day i named a #stylesheet "styles_upon_styles.css"

it's amazing how much #homestar talksay has infected my vocabulary. the other day i named a #stylesheet "styles_upon_styles.css"

it's amazing how much #homestar talksay has infected my vocabulary. the other day i named a #stylesheet "styles_upon_styles.css"

#ViernesDeEscritorio #DesktopFriday
#KDE #Plasma #Qt #StyleSheet #Pestañas #RetroIluminación #CyberPunk
Buen finde ^_^

#ViernesDeEscritorio #DesktopFriday
#KDE #Plasma #Qt #StyleSheet #Pestañas #RetroIluminación #CyberPunk
Buen finde ^_^

#ViernesDeEscritorio #DesktopFriday
#KDE #Plasma #Qt #StyleSheet #Pestañas #RetroIluminación #CyberPunk
Buen finde ^_^

#ViernesDeEscritorio #DesktopFriday
#KDE #Plasma #Qt #StyleSheet #Pestañas #RetroIluminación #CyberPunk
Buen finde ^_^

#Development #Launches
UA+ · A different type of CSS reset style sheet https://ilo.im/16373p

_____
#CSS #CssReset #UserAgent #StyleSheet #BoxModel #Accessibility #ScreenReader #Browser #WebDev #Frontend

#Development #Launches
UA+ · A different type of CSS reset style sheet https://ilo.im/16373p

_____
#CSS #CssReset #UserAgent #StyleSheet #BoxModel #Accessibility #ScreenReader #Browser #WebDev #Frontend

#Development #Launches
UA+ · A different type of CSS reset style sheet https://ilo.im/16373p

_____
#CSS #CssReset #UserAgent #StyleSheet #BoxModel #Accessibility #ScreenReader #Browser #WebDev #Frontend

#Development #Launches
UA+ · A different type of CSS reset style sheet https://ilo.im/16373p

_____
#CSS #CssReset #UserAgent #StyleSheet #BoxModel #Accessibility #ScreenReader #Browser #WebDev #Frontend

Looking for a stylesheet to spruce up your Markdown? DEVONthink user jsloop has created his own darkly themed styling for DEVONthink and DEVONthink To Go, that he shares with you. #devonthink #devonthinktogo #markdown #stylesheet https://buff.ly/H0JoiYz

Looking for a stylesheet to spruce up your Markdown? DEVONthink user jsloop has created his own darkly themed styling for DEVONthink and DEVONthink To Go, that he shares with you. #devonthink #devonthinktogo #markdown #stylesheet https://buff.ly/H0JoiYz

Looking for a stylesheet to spruce up your Markdown? DEVONthink user jsloop has created his own darkly themed styling for DEVONthink and DEVONthink To Go, that he shares with you. #devonthink #devonthinktogo #markdown #stylesheet https://buff.ly/H0JoiYz

Looking for a stylesheet to spruce up your Markdown? DEVONthink user jsloop has created his own darkly themed styling for DEVONthink and DEVONthink To Go, that he shares with you. #devonthink #devonthinktogo #markdown #stylesheet https://buff.ly/H0JoiYz

Looking for a stylesheet to spruce up your Markdown? DEVONthink user jsloop has created his own darkly themed styling for DEVONthink and DEVONthink To Go, that he shares with you. #devonthink #devonthinktogo #markdown #stylesheet https://buff.ly/H0JoiYz

Open the conversation about:
Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

#CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

So... that said...
Which method is "better"?
They both seem to serve the same functional purpose, in the end.
my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

**For the sake of conversation:**
Why do we have the ability to be more granular about the identity of the source?
See above "@ import" vs "@ font-face"

Also, for the sake of ... the same conversation, really:
[I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

#fontface #import #stylesheet #overkill

Open the conversation about:
Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

#CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

So... that said...
Which method is "better"?
They both seem to serve the same functional purpose, in the end.
my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

**For the sake of conversation:**
Why do we have the ability to be more granular about the identity of the source?
See above "@ import" vs "@ font-face"

Also, for the sake of ... the same conversation, really:
[I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

#fontface #import #stylesheet #overkill

Open the conversation about:
Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

#CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

So... that said...
Which method is "better"?
They both seem to serve the same functional purpose, in the end.
my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

**For the sake of conversation:**
Why do we have the ability to be more granular about the identity of the source?
See above "@ import" vs "@ font-face"

Also, for the sake of ... the same conversation, really:
[I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

#fontface #import #stylesheet #overkill

Open the conversation about:
Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

#CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

So... that said...
Which method is "better"?
They both seem to serve the same functional purpose, in the end.
my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

**For the sake of conversation:**
Why do we have the ability to be more granular about the identity of the source?
See above "@ import" vs "@ font-face"

Also, for the sake of ... the same conversation, really:
[I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

#fontface #import #stylesheet #overkill

Open the conversation about:
Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

#CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

So... that said...
Which method is "better"?
They both seem to serve the same functional purpose, in the end.
my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

**For the sake of conversation:**
Why do we have the ability to be more granular about the identity of the source?
See above "@ import" vs "@ font-face"

Also, for the sake of ... the same conversation, really:
[I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

#fontface #import #stylesheet #overkill

It’s incorrect to write the term #DOGE unadorned. This so-called “department” is wholly imaginary, as is the “authority” under which it claims to operate. Its make therefore should always be rendered in quotes — ‘“DOGE”’ — preferably preceded by the words “the so-called”.

As a second reference, the term “den of vipers” may be used.

#Stylesheet #journalism

It’s incorrect to write the term #DOGE unadorned. This so-called “department” is wholly imaginary, as is the “authority” under which it claims to operate. Its make therefore should always be rendered in quotes — ‘“DOGE”’ — preferably preceded by the words “the so-called”.

As a second reference, the term “den of vipers” may be used.

#Stylesheet #journalism

It’s incorrect to write the term #DOGE unadorned. This so-called “department” is wholly imaginary, as is the “authority” under which it claims to operate. Its make therefore should always be rendered in quotes — ‘“DOGE”’ — preferably preceded by the words “the so-called”.

As a second reference, the term “den of vipers” may be used.

#Stylesheet #journalism

It’s incorrect to write the term #DOGE unadorned. This so-called “department” is wholly imaginary, as is the “authority” under which it claims to operate. Its make therefore should always be rendered in quotes — ‘“DOGE”’ — preferably preceded by the words “the so-called”.

As a second reference, the term “den of vipers” may be used.

#Stylesheet #journalism

Richard Rutter (@Richr) introduces TODS – a #Typographic and #OpenType default #Stylesheet.

“The idea is to set sensible typographic defaults for use on prose (a column of text), making particular use of the font features provided by OpenType.”

https://clagnut.com/blog/2433

Richard Rutter (@Richr) introduces TODS – a #Typographic and #OpenType default #Stylesheet.

“The idea is to set sensible typographic defaults for use on prose (a column of text), making particular use of the font features provided by OpenType.”

https://clagnut.com/blog/2433

Richard Rutter (@Richr) introduces TODS – a #Typographic and #OpenType default #Stylesheet.

“The idea is to set sensible typographic defaults for use on prose (a column of text), making particular use of the font features provided by OpenType.”

https://clagnut.com/blog/2433

#Development #Hacks
Beating ‘!important’ user agent styles (sort of) · How CSS transitions make the impossible possible https://ilo.im/15zqnb

_____
#UserAgent #Stylesheet #CssCascade #CssTransition #CssCalc #CssConstant #Browser #WebDev #Frontend #CSS

#Development #Hacks
Beating ‘!important’ user agent styles (sort of) · How CSS transitions make the impossible possible https://ilo.im/15zqnb

_____
#UserAgent #Stylesheet #CssCascade #CssTransition #CssCalc #CssConstant #Browser #WebDev #Frontend #CSS

#Development #Hacks
Beating ‘!important’ user agent styles (sort of) · How CSS transitions make the impossible possible https://ilo.im/15zqnb

_____
#UserAgent #Stylesheet #CssCascade #CssTransition #CssCalc #CssConstant #Browser #WebDev #Frontend #CSS

#Development #Hacks
Beating ‘!important’ user agent styles (sort of) · How CSS transitions make the impossible possible https://ilo.im/15zqnb

_____
#UserAgent #Stylesheet #CssCascade #CssTransition #CssCalc #CssConstant #Browser #WebDev #Frontend #CSS

Thoughtfully designed, aesthetically pleasing CSS library with many modern features:

"matcha.css – Drop-in semantic styling library in pure css"

Think default #browser #stylesheet: no build steps, no dependencies, no #JavaScript, no configuration needed. Just link it into your new or old #HTML and off you go.

https://matcha.mizu.sh/

#matchacss

Thoughtfully designed, aesthetically pleasing CSS library with many modern features:

"matcha.css – Drop-in semantic styling library in pure css"

Think default #browser #stylesheet: no build steps, no dependencies, no #JavaScript, no configuration needed. Just link it into your new or old #HTML and off you go.

https://matcha.mizu.sh/

#matchacss

Thoughtfully designed, aesthetically pleasing CSS library with many modern features:

"matcha.css – Drop-in semantic styling library in pure css"

Think default #browser #stylesheet: no build steps, no dependencies, no #JavaScript, no configuration needed. Just link it into your new or old #HTML and off you go.

https://matcha.mizu.sh/

#matchacss

Thoughtfully designed, aesthetically pleasing CSS library with many modern features:

"matcha.css – Drop-in semantic styling library in pure css"

Think default #browser #stylesheet: no build steps, no dependencies, no #JavaScript, no configuration needed. Just link it into your new or old #HTML and off you go.

https://matcha.mizu.sh/

#matchacss

Thoughtfully designed, aesthetically pleasing CSS library with many modern features:

"matcha.css – Drop-in semantic styling library in pure css"

Think default #browser #stylesheet: no build steps, no dependencies, no #JavaScript, no configuration needed. Just link it into your new or old #HTML and off you go.

https://matcha.mizu.sh/

#matchacss

If you #edit #manuscripts for #medical-#journal #articles, do you use a #StyleSheet? I don't. I have a different method for managing #style. http://editor-mom.blogspot.com/2024/03/one-medical-editors-method-for-editing.html

If you #edit #manuscripts for #medical-#journal #articles, do you use a #StyleSheet? I don't. I have a different method for managing #style. http://editor-mom.blogspot.com/2024/03/one-medical-editors-method-for-editing.html

If you #edit #manuscripts for #medical-#journal #articles, do you use a #StyleSheet? I don't. I have a different method for managing #style. http://editor-mom.blogspot.com/2024/03/one-medical-editors-method-for-editing.html

If you #edit #manuscripts for #medical-#journal #articles, do you use a #StyleSheet? I don't. I have a different method for managing #style. http://editor-mom.blogspot.com/2024/03/one-medical-editors-method-for-editing.html

If you #edit #manuscripts for #medical-#journal #articles, do you use a #StyleSheet? I don't. I have a different method for managing #style. http://editor-mom.blogspot.com/2024/03/one-medical-editors-method-for-editing.html