How bfiliks/intertextuality-network-aa-lit works
Project type and purpose
• This is a static visualization pipeline / static site project.
• Purpose: take a curated CSV of intertextual connections, run a Python script to generate an interactive Plotly network graph (interactive.html), and bundle it with static assets (PDF poster, slide deck, images, index.html) for local viewing or web deployment.
File structure
• Top-level files:
• edges.csv → data source of book‐to‐book connections
• build_network.py → Python script that reads edges.csv and outputs the visualization
• index.html → landing page or redirector
• LICENSE, README.md → documentation
• assets/ directory: static outputs and supporting materials:
• interactive.html (generated Plotly graph)
• PDF, PPTX, SVG, PNG poster and QR code
• No “backend” server or database—everything is file‐based.
README for additional insights
• The script regenerates assets/interactive.html from edges.csv.
• Uses Plotly (client‐side JavaScript) for interactivity and theme filters.
• Deployment targets: GitHub Pages, Netlify, Vercel, or Hugging Face Spaces as a static site.
a. Main components:
1. Data Source
• edges.csv (CSV file)
2. Processing Engine
• build_network.py (Python script + libraries: pandas, plotly)
3. Generated Artifacts
• assets/interactive.html (HTML + JS)
• assets/*.png/.svg/.pdf/.pptx (static assets)
• index.html
4. Hosting Layer
• GitHub Pages / Netlify / Vercel / Static file server
5. Client
• Web Browser rendering HTML/JS
b. Relationships & data flow:
• Static assets and index.html are served alongside interactive.html
• Hosting layer serves static files to the browser
• Browser fetches interactive.html, loads Plotly JS, reads embedded JSON graph data, renders interactive network
c. Architectural patterns & design principles:
• Batch pipeline: regenerate on demand via CLI (no live server)
• Static site architecture: pre-render assets, serve over CDN or GitHub Pages
• Separation of concerns: data (CSV) vs. processing (Python) vs. presentation (HTML/JS)
d. Key technologies:
• Python (pandas, plotly)
• CSV file as data store
• Plotly.js for client-side graph rendering
• GitHub Pages / Netlify static hosting
• Standard web stack: HTML/CSS/JS
Final advice
• Be exhaustive in capturing all static files your pipeline depends on (e.g., index.html, poster assets).
• Don’t overcomplicate: break the project into Data, Build, Output, Hosting, Client.
• Keep it clean: separate offline build steps from online serving steps visually.