We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 38290
    • 712 Posts
    Quote from: emmanuel at Sep 15, 2013, 07:13 PM
    Hi. Really nice initiative !
    Is there a list of todos/ideas/guidelines/placetodiscuss for this default manager ?
    My local setup is running now and i started to tweak _scss files a bit.. it works well and i see a lot to clean there.. but i don't know how to contribute with github... I think a short list of commands you use for pull/commit the theme save me a lot of time..


    Glad you are up and running. I mean grunting. The process for contributing to the theme is the same as the rest of MODX Revolution, so luckily there are some docs to reference for that you can find here:
    http://rtfm.modx.com/search/search-results?search=git&id=1325

    To submit changes you're going to need to use GitHub to Fork the modxcms/revolution repository
    https://help.github.com/articles/fork-a-repo

    You should also create a branch that is specific to the types of changes you are making. For example:
    git checkout -b manager-theme


    would create a new 'manager-theme' branch for you to work on:
    http://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging

    Once you've tested and are ready to submit the work you've done over at your fork and you are ready to submit changes back to the modxcms/revolution repository you'll do that by using Pull Requests:
    https://help.github.com/articles/using-pull-requests
      jpdevries
      • 38290
      • 712 Posts
      Quote from: easylancer at Sep 09, 2013, 01:58 AM
      Quote from: dinocorn at Sep 09, 2013, 01:45 AM
      Back to the topic at hand, I've started working on an automator for creating custom (non-default) Manager themes. Nothing much more than playing around at this point, and will be much more useful when the Sass has been abstracted to separate layout from style. Idea is, you runs this command, answer 11 questions for things like theme name, author info and a few settings like whether you will be using Sass or Less, and it creates a scaffold of all the files you need to stub out your theme.

      Installation
      If you haven't already done so, install grunt-init.
      More on grunt-init at http://gruntjs.com/project-scaffolding
      npm install -g grunt-init


      Clone Theme Automator
      Linux/Mac Users
      git clone [email protected]:jpdevries/grunt-modx-manager-theme.git ~/.grunt-init/modx-manager-theme


      Windows Users
      git clone [email protected]:jpdevries/grunt-modx-manager-theme.git %USERPROFILE%/.grunt-init/modx-manager-theme


      Usage
      cd to an empty directory then
      grunt-init modx-manager-theme

      This is beautiful (my geekyness kicking in), I shall give it a test run later on today and let you know how it goes. I will try and catch up with you later on Skype to talk about the dependencies issue and the Vagrant setup I am working on.

      I've started a similar grunt-init template, but more abstract and to be used for any new web project. You can use Sass, Less or plain-CSS editing and choose from includes like Bootstrap, Foundation 4, HTML5 Boilerplate, Bourbon and Neat. Use grunt tasks to fetch dependencies, pre-process and concatenate CSS & JS files and watch files for changes. Source code, Instructions and Quick Screencast:
      https://github.com/jpdevries/grunt-neat-pages/blob/master/README.md
        jpdevries
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        Well, this grumpy old lady can't even get the environment set up. After about the sixth dependency error, I gave up on it. Maybe another try another time.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 38290
          • 712 Posts
          Quote from: sottwell at Sep 22, 2013, 10:04 PM
          Well, this grumpy old lady can't even get the environment set up. After about the sixth dependency error, I gave up on it. Maybe another try another time.

          I'm assuming you don't have bower installed. I forgot to add that to the docs, which is based off 10up's grunt-wp-theme
          https://github.com/10up/grunt-wp-theme

          Do you have node installed?
          node --version


          Do you have the grunt cli installed?
          npm install -g grunt-cli
          grunt --version


          Do you have bower installed?
          npm install -g bower
          bower --version


          Do you have grunt-init installed?
          npm install -g grunt-init
          grunt-init --version


          Is the neat-pages folder in your grunt-init directory?
          ls ~/.grunt-init/
            jpdevries
            • 38290
            • 712 Posts
            Quote from: sottwell at Sep 22, 2013, 10:04 PM
            Well, this grumpy old lady can't even get the environment set up. After about the sixth dependency error, I gave up on it. Maybe another try another time.

            It doesn't look like installing bower is required. If you have git, node, grunt-cli and grunt-init installed you should be good to go. If you don't mind check those and if still getting an error you can open an issue with details here:
            https://github.com/jpdevries/grunt-neat-pages/issues/new
              jpdevries
              • 8386 ☆ A M B ☆
              • 160 Posts
              Quote from: sottwell at Sep 22, 2013, 10:04 PM
              Well, this grumpy old lady can't even get the environment set up. After about the sixth dependency error, I gave up on it. Maybe another try another time.

              Try this package that I have setup which only require you to install 2 dependencies, which are Vagrant and VirtualBox.

              https://github.com/silentworks/modx-devops

              With this you don't need to worry about Ruby, Ruby Gem, SASS, Bower or GruntJS as its all setup in the environment for you. Let me know how it goes.
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                <sigh> you don't leave me much in the way of an excuse to keep putting it off... so now I'm going to github to make a fork.
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 8386 ☆ A M B ☆
                  • 160 Posts
                  Quote from: sottwell at Sep 23, 2013, 09:36 AM
                  <sigh> you don't leave me much in the way of an excuse to keep putting it off... so now I'm going to github to make a fork.</sigh>

                  Make sure you don't fork the repo, just clone it. smiley If you need any help, you can catch me on Skype later on this evening, I will send you PM with my Skype info.
                    • 38290
                    • 712 Posts
                    So, I’m here to show you how Sass doesn’t have to disrupt your process and workflow, and how it can make your life easier.
                    http://alistapart.com/article/why-sass
                      jpdevries
                      • 28042 ☆ A M B ☆
                      • 24,524 Posts
                        Studying MODX in the desert - http://sottwell.com
                        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                        Join the Slack Community - http://modx.org