Enhancement: Add Server-Rendered Framework Integration (Rails / Django / Laravel) — demo page section and CDN usage guide
I maintainer di solito rispondono entro 1 giorno
@Abhinandankaushik ci sta già lavorando.
Dal 21/3/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
🎯 Direction
SocialShareButton is a lightweight, zero-dependency, framework-agnostic social sharing component. Ruby on Rails, Django, and Laravel are the three most popular server-rendered web frameworks — they generate HTML on the server and send it to the browser, making CDN-based widget integration the standard approach. This issue adds a single combined demo section covering all three, since the integration pattern is near-identical across them.
📹 See the button in action: https://youtu.be/cLJaT-8rEvQ?si=CLipA0Db4WL0EqKM
📁 Files to Create / Modify
ℹ️ No New Wrapper File Needed
Integration is done by placing CDN <link> and <script> tags in the server-rendered base layout template of each framework. No JavaScript wrapper is required.
✅ Existing File: index.html — Add Server-Rendered Frameworks Section
Add a new section with:
- Section heading:
🖥️ Server-Rendered Frameworks (Rails / Django / Laravel) - A brief note that the pattern is the same across all three — include CSS in
<head>, JS before</body>, initialize with a script
Ruby on Rails (app/views/layouts/application.html.erb):
<%# In <head> %>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/social-share-button/dist/social-share-button.css">
<%# Before </body> %>
<script src="https://cdn.jsdelivr.net/npm/social-share-button/dist/social-share-button.js"></script>
<div id="share-button"></div>
<script>
new SocialShareButton({
container: '#share-button',
url: window.location.href,
title: document.title,
theme: 'dark',
buttonText: 'Share'
});
</script>
Django (templates/base.html):
{# In <head> #}
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/social-share-button/dist/social-share-button.css">
{# Before </body> #}
<script src="https://cdn.jsdelivr.net/npm/social-share-button/dist/social-share-button.js"></script>
<div id="share-button"></div>
<script>
new SocialShareButton({
container: '#share-button',
url: window.location.href,
title: document.title,
theme: 'dark',
buttonText: 'Share'
});
</script>
Laravel (resources/views/layouts/app.blade.php):
{{-- In <head> --}}
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/social-share-button/dist/social-share-button.css">
{{-- Before </body> --}}
<script src="https://cdn.jsdelivr.net/npm/social-share-button/dist/social-share-button.js"></script>
<div id="share-button"></div>
<script>
new SocialShareButton({
container: '#share-button',
url: window.location.href,
title: document.title,
theme: 'dark',
buttonText: 'Share'
});
</script>
✅ Acceptance Criteria
- No new wrapper file required — integration is template/CDN only
-
index.htmlupdated with a server-rendered frameworks section containing separate code snippets for Rails, Django, and Laravel - Copy-to-clipboard button present on new code blocks in
index.html - README updated to mention Rails, Django, and Laravel as supported integration patterns
⚠️ Planned — Not Final
This issue represents a planned enhancement and is not guaranteed to be implemented. It may be dropped if it does not align with the repository's direction. Before opening a pull request, please discuss with the maintainers in this issue thread.
- Lingua principale
- TypeScript
- Stelle
- 29
- Fork
- 74
- Merge medio
- 8h 52m
- PR unite (30g)
- 4
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di AOSSIE-Org/SocialShareButton
-
Improvement: Add try-catch blocks for better error handling in social-share-button.jsForse già presa @afzalansari12 l’ha presa 118 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
AOSSIE-Org/SocialShareButton#132 · 5 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Remove or guard console.error statement in production build (src/social-share-button.js)Forse di nuovo libera @Akshat0125 l’ha presa 244 giorni fa e non c’è nessuna pull request aperta. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
AOSSIE-Org/SocialShareButton#43 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[FEATURE]: Add Google Tag Manager (dataLayer.push) Analytics AdapterForse già presa @Devnil434 l’ha presa oggi. Apertaenhancement
Difficoltà 3/5 1-2 giorni Idoneità per principianti 74/100
AOSSIE-Org/SocialShareButton#270 ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG]: React, Preact and Qwik share buttons keep sharing the first page's link after navigationForse già presa @atharva134kadam l’ha presa 1 giorno fa. Apertabug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
AOSSIE-Org/SocialShareButton#266 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[FEATURE]: Add Scroll-to-Top Button with Smooth AnimationForse già presa @zaibamachhaliya l’ha presa 92 giorni fa. Apertaenhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
AOSSIE-Org/SocialShareButton#240 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di AOSSIE-Org/SocialShareButton
Issue simili
-
ready-for-agent
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
LucasSantana-Dev/Lucky#3257 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
danielmiessler/LifeOS#2894 ·
I maintainer di solito rispondono entro 5 giorni
-
enhancement frontend good first issue help wanted testing-infrastructure
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 2 giorni
-
enhancement follow-up
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno