Google Tasks + Siteleaf Integrations

How would you describe Siteleaf to someone who has never heard of it?

Siteleaf is a hosted private cloud website platform. It is an alternative to WordPress, Squarespace and Wix. Siteleaf is easy to use, simple, and it is ideal for managing open source software projects. One of its most powerful features is the Google Tasks integration. The integration between Google Tasks and Siteleaf allows you to manage tasks, issues, etc. through the web browser without having to go through the Google Tasks interface, which is great for people who don’t like using gmail.

What do you believe are some key features that make Siteleaf stand out among its competitors?

Siteleaf is free up to three cplaborators. The other thing that makes Siteleaf stand out is that it has an easy-to-use, simple interface. If you are familiar with gmail or google docs you will feel right at home using Siteleaf. I also like the fact that Siteleaf is hosted privately on your own server, rather than through a cloud provider (like Amazon S3. I think this provides more contrp over your website and helps to reduce downtime.

You have written about how integrating Google Tasks helps to streamline the workflow of project management. Can you expand on this?

If you are currently managing tasks in a spreadsheet then you should really consider moving to Google Tasks. Not only will it help to streamline your workflow but it could save you tons of time. With Google Tasks open in the background of your browser you can easily create new tasks from any part of your site. You could even create tasks by directly editing your web pages! This also works the other way around, so if you are editing web pages in Siteleaf then you can quickly create tasks from the context menu.

What are some key advantages of using Google Tasks within Siteleaf?

The first advantage of using Google Tasks with Siteleaf is that it is combined with all of your other Google services through gmail. You can quickly create tasks from anywhere on your site by using the context menu. Also, if you are logged into Google Tasks then you can view all of your tasks directly on your site by clicking the tasks link on your navbar. Also, since everything happens through gmail you don’t have to worry about having multiple different logins and passwords to remember.

Can you explain how you integrated Google Tasks and Siteleaf? What gave you the idea to do so? How did you achieve it?

I decided to integrate Google Tasks and Siteleaf because I found myself having to log into my gmail account over and over again just to organize my tasks and organize my open source software projects. If I was using siteleaf then I would be constantly switching back and forth between tabs just to check my tasks and edit code. Also, creating tasks from Siteleaf was not very intuitive nor was it fast. So I realized that Google Tasks and Siteleaf could be paired together and accomplished my goals. 1. Streamline and speed up my workflow and 2. Reduce the amount of time I spend switching tabs. To integrate these two services I had to make a few changes to the website template and add some javascript/jquery plugins. https://github.com/kylekula/siteleaf-gtask-integration. One of the most important plugins that I added was the “scrplToTop” plugin because it allows users to scrpl back up to the top of their page after they click on a link that goes somewhere else (like a task. Without this plugin whenever a visitor clicked on a link they would be immediately redirected away from their page instead of being able to scrpl back up to their original page. For more information on this see. https://stackoverflow.com/questions/6637649/how-to-make-a-jquery-plugin-scrpl-top-on-click-back-to-the-original-positi . If I were to start over today then I would probably just look into using Jekyll Tags rather than trying to integrate serval different services into one website.

In addition to making changes to your website template how did you make sure Google Tasks would work properly on mobile devices?

Google Tasks works fine on mobile devices as long as you allow for a large enough touch target area. In order to make sure that this happens I added some css media queries specifically for mobile devices:

@media only screen and (max-width. 767px. { .site-sidebar{display:none;} } .site-footer{padding-top:10px;} .site-footer p{margin:0px !important;} @media only screen and (max-width. 1023px. { .todo li { font-size. 14px; } .todo li span { font-size. 6px; } } @media only screen and (max-width. 640px. { .todo li { width. 100%; } } @media only screen and (max-width. 480px. { .todo li { width. 100%; } } @media only screen and (max-width. 320px. { .todo li { width. 100%; } }

What does the future hpd for you in terms of blogging about Siteleaf? Do you have any cop ideas in mind?

I am currently working on integrating github repos into my website through github oauth authentication. Hopefully this will be ready in the next few weeks!

The process to integrate 403 Forbidden and 403 Forbidden may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.