191 skills found · Page 6 of 7
harlanji / Xmpp4jsAn XMPP/BOSH library written in Javascript. NOTE: this project is long abandoned. I recommend using StropheJS instead; if you are interested in maintaining it please feel free to fork and I'll point people there. (2007, pure-JS DOM; last tested in 2018 Chrome and iOS)
afdhruval / ObysCreated using Shery.js, CSS animations, and modern JavaScript, this site delivers smooth scroll-based effects and dynamic motion. Deployed on Vercel, it demonstrates refined animation techniques while maintaining clean performance and responsive design.
d-stoll / Attio JsA community-maintained JavaScript/TypeScript SDK for Attio
Yoric / Marv The TinkerA JS-to-JS compiler written in JS to simplify writing, maintaining and troubleshooting JavaScript code bases.
viodotcom / OpticksVio.com Toggle Flag JavaScript SDK - Maintainer: @jopdeklein
Sachin-deepak-S / Fitness AdventureA gamified fitness web app that helps users track workouts, maintain streaks, complete quests, and level up their fitness journey. Built with PHP, MySQL, HTML/CSS, and JavaScript, it features secure login, user dashboards, profile management, and an XP-based system to stay motivated.
openstack / Xstatic Angular GettextAngular-Gettext JavaScript library packaged as XStatic. Mirror of code maintained at opendev.org.
Munia-Akhter / OBE Based Result Management SystemResult management system Outcome Based Education (OBE) is a system that will facilitate the storing and evaluation of all the components of an OBE based curriculum to process student results. It is very difficult to find a usable traditional result management system that would be responsive and easily amenable. To meet the challenges of continuous quality improvement concept of OBE, it is necessary to find a system that can be adjustable with minimal effort. This system is developed to address this need. The stakeholders of the system are the university and the instructors for making the result processing of a course that is design based on the concept of OBE. Setting up Course Outcome (CO) for a course and creating a map between Program Outcome (PO)s is one of the core tasks of the system. It is also possible to distribute the course marks and submit obtained marks of individual students of a course. According to these two features the system can analyze the results of all courses and generate individual student’s PO achievement history.In my project, the main language of programming which we are using is PHP, JavaScript. MySQL server is used to maintain system database. For designing the view for both frontend and backend, we have used HTML5, CSS3, Bootstrap.
EMETEM-GLOBAL-ENTERPRISE / Prototype# Contributing to this repository <!-- omit in toc --> ## Getting started <!-- omit in toc --> Before you begin: - This site is powered by Node.js. Check to see if you're on the [version of node we support](contributing/development.md). - Have you read the [code of conduct](CODE_OF_CONDUCT.md)? - Check out the [existing issues](https://github.com/github/docs/issues) & see if we [accept contributions](#types-of-contributions-memo) for your type of issue. ### Use the 'make a contribution' button  Navigating a new codebase can be challenging, so we're making that a little easier. As you're using docs.github.com, you may come across an article that you want to make an update to. You can click on the **make a contribution** button right on that article, which will take you to the file in this repo where you'll make your changes. Before you make your changes, check to see if an [issue exists](https://github.com/github/docs/issues/) already for the change you want to make. ### Don't see your issue? Open one If you spot something new, open an issue using a [template](https://github.com/github/docs/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix. ### Ready to make a change? Fork the repo Fork using GitHub Desktop: - [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop. - Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)! Fork using the command line: - [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them. Fork with [GitHub Codespaces](https://github.com/features/codespaces): - [Fork, edit, and preview](https://docs.github.com/en/free-pro-team@latest/github/developing-online-with-codespaces/creating-a-codespace) using [GitHub Codespaces](https://github.com/features/codespaces) without having to install and run the project locally. ### Make your update: Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-githubdocs-repository). - Are you making changes to the application code? You'll need **Node.js v14** to run the site locally. See [contributing/development.md](contributing/development.md). - Are you contributing to markdown? We use [GitHub Markdown](contributing/content-markup-reference.md). ### Open a pull request When you're done making changes and you'd like to propose them for review, use the [pull request template](#pull-request-template) to open your PR (pull request). ### Submit your PR & get it reviewed - Once you submit your PR, others from the Docs community will review it with you. The first thing you're going to want to do is a [self review](#self-review). - After that, we may have questions, check back on your PR to keep up with the conversation. - Did you have an issue, like a merge conflict? Check out our [git tutorial](https://lab.github.com/githubtraining/managing-merge-conflicts) on how to resolve merge conflicts and other issues. ### Your PR is merged! Congratulations! The whole GitHub community thanks you. :sparkles: Once your PR is merged, you will be proudly listed as a contributor in the [contributor chart](https://github.com/github/docs/graphs/contributors). ### Keep contributing as you use GitHub Docs Now that you're a part of the GitHub Docs community, you can keep participating in many ways. **Learn more about contributing:** - [Types of contributions :memo:](#types-of-contributions-memo) - [:mega: Discussions](#mega-discussions) - [:beetle: Issues](#beetle-issues) - [:hammer_and_wrench: Pull requests](#hammer_and_wrench-pull-requests) - [:question: Support](#question-support) - [:earth_asia: Translations](#earth_asia-translations) - [:balance_scale: Site Policy](#balance_scale-site-policy) - [Starting with an issue](#starting-with-an-issue) - [Labels](#labels) - [Opening a pull request](#opening-a-pull-request) - [Working in the github/docs repository](#working-in-the-githubdocs-repository) - [Reviewing](#reviewing) - [Self review](#self-review) - [Pull request template](#pull-request-template) - [Suggested changes](#suggested-changes) - [Windows](#windows) ## Types of contributions :memo: You can contribute to the GitHub Docs content and site in several ways. This repo is a place to discuss and collaborate on docs.github.com! Our small, but mighty :muscle: docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed. ### :mega: Discussions Discussions are where we have conversations. If you'd like help troubleshooting a docs PR you're working on, have a great new idea, or want to share something amazing you've learned in our docs, join us in [discussions](https://github.com/github/docs/discussions). ### :beetle: Issues [Issues](https://docs.github.com/en/github/managing-your-work-on-github/about-issues) are used to track tasks that contributors can help with. If an issue has a triage label, we haven't reviewed it yet and you shouldn't begin work on it. If you've found something in the content or the website that should be updated, search open issues to see if someone else has reported the same thing. If it's something new, open an issue using a [template](https://github.com/github/docs/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix. ### :hammer_and_wrench: Pull requests A [pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests) is a way to suggest changes in our repository. When we merge those changes, they should be deployed to the live site within 24 hours. :earth_africa: To learn more about opening a pull request in this repo, see [Opening a pull request](#opening-a-pull-request) below. ### :question: Support We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with GitHub, unrelated to our documentation, please [contact GitHub Support directly](https://support.github.com/contact). Any issues, discussions, or pull requests opened here requesting support will be given information about how to contact GitHub Support, then closed and locked. If you're having trouble with your GitHub account, contact [Support](https://support.github.com/contact). ### :earth_asia: Translations This website is internationalized and available in multiple languages. The source content in this repository is written in English. We integrate with an external localization platform called [Crowdin](https://crowdin.com) and work with professional translators to localize the English content. **We do not currently accept contributions for translated content**, but we hope to in the future. ### :balance_scale: Site Policy GitHub's site policies are published on docs.github.com, too! If you find a typo in the site policy section, you can open a pull request to fix it. For anything else, see [the CONTRIBUTING guide in the site-policy repo](https://github.com/github/site-policy/blob/main/CONTRIBUTING.md). ## Starting with an issue You can browse existing issues to find something that needs help! ### Labels Labels can help you find an issue you'd like to help with. - The [`help wanted` label](https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) is for problems or updates that anyone in the community can start working on. - The [`good first issue` label](https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) is for problems or updates we think are ideal for beginners. - The [`content` label](https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3Acontent) is for problems or updates in the content on docs.github.com. These will usually require some knowledge of Markdown. - The [`engineering` label](https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3Aengineering) is for problems or updates in the docs.github.com website. These will usually require some knowledge of JavaScript/Node.js or YAML to fix. ## Opening a pull request You can use the GitHub user interface :pencil2: for some small changes, like fixing a typo or updating a readme. You can also fork the repo and then clone it locally, to view changes and run your tests on your machine. ## Working in the github/docs repository Here's some information that might be helpful while working on a Docs PR: - [Development](/contributing/development.md) - This short guide describes how to get this app running on your local machine. - [Content markup reference](/contributing/content-markup-reference.md) - All of our content is written in GitHub-flavored Markdown, with some additional enhancements. - [Content style guide for GitHub Docs](/contributing/content-style-guide.md) - This guide covers GitHub-specific information about how we style our content and images. It also links to the resources we use for general style guidelines. - [Reusables](/data/reusables/README.md) - We use reusables to help us keep content up to date. Instead of writing the same long string of information in several articles, we create a reusable, then call it from the individual articles. - [Variables](/data/variables/README.md) - We use variables the same way we use reusables. Variables are for short strings of reusable text. - [Liquid](/contributing/liquid-helpers.md) - We use liquid helpers to create different versions of our content. - [Scripts](/script/README.md) - The scripts directory is the home for all of the scripts you can run locally. - [Tests](/tests/README.md) - We use tests to ensure content will render correctly on the site. Tests run automatically in your PR, and sometimes it's also helpful to run them locally. ## Reviewing We (usually the docs team, but sometimes GitHub product managers, engineers, or supportocats too!) review every single PR. The purpose of reviews is to create the best content we can for people who use GitHub. :yellow_heart: Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time. :yellow_heart: Reviews discuss content, not the person who created it. :yellow_heart: Reviews are constructive and start conversation around feedback. ### Self review You should always review your own PR first. For content changes, make sure that you: - [ ] Confirm that the changes address every part of the content strategy plan from your issue (if there are differences, explain them). - [ ] Review the content for technical accuracy. - [ ] Review the entire pull request using the [localization checklist](contributing/localization-checklist.md). - [ ] Copy-edit the changes for grammar, spelling, and adherence to the style guide. - [ ] Check new or updated Liquid statements to confirm that versioning is correct. - [ ] Check that all of your changes render correctly in staging. Remember, that lists and tables can be tricky. - [ ] If there are any failing checks in your PR, troubleshoot them until they're all passing. ### Pull request template When you open a pull request, you must fill out the "Ready for review" template before we can review your PR. This template helps reviewers understand your changes and the purpose of your pull request. ### Suggested changes We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch. As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations). ## Windows This site can be developed on Windows, however a few potential gotchas need to be kept in mind: 1. Regular Expressions: Windows uses `\r\n` for line endings, while Unix based systems use `\n`. Therefore when working on Regular Expressions, use `\r?\n` instead of `\n` in order to support both environments. The Node.js [`os.EOL`](https://nodejs.org/api/os.html#os_os_eol) property can be used to get an OS-specific end-of-line marker. 1. Paths: Windows systems use `\` for the path separator, which would be returned by `path.join` and others. You could use `path.posix`, `path.posix.join` etc and the [slash](https://ghub.io/slash) module, if you need forward slashes - like for constructing URLs - or ensure your code works with either. 1. Bash: Not every Windows developer has a terminal that fully supports Bash, so it's generally preferred to write [scripts](/script) in JavaScript instead of Bash.
openstack / Eslint Config OpenstackJavaScript Style Guidelines for OpenStack. Mirror of code maintained at opendev.org.
bevry-archive / Bal UtilUtility functions for JavaScript and Node.js used and maintained by Benjamin Lupton
Floofies / Differentia.jsNo longer being supported or maintained. A Graph Theory & Data Structure Library for JavaScript.
anselmh / Css Slider[DEPRECATED] A mostly CSS based slider which is only enhanced by JavaScript and is hardware accellerated by default. Not actively maintained.
tahmid-ni7 / Online Bookshop With LaravelThis is an online bookshop project with laravel 5.8, bootstrap 4, javaScript and jquery. In this project I use stripe payment system, and Laravel Shoppingcart for maintaining the user orders and payments. This project has many other cool functionality, like as Data table and so on.
mojiito / MojiitoDEPRECATED - No longer maintained! Mojito is a JavaScript framework, heavily inspired by Angular, which brings the benefits of components, services, ... to your (static) website.
OmriGM / Code MetricsLive Code Metrics is a VS Code extension that provides real-time analysis of function sizes in your code. Supporting JavaScript, TypeScript, Java, and Python, it helps maintain clean and maintainable code by visualizing function lengths against customizable thresholds.
botblock / BotListA package for easily updating your server count on all Discord bot lists. [JavaScript - maintained by @PassTheMayo]
RednibCoding / Paula TrackerA classic 4-channel sound tracker inspired by the legendary **Ultimate Sound Tracker** from the Amiga era. Built with modern web technologies (ES6 JavaScript, Canvas, Web Audio API) while maintaining that old-school demoscene aesthetic.
sibisiddharth8 / RoyalConnect2k24Developed and maintained the official website of the Rotaract Club of Coimbatore Royals, "RoyalConnect2k24." The project was built using ReactJS, HTML, CSS, JavaScript, and React Bootstrap, ensuring a responsive and user-friendly interface. Utilized Figma for UI design, emphasizing a modern and cohesive visual experience.
Viewforview / IntroduceDigital advertising is becoming increasingly important. At the same time, however, the problems of this type of marketing are becoming more and more apparent. Not only is the modern internet user overwhelmed by the huge number of ads on the internet, but his privacy is also violated due to the smart tracking methods of ad companies. The VIEW FOR VIEW (VIE) tries to solve this issue. Short facts: VIE was developed by the team of cryptocurency. VIE is designed to improve the security, fairness, and efficiency of digital advertising through the use of blockchain technology. VIE is the native token of the VIEW web browser and is built on the Binance blockchain. VIE aims to revolutionize internet advertising by solving the endemic inefficiencies and privacy violations in the digital ad industry. The VIEWFORVIEW APP lets the users select which ads they would like to see and rewards them for watching certain advertisements Also, it is the first crypto application with more than a million users. Users maintain privacy as they earn VIE for viewing ads. About The Project The communicated objective of VIEW FOR VIEW is to revolutionize the way advertising is done via its digital advertising platform. The foundation of the cryptocurrency is Binance. For the first time, users can decide whether they want to see ads or not. As a result, users now view fewer, more targeted, and desired advertisements. This means they become more valuable to advertisers. In addition, the privacy of users is improved. Since users can actively choose to view an ad, only very relevant ads are allowed. The user is paid VIE for viewing the ad. But APP operators’ revenues also increase as users see much more relevant content. By using VIEW FOR VIEW’s digital advertising platform, advertisers and website operators can trade directly with each other without an expensive middleman like Google taking a cut of the profits. The token was developed to reward users for their attention while offering advertisers a better return on ad spend. The VIEW FOR VIEW was founded in 2015 by Brendan Eich and Brian Bondy. Brendan Eich is a well-known name in the tech world. Not only did he create JavaScript, but he was also a key figure in the development of Mozilla’s Firefox. Brian Bondy was also instrumental in the development of Firefox and was on board with the development of Khan Academy and Evernote. In 2017, the ICO took place, which sold out more quickly than almost any other project. Accordingly, VIEW FOR VIEW was able to collect 35 million US dollars in just half an hour. Almost all of the 1.5 billion tokens have now been distributed. Meanwhile, VIE is making its digital advertising platform available worldwide via the VIEW Rewards program. How Does It Work? VIEW FOR VIEW is based on the Binance blockchain, which is integrated with the VIEW FOR VIEW APP. The protocol relies on three parties to function: Users, Creators, and Advertisers, to allow businesses to access users’ attention: Users earn for their attention: Users maintain privacy as they earn VIE for viewing ads. Creators get paid for making great content: Publishers and creators earn ad revenue and user contributions as well as tips. Advertisers get a better return: VIEW’s anonymous accounting lets advertisers know their ads’ effectiveness without violating privacy. (Source: Viewforview.com) The idea is pretty smart. The VIEW FOR VIEW APP VIEW matches content with advertisers that are truly relevant through the use of machine learning in the device, while feedback mechanisms ensure that users receive ads for the products they are most likely to buy. All of this data is encrypted and stored only on the device. And VIEW protects the identity of its users. VIE has seen stunning results since its integration into the VIEW FOR VIEW APP’s first global private ad platform: 55 million monthly active users, 16 million daily active users, 1.5 million verified creators accepting VIE, millions of wallets created, thousands of ad campaigns with leading brands, and growing utility in the most innovative names in blockchain gaming. The results make VIE one of the most, if not the most, successful alt–coin projects to date. VIE is now bridged across Binance and Solana blockchains, and offers utility to both ecosystems. — viewforview.com VIEW FOR VIEW APP The tokens store all user data in a secure and private format while providing specific personalized advertising to advertisers. This is only possible with the end user’s consent. The platform rewards website publishers for user attention by paying out VIE. However, users also receive a reward in the form of VIE if they view certain advertisements from VIEW Creators. Users can always decide which advertisements they would like to see. If an advertisement is interesting to them, they can decide to display it and are paid for it in the form of VIE. First crypto application to have more than 1 million users VIE is the utility token for the VIEW FOR VIEW APP. It is an BEP-20 token secured by Proof-of-Work (PoW). The token is the unit of reward in this advertising ecosystem. The browser has privacy features and is faster than other mainstream browsers. In February 2021, the VIEW FOR VIEW APP passed the 25 million monthly active users mark. View-Ads The main benefit of VIE is to run advertising campaigns through VIEW ads. Since last year, advertisers have had to spend at least $2,500 per month to launch a campaign. However, a more comprehensive self-service platform is in the works. Ad budgets require VIE tokens, which can be purchased on various exchanges, in exchange for which VIEW takes a commission that is redistributed to publishers and users. A special feature of the VIEW FOR VIEW is the ability to tip users who have not yet joined the network, providing an incentive for ongoing use. Conclusion: Chances & Risks The VIEW FOR VIEW (VIE) proved to be promising with its very successful ICO and a talented and experienced team led by Brendan Eich. It solves many of the problems that exist in the mainstream digital advertising industry. Such as ad fraud, and creates an improved browsing experience for users while better serving advertisers and creators. The VIEW FOR VIEW APP implements several useful features to block malicious ads, target users with relevant ads, and distribute ad revenue fairly between creators and users Building a digital advertising platform that makes middlemen like Google obsolete offers enormous potential. After all, the market for online advertising is gigantic. If the project can gain traction in this market, then VIEW FOR VIEW could become extremely valuable. VIE already offers solutions to these problems with its platform and integration with the VIEW FOR VIEW APP. Moreover, VIE’s team consists of very capable developers. Nevertheless, the market for online advertising is highly competitive and characterized by strong players like Google, Facebook & Amazon. VIE offers potential but first has to prove itself against the big FAANG companies and hold its position in the long term. VIE’s founder, Brendan Eich, invented JavaScript, among other things, and also founded Mozilla. If the developers succeed, VIE could be a front-runner in the Web 3.0 space. Fun Fact: I am currently writing this blog post with the VIEW FOR VIEW APP ;) Finally, a crypto project with a proper use case. Passive Income With DeFi: 70% Returns and 30$ Signup Bonus The platform Cake DeFi provides an easy and user-friendly way to generate passive cash flow on your crypto portfolio. This is done in three different ways, called lending, staking, and liquidity mining. All you have to do is to sign up for the platform, top-up money via credit card or transfer cryptocurrencies and put your assets to work. Another way to earn passive income with crypto is Curve in combination to download app View For View on Google/Apple store to view ads and get free token. How To Buy $VIE? For newcomers, I’d personally recommend using website viewforview.com as an easy-to-use trading platform with a user-friendly interface and step-by-step instructions. viewforview.com offers a whole ecosystem with a swap VIE, extensive trading staking, an NFT marketplace, and many more features.
