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

Decide CSS file standard placement and name #56

Open
aureliojargas opened this issue Dec 19, 2018 · 0 comments
Open

Decide CSS file standard placement and name #56

aureliojargas opened this issue Dec 19, 2018 · 0 comments

Comments

@aureliojargas
Copy link
Owner

  • ./assets/2013/ads.css
  • ./assets/2013/site.css
  • ./assets/2013/topbar.css
  • ./assets/2014.css
  • ./assets/articles.css
  • ./assets/bars.css
  • ./assets/bars2.css
  • ./assets/common.css
  • ./assets/gh-fork-ribbon.css
  • ./assets/jekyll.css
  • ./assets/monokai.css
  • ./assets/reset.css
  • ./assets/vim.css
  • ./baterna/baterna.css
  • ./coisinha/inc/coisinha.css
  • ./coisinha/inc/index.css
  • ./coisinha/inc/nav.css
  • ./coisinha/inc/nav2.css
  • ./coisinha/inc/nav3.css
  • ./coisinha/inc/print.css
  • ./coisinha/inc/yui-2.7.0.css
  • ./curso/prompt-doc.css
  • ./dumbs/dumbs.css
  • ./projects/emomemory/emomemory.css
  • ./projects/sedsed/index.css
  • ./projects/soft4.css
  • ./projects/txt2regex/index.css
  • ./rac/info/exemplo.css
  • ./rac/info/tutorial/tutorial.css
  • ./rac/site.css
  • ./regex/guia/styles.css
  • ./regex/regex.css
  • ./surf/site-sub.css
  • ./surf/site.css
  • ./viagem/atacama/mapas/mapas.css
  • ./viagem/viagem.css

It seems CSS files related to layouts are in /assets.

But there's that extra vim.css, that pertains to the /vim area.

It seems areas have their CSS file inside their folder , but the naming is not consistent.

Decide what would be the desired pattern, document it in the main README and fix the outliers.

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

No branches or pull requests

1 participant