stylus / stylus-lang.com Goto Github PK

Currently we're loading the full jQuery lib and as far as I can see it's only for plugins.js and main.js which are short, simple, and can easily be rewritten in vanilla js with IE8 (or IE7?) support.

@kizu I'm leaving open-source. Can I transfer domain to you or someone at Automattic? I don't want to keep paying for it.

Try to access the website but it looks like it is unavailable now

Negative variable issue.
If no colon after property, this property will ignored":

value = 100px

.foo 
    width 10px
    margin-left -(value)

wil render as:

.foo {
    width: 10px;
}

stylus/stylus#1870 (comment)

It seems that conditional overwriting of stylus variables with media queries isn't possible. For example, the following stylus code:

bg_color = white

@media (prefers-color-theme: dark)
    bg_color = black

body
    background: bg_color

Compiles to:

body {
  background: #fff;
}

Is this behavior intended? The documentation doesn't go into detail about how variables interact with media queries.

• "Footer" area needs love.
• Should probably use an off-canvas menu. Received some complaints about the 1/3 screen-height menu on mobile. :}

https://stylus-lang.com/docs/bifs.html#sliceval-start-end
It may already be fixed by stylus/stylus#2300 in 2017, but the official document page isn't updated yet.

Stylus has a problem with fragmentation. I think it's fine to honor the patron of the language, but not at the cost of fragmenting the brand.

Perhaps we should migrate the Gitter to stylus/stylus, and add some buttons to that chat room on the main repo's README (as well as some other sweeeeeet badges) and on the website itself.

We should really try to migrate users to the same official-looking chat room in whatever ways we can.

@kizu @Panya Care if I remove master since we're not using it for anything and it adds to confusion/project bloat?

They're in reverse alphabetical right now. Would rather them be in alphabetical.

can someone clean up the credits? they look like crap

• smaller fonts
• sans
• dark tomato color instead of white (same with tj's link)
• i wish we could B&W and then color overlay Learnboost's logo so it matched the others
• looks terrible on mobile
• it'd be nice if we could just remove all the text like "originated at:", "supported by:" and just had a block list of links/logos

oh and the stylus organization on GitHub needs the new logo

I've sent MojoTech an email about using the logo. They'll probably approve it at the beginning of next week. If they don't or it takes too long we can design a new logo for it in a few days.

Hi all, happy to write a patch but I wasn't sure of the current state of the website, which branch to use, etc, etc. It looks to me like things are in a state of flux at the moment, what with three sites floating around:
http://stylus.github.io/stylus
http://LearnBoost.github.io/stylus
http://www.stylus-lang.com

I think the document need to be re-organized. The current document is lack or organizing. I think we should consider chunk it into many sections. Also, a searchbox would be welcome for a document. We can use google cse, duckduckgo or yandex.

Btw, I would like to suggest the writing style for document. Using this one: https://css-tricks.com/words-avoid-educational-writing

I notice that sometimes the http://stylus-lang.com/try.html page does not compile correctly. I use it quite often to test how things will work or look (probably better to do locally, but it makes it easy to isolate and test code).

Example:

// Mixin
position(type, values...)
    properties = top right bottom left
    skip       = _

    // top value
    push(values, skip) if length(values) is 0

    // right value
    push(values, values[0]) if length(values) is 1

    // bottom value
    push(values, values[0]) if length(values) is 2

    // left value
    push(values, values[1]) if length(values) is 3

    position: type

    for property, index in properties
        {property}: values[index] if values[index] isnt skip

// Usage
.vh
.screen-reader-text
    position: absolute auto _ _ -999em
    width: 1px
    height: 1px
    overflow: hidden

Try Stylus!

It compiles just fine locally and on CodePen though (view compiled CSS)

Hi just wanted to give you some feedback from the outside world :)

I came across stylus multiple times now, while searching for a portable less/scss-replacement.
However, it wasn't clear to me that stylus does accept brackets (scss/less syntax) at all!

Therefore, i think many devs skim thru the site and will probably think 'oh this is kindof coffeescript for css..nevermind'.

I would consider the bracket/semicolon-omission a feature, rather than the USP.

My advice: communicate 'a portable,flexible,etc less/scss-replacement' in the header. That will probably increase adoption for curious less/scss developers.

As described here, the attribution should be updated with a mention of TJ and Automattic.
I'll make a PR for that in a bit.

Color of navigation on the website is to vibrant. Make it less vibrant please. It would be much comfortable to use it.

Stylus currently resolves stylus files if they have the same name as their parent folder (with .styl extension).
For example:
given the following directory structure where test.styl is the input file and test.css is the output file

.
├── a
|   ├── a.styl
├── test.styl
├── test.css

and the following file contents

./test.styl

@require a

./a/a.styl

body
  background-color red

yields the following output
./test.css

body {
  background-color: #f00;
}

this seems like logical and intended behavior, but it appears to not be listed in the documentation ( or at least not in the @import.md index styles section:

@ import also supports index styles. This means when you @import blueprint, it will resolve
either blueprint.styl or blueprint/index.styl. This is really useful for libraries that want to expose all their features, while still allowing feature subsets to be imported.

Unless this behavior is unintended, it should probably be changed to something like:

@ import also supports index styles. This means when you @import blueprint, it will resolve
blueprint.styl, blueprint/index.styl, or blueprint/blueprint.styl . This is really useful for libraries that want to expose all their features, while still allowing feature subsets to be imported.

Hey I just noticed in my spam folder that the domain is up for renewal tomorrow. I'm broke and don't really think it's worth it anyway. Maybe we should just put it on stylus.github.io or something?