Git Product home page Git Product logo

willtheorangeguy.github.io's Introduction

Hi!/¡Hola!/Hoi!/Salut! 👋, I'm @willtheorangeguy

I build small, fun, and powerful programs in Python and reusable web templates! I also like dogs.

Check out some of my GitHub stats below, or scroll down a little further to see the repositories that I am most proud of. If you want to get in touch, don't hesitate to open a pull request, issue or discussion on any of my projects! Happy open sourcing!

willtheorangeguy

 willtheorangeguy

willtheorangeguy

willtheorangeguy.github.io's People

Contributors

deepsource-autofix[bot] avatar deepsource-io[bot] avatar deepsourcebot avatar dependabot[bot] avatar imgbotapp avatar jaskirat11011 avatar restyled-commits avatar restyled-io[bot] avatar willtheorangeguy avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

jaskirat11011

willtheorangeguy.github.io's Issues

Fix DeepSource

DeepSource integration has already been created, now the problems it has created need to be fixed. Also add a DeepSource badge to the README.

  • Fix DeepSource Issues
  • Add Badge

Add Google Analytics

Add Google Analytics, and since we are now using Google projects, this opens the website to Google Fonts as well.

Update redirects

Change each of the redirect pages to match the website style and layout, as well as the main redirect index.html and README.md.

Travel Blog Style

Here are some basic outlines for the style rules that have been proposed for the travel blog:

Colours:

  • Oranges:
    • e7c5a6
    • ff752e
    • fe8136
    • fc682a
  • Blues:
    • afe2e7
    • 98deeb
    • 7eccdc
    • a7c3be

Fonts:

  • Verdana for copy
  • Natural for headings
  • Handwritten font remains for certain stylistic elements

Create Translations

Using tools like Lingohub, POEditor, create translations of the project in popular languages. They could also be released for public help in translation!

Starting Languages:

  • English
  • Dutch
  • Spanish

Update icon sets

Update the icon sets to the latest version. Also ensure that icon licenses are included with the project.

Add a social media page

Add a contact/social media page where all of my social networks are in a grid or table-like pattern, and they all have the icon on top of the name of the social network, and the handle. Each of these boxes should be a button, and when you click on it, sends you to the desired social media network.

The layout would be somewhat like how Font Awesome does its icon-search.

It would also be cool to integrate this with some form of search, as the point would be to have every single account I have on there, so searching would make it much easier for the user.

Add new portfolio page

Remove the current homepage that is a boring text-based list, and create a new portfolio page.

There should be the following sections:

  • About/Portfolio
  • Resume
  • Current Projects
  • Blog
  • Travel Blog
  • What I am running on my computer/current computer build

Add a reviews section

Add a section, or even just a page in the blog, that catalogs reviews I have written and their locations.

Travel Blog to do

  • Update links
  • Update legal pages
  • Languages (Spanish/English)
  • Round image corners with Photoshop

Add a book section

Add a section to the portfolio page that shows books I am reading and am interested in, as well as books that I would recommend.

It would be cool to have progress bars underneath each book for how far I am into the books.

Docker docs

Add documentation for the Docker container.

Add LICENSE preface to the top of each code document

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#16

Add a license preface to the top of each code document. This can be from a personal license, or like something that the GNU GPL v3 has:

        How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

  If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

    <program>  Copyright (C) <year>  <name of author>
    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".

  You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.

  The GNU General Public License does not permit incorporating your program
into proprietary programs.  If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library.  If this is what you want to do, use the GNU Lesser General
Public License instead of this License.  But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.