How jlnetosci/st-social-media-links works
Project type and purpose
• This is an open-source Python package (a Streamlit “widget” library) called st-social-media-links.
File structure
• Top-level files:
– setup.py (packaging and installation)
– README.md, CHANGELOG.md, LICENSE, .gitignore (project metadata)
– img/ (documentation screenshots)
• Package directory st_social_media_links/:
– __init__.py (package export)
– st_social_media_links.py (main implementation)
There are no separate frontend/backend folders—this is a single library that plugs into Streamlit at runtime.
Main components
a. Client (Streamlit App)
– User’s Python script or notebook that calls SocialMediaIcons(...).
b. st-social-media-links Library
– Entry point: SocialMediaIcons class
– Render method that calls Streamlit APIs
c. Streamlit Runtime
– Streamlit’s server side (executes Python, serializes front-end commands)
d. Font Awesome CDN or CSS
e. Browser
Relationships and interactions
• User Code → Library: imports and instantiates SocialMediaIcons.
• Library → Streamlit Server API: library calls st.markdown or components to send HTML/CSS.
• Streamlit Server → Streamlit Front-End: transports component spec via WebSocket.
• Front-End → Font Awesome: browser fetches CSS/fonts from CDN.
Architectural patterns and principles
• Extensibility: new platforms can be added to the internal mapping.
• Minimal Layers: no database or separate microservice, just a thin integration layer.
Technologies and frameworks
• Python 3.x
• setuptools (setup.py)
• Streamlit (st.markdown or st.components API)
Essential detail to capture
• The two optional rendering modes (sidebar, justify_content).
• The fact that no persistent storage or backend service exists.