diff --git a/.gitignore b/.gitignore index 297959a..66f8fb5 100644 --- a/.gitignore +++ b/.gitignore @@ -1,23 +1,2 @@ -/vendor/ -node_modules/ -npm-debug.log -yarn-error.log - -# Laravel 4 specific -bootstrap/compiled.php -app/storage/ - -# Laravel 5 & Lumen specific -public/storage -public/hot - -# Laravel 5 & Lumen specific with changed public path -public_html/storage -public_html/hot - -storage/*.key -.env -Homestead.yaml -Homestead.json -/.vagrant -.phpunit.result.cache +.idea/ +.vscode/ diff --git a/CNAME b/CNAME new file mode 100644 index 0000000..0d1f409 --- /dev/null +++ b/CNAME @@ -0,0 +1 @@ +linkedin.javanile.org \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..52d5693 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,92 @@ +# Contributing + +When contributing to this repository, please first discuss the change you wish to make via issue, +email, or any other method with the owners of this repository before making a change. + +Please note we have a code of conduct, please follow it in all your interactions with the project. + +## Pull Request Process + +1. Ensure any install or build dependencies are removed before the end of the layer when doing a + build. +2. Update the README.md with details of changes to the interface, this includes new environment + variables, exposed ports, useful file locations and container parameters. +3. Increase the version numbers in any examples files and the README.md to the new version that this + Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). +4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you + do not have permission to do that, you may request the second reviewer to merge it for you. + +## Code of Conduct + +### Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, gender identity and expression, level of experience, +nationality, personal appearance, race, religion, or sexual identity and +orientation. + +### Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or +advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +### Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or +reject comments, commits, code, wiki edits, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +### Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +### Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at . All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +### Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at [http://contributor-covenant.org/version/1/4][version] + +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/ diff --git a/LICENSE b/LICENSE index cf482f7..1fad7b4 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2024 Javanile +Copyright (c) 2022 Javanile Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/README.md b/README.md index 32b030c..4a2da12 100644 --- a/README.md +++ b/README.md @@ -1 +1,32 @@ -# linkedin-button \ No newline at end of file +
+ +# LinkedIn Button + +***Create Magic LinkedIn Button for your README.md*** + +like this +[![Share on LinkedIn](https://img.shields.io/badge/-share%20on%20linkedin-blue?logo=linkedin&style=for-the-badge)](https://linkedin.com/intent/tweet?text=This%20%22Magic%20Button%22%20share%20stuff%20on%20LinkedIn%20from%20MARKDOWN%0A%0Ahttps%3A%2F%2Flinkedin.javanile.org%2F%0Ahttps%3A%2F%2Fgithub.com%2Fjavanile%2Flinkedin-button%0A%0A%23DEVCommunity%20%23Markdown%20%23LinkedInButton%20%23Socialware) + +
+ +## Get Started + +Grow your project by putting a fantastic button that will allow your users to easily share your work on LinkedIn. Use the online tool to build your button + +> 🔗 [https://linkedin.javanile.org](https://linkedin.javanile.org) + +## Contributing + +Thank you for considering contributing to this project! The contribution guide can be found in the [CONTRIBUTING.md](CONTRIBUTING.md). + +## Code of Conduct + +In order to ensure that the Javanile community is welcoming to all, please review and abide by the [Code of Conduct](CONTRIBUTING.md#code-of-conduct). + +## Security Vulnerabilities + +If you discover a security vulnerability within Javanile, please send an e-mail to Francesco Bianco via [bianco@javanile.org](mailto:bianco@javanile.org). All security vulnerabilities will be promptly addressed. + +## License + +This project is open-sourced software licensed under the [MIT license](LICENSE). diff --git a/index.html b/index.html new file mode 100644 index 0000000..acb0b0c --- /dev/null +++ b/index.html @@ -0,0 +1,99 @@ + + + +LinkedIn Button + + + + +

LinkedIn Button

+

Grow your project by putting a fantastic button that will allow your users to easily share your work on LinkedIn

+ +

Get Started

+

Type to the following area the content to share on LinkedIn

+ + +

Look & Feel

+

Select the style that best fit with your needs

+ + +

Preview

+

This is what the button looks like, click to see how it works

+
+ Share on LinkedIn +
+ +

Copy & Paste

+

Copy this code snippet and put it in your README.md

+ +
+ +
+
+ +

License

+

+ The MIT License (MIT). + Please see License File + for more information. +

+ +
+ + Edit on GitHub + +Fork me on GitHub + + + +