home.social

#stylesheet — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #stylesheet, aggregated by home.social.

  1. New (to me) #stylesheet [ETA: I mean #StyleGuide, of course; what am I writing? A blig post?] has just dropped:

    Numbers
    Written out up to and including ninety-nine (however 14 million etc.); commas in thousands.

    #AcademicWriting

  2. @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

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

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

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

  6. 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 buff.ly/H0JoiYz

  7. 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

  8. 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

  9. 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

  10. 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

  11. 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

  12. 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

  13. 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.

    matcha.mizu.sh/

    #matchacss

  14. Как мы отказались от styled-components в React Native приложениях

    Styled-components является стандартом написания стилей для многих команд, которые разрабатывают приложения на React Native. Но мы не всегда задумываемся, зачем мы тащим это в продукт и какую выгоду получим. А что если от styled-components больше вреда, чем пользы? Я поделюсь нашим опытом в Профи и попробуем разобраться вместе.

    habr.com/ru/articles/775476/

    #styledcomponents #reactnative #restyle #tailwind #stylesheet

  15. Quarto: Mal wieder am Stylesheet gebastelt

    Nach einer längeren Pause sah ich mich mal wieder genötigt, am Quarto-Stylesheet, das dieses Blog Kritzelheft antreibt, Korrekturen vorzunehmen. Denn gestern fiel mir auf, daß die Listen nicht mit der gewünschten Serifen-Schrift, sondern mit einem serifenlosen Font angzeigt wurden. kantel.github.io/posts/2023110 #Quarto #Stylesheet #Webworking #StatischeSeiten

  16. Just added Water.css¹ support to Kitten².

    Water is a CSS stylesheet for semantic HTML that’s responsive, has good typographical defaults, and light/dark mode support.

    Useful for demos, teaching, and also as a good base stylesheet for your Small Web places.

    Just add WATER (see what I did there?) to your libraries array in your pages.

    ¹ watercss.kognise.dev/
    ² codeberg.org/kitten/app/

    #Kitten #SmallWeb #SmallTech #WaterCSS #CSS #web #dev #stylesheet #html #semanticHTML

  17. Just added Water.css¹ support to Kitten².

    Water is a CSS stylesheet for semantic HTML that’s responsive, has good typographical defaults, and light/dark mode support.

    Useful for demos, teaching, and also as a good base stylesheet for your Small Web places.

    Just add WATER (see what I did there?) to your libraries array in your pages.

    ¹ watercss.kognise.dev/
    ² codeberg.org/kitten/app/

    #Kitten #SmallWeb #SmallTech #WaterCSS #CSS #web #dev #stylesheet #html #semanticHTML

  18. Just added Water.css¹ support to Kitten².

    Water is a CSS stylesheet for semantic HTML that’s responsive, has good typographical defaults, and light/dark mode support.

    Useful for demos, teaching, and also as a good base stylesheet for your Small Web places.

    Just add WATER (see what I did there?) to your libraries array in your pages.

    ¹ watercss.kognise.dev/
    ² codeberg.org/kitten/app/

    #Kitten #SmallWeb #SmallTech #WaterCSS #CSS #web #dev #stylesheet #html #semanticHTML

  19. Just added Water.css¹ support to Kitten².

    Water is a CSS stylesheet for semantic HTML that’s responsive, has good typographical defaults, and light/dark mode support.

    Useful for demos, teaching, and also as a good base stylesheet for your Small Web places.

    Just add WATER (see what I did there?) to your libraries array in your pages.

    ¹ watercss.kognise.dev/
    ² codeberg.org/kitten/app/

    #Kitten #SmallWeb #SmallTech #WaterCSS #CSS #web #dev #stylesheet #html #semanticHTML

  20. Just added Water.css¹ support to Kitten².

    Water is a CSS stylesheet for semantic HTML that’s responsive, has good typographical defaults, and light/dark mode support.

    Useful for demos, teaching, and also as a good base stylesheet for your Small Web places.

    Just add WATER (see what I did there?) to your libraries array in your pages.

    ¹ watercss.kognise.dev/
    ² codeberg.org/kitten/app/

    #Kitten #SmallWeb #SmallTech #WaterCSS #CSS #web #dev #stylesheet #html #semanticHTML

  21. Fine friends of the night,

    I can finally say that I'm in the final phase of the Sisyphean task of writing a #GTK3 & #GNOME Shell #stylesheet, which I call #temperantia.

    There are still some minor bugs etc, but overall it's usable, for sure. Two features I especially enjoy is the ability to easily change any color, and how well it works on eg. tablets, due to it being scalable.

    Some time later this year it'll be available from Codeberg, along w/ some icons, color schemes & wallpapers.

    :*