list of lists

2 years ago · f84556c1ef
parent ffb0995078
commit f84556c1ef
5 changed files with 153 additions and 2 deletions
--- a/main.py
+++ b/main.py
@ -9,13 +9,39 @@ prefix = os.environ.get('URL_PREFIX', '')
 port = os.environ.get('PORT', '3000')
 debug = os.environ.get('DEBUG', 'False')
 def list_files(folder, remove_ext=False):
    ''' Read all the functions in a folder '''
    names = []
    for entry in os.scandir(folder):
        # add to the list only proper files
        if entry.is_file(follow_symlinks=False):
            # remove the extension from the filename
            n = entry.name
            if remove_ext:
                n = os.path.splitext(entry.name)[0]
            names.append(n)
    return names
 app = Flask(__name__)
 app.wsgi_app = PrefixMiddleware(app.wsgi_app, prefix=prefix)
@app.route('/favicon.ico')
 def favicon():
    return send_from_directory(os.path.join(app.root_path, 'static'),
                               'favicon.ico', mimetype='image/vnd.microsoft.icon')
@app.route('/')
-def list():
+def home():
-    with open('list.md',"r") as f:
+    listos = list_files('txt', True)
    return render_template('home.html', listos = listos)
@app.route('/<slug>')
 def list(slug):
    with open(f'txt/{slug}.md',"r") as f:
        text = f.read()
    list = markdown(text)
    return render_template('list.html', list = list)
--- a/static/style.css
+++ b/static/style.css
@ -67,3 +67,20 @@ em {
 code {
 	background-color: #eee;
 }
 .home-list {
 	list-style: default;
 }
 .home-list li {
 	display: block;
 }
 .home-list li:after {
 	content: none;
 }
 .home-list a {
 	color: currentColor;
 	text-transform: capitalize;
 }
--- a/templates/home.html
+++ b/templates/home.html
@ -0,0 +1,18 @@
 <!DOCTYPE html>
 <html lang="en">
 	<head>
 		<meta charset="UTF-8" />
 		<meta http-equiv="X-UA-Compatible" content="IE=edge" />
 		<meta name="viewport" content="width=device-width, initial-scale=1.0" />
 		<link rel="stylesheet" href="{{url_for('static', filename='style.css')}}" />
 		<title>list list</title>
 	</head>
 	<body>
 		<h1>List of lists</h1>
 		<ul class="home-list">
 			{% for list in listos %}
 			<li><a href="{{url_for('list', slug=list)}}">{{list}}</a></li>
 			{% endfor %}
 		</ul>
 	</body>
 </html>
--- a/txt/brainstorm.md
+++ b/txt/brainstorm.md
@ -0,0 +1,90 @@
 -   Create a space
 -   to host a list of resources
 -   to explore the documentation of coding related practices
 -   for situated software
 -   and articulate it as a form of care
 <br>
 -   Target public
 -   people in small communities that deal with software
 -   _Examples_
 -   Soupboat
 -   Breadcube
 -   XPUB
 -   Varia
 -   OSP
 -   Konstant
 -   Autonomic
 -   100R
 -   etc
 <br>
 -   Why a space?
 -   Why a list?
 -   Why resources?
 -   Why not just a manual on how to write the perfect software documentation?
 <br>
 -   It's tricky!
 <br>
 -   There is no such a thing as a magic solution for perfect documentation
 -   While there are documentation frameworks that help naming and structuring things, these usually cover just generic approach for technical writing
 -   Situated software has more to offer than a generic approach
 -   sprouting from specific contexts
 -   it can depend on particular knowledges and skills
 -   that differ in each community
 <br>
 -   This diversity means manifold of ideas and ways to document
 -   Hence a list of resources
 -   Someone would call it site specific software
 -   someone else situated knowledges
 <br>
 -   Different resources come from different communities
 -   It is not guaranted for them to be interchangeable
 -   nor to be effective or either meaningful for everyone else
 -   Yet, to be together in this list could be a way to interfere with each other
 -   To create perspective and inspire new strategies
 <br>
 -   So the need for a space where to host the list
 -   What are the feature of this space?
 -   Open to contributions
 -   A bit structured
 -   A bit loose
 -   Is it a platform?
 -   Could it be something different than a website?
 -   Could it work without browser's technology?
 -   Could it have less environmental impact?
 -   Could it be simple and lightweight?
 -   Could it inhabit existing documentations?
 -   A strange hyper tagging system?
 <br>
 -   _Idea_
 -   Federated list
 -   should it follow the concepts of the Fediverse?
 -   several instances of this list
 -   growing from specific groups or cluster of groups
 -   each community curates it's own list
 -   this is interesting
 -   is it different from a normal feed?
 -   yes
 -   because the contents are curated
 -   not just aggregated
 -   how is it structured?
 -   each instance has a server
 -   and offer access for clients
 -   _again_ could this be something different than a website?
 -   actually and ideally
 -   every instance could decide on the form
--- a/txt/situated_doc.md
+++ b/txt/situated_doc.md