Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added some Sass specific blogposts #20

Closed
wants to merge 1 commit into from
Closed

added some Sass specific blogposts #20

wants to merge 1 commit into from

Conversation

sturobson
Copy link
Contributor

Thought these might be good here. I've added in date order. No worries if not deserved of space here.

Thought these might be good here. I've added in date order. No worries if not deserved of space here.
@MarioRicalde
Copy link
Contributor

Not convinced that just putting them on the top is the best way to go for this; there should be some sort of order on those articles.

@bpainter
Copy link
Member

The way we're displaying articles right now is temporary. Something much nicer coming in the near future.

@sturobson
Copy link
Contributor Author

Pleased this has garnered some discussion. Like I said I'm happy to not have them included.

By date is probably not ideal for all and sundry to submit posts until you've got whatever planned in place.

@jina
Copy link
Member

jina commented Oct 14, 2013

Is it possible to allow the loop to post in alphabetical order or something, but not require people to have to manually do it?

@bpainter
Copy link
Member

Yeah. We could dump those links in a yml file instead and just order things with Ruby.

On Oct 14, 2013, at 5:37 PM, ₍˄ุ.͡˳̫.˄ุ₎ notifications@github.com wrote:

Is it possible to allow the loop to post in alphabetical order or something, but not require people to have to manually do it?


Reply to this email directly or view it on GitHub.

@jina
Copy link
Member

jina commented Oct 14, 2013

They're already in a .yml file. Boom!

@MarioRicalde
Copy link
Contributor

I'm not sure that that's the way to go, mainly because those articles some
follow some sort of coherent path, from "introduction" to "advanced".

█ Mario "Kuroir" Ricalde
_█ *_Front-end Engineer *
_█ _kuroir@twitter
*█ *+1 ‪(415) 800-415-4‬

On Mon, Oct 14, 2013 at 4:41 PM, Bermon Painter notifications@github.comwrote:

Yeah. We could dump those links in a yml file instead and just order
things with Ruby.

On Oct 14, 2013, at 5:37 PM, ₍˄ุ.͡˳̫.˄ุ₎ notifications@github.com
wrote:

Is it possible to allow the loop to post in alphabetical order or
something, but not require people to have to manually do it?


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//pull/20#issuecomment-26291262
.

@jina
Copy link
Member

jina commented Oct 14, 2013

That's a good point… If this page gets long enough, we may have to break the articles down into categories… Introduction, Organization, Tricks & Tips, Refactoring, etc. For now I'll add to the bottom of the list… is that cool?

@bpainter
Copy link
Member

I think in your case your best bet would be for us to show the first article and then have folks read through the series based on the linking on your site.

On Oct 14, 2013, at 5:44 PM, Mario Ricalde notifications@github.com wrote:

I'm not sure that that's the way to go, mainly because those articles some
follow some sort of coherent path, from "introduction" to "advanced".

  • █ Mario "Kuroir" Ricalde
    _█ *_Front-end Engineer *
    _█ *_kuroir@twitter*
    *█ *+1 ‪(415) 800-415-4‬

On Mon, Oct 14, 2013 at 4:41 PM, Bermon Painter notifications@github.comwrote:

Yeah. We could dump those links in a yml file instead and just order
things with Ruby.

On Oct 14, 2013, at 5:37 PM, ₍˄ุ.͡˳̫.˄ุ₎ notifications@github.com
wrote:

Is it possible to allow the loop to post in alphabetical order or
something, but not require people to have to manually do it?


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHubhttps://github.com//pull/20#issuecomment-26291262
.


Reply to this email directly or view it on GitHub.

@jina
Copy link
Member

jina commented Oct 14, 2013

Yeah, I'll do that to avoid the repetition.

@jina jina closed this in 7d877d3 Oct 14, 2013
nex3 pushed a commit that referenced this pull request Jun 23, 2023
asaf400 pushed a commit to asaf400/ass-site that referenced this pull request Apr 18, 2024
asaf400 pushed a commit to asaf400/ass-site that referenced this pull request Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants