Project

General

Profile

Feature #35

Create MVP website for the project

Added by koszko 5 months ago. Updated 4 days ago.

Status:
New
Priority:
High
Assignee:
Start date:
07/01/2021
Due date:
% Done:

0%

Estimated time:

Description

We need better online presence.

This is also going to become a separate project at this tracker at some point.

It already happened

History

#1

Updated by koszko 4 months ago

🤦

When renewing the VPS I used the opportunity and coded the fix for credit card payment confirmation page of my bank. I wanted to additionally remove the red ugly javascript notice on that page but for some reason this didn't work properly. I renewed my VPS but needed to do some more experiments with removing the js notice and decided to do a dummy purchase I would cancel afterwards. I went with a purchase of `hachette-hydrilla.org' domain (all better ones were taken and I didn't care because I was going to cancel the purchase anyway). Suddenly, the purchase completed without my bank page showing up ;_;

As a result of this accident we have a `hachette-hydrilla.org' domain for 1 year

#2

Updated by jahoti 4 months ago

I suppose that's one less problem we have to solve! In all seriousness, it's not a bad choice; the only problem is that you're now out of pocket, of course. How much did you pay, and do you need reimbursement?

#3

Updated by koszko 4 months ago

the only problem is that you're now out of pocket, of course. How much did you pay, and do you need reimbursement?

It's ok. Domains are cheap (compared to VPS or commercial SSL certs). I just updated the application with regard to domain price (btw, the domain now seems cheaper than it showed to me when I checked the price before).

Btw, just to be sure, by including "Tasks list" in the attachment you mean moving the list from below "Current intended uses:"? It seems we could also move the budget table to that file. And in the application itself we could then just say the money is going to fund the "infrastrcture and development of Hachette and Hydrilla". Does that seem good?

#4

Updated by jahoti 4 months ago

It's ok. Domains are cheap (compared to VPS or commercial SSL certs). I just updated the application with regard to domain price (btw, the domain now seems cheaper than it showed to me when I checked the price before).

I just realized I was thinking of the price for a VPS (thank God you weren't up to renewing that :`). Even better that it was cheaper!

Btw, just to be sure, by including "Tasks list" in the attachment you mean moving the list from below "Current intended uses:"? It seems we could also move the budget table to that file. And in the application itself we could then just say the money is going to fund the "infrastrcture and development of Hachette and Hydrilla". Does that seem good?

Exactly, and now that you mention it moving the budget table too would be a great idea! However, as the application is meant to be "self-contained", the statement in there should probably stay as is (minus table). In fact, it might even be useful to add a few "stretch goals" to that statement with some concrete examples of what more we could achieve, if there's any in particular that stand out (it's probably best I don't try that, however, given that my "estimation" for how long would be a good start was 12 months :).

#5

Updated by jahoti 4 months ago

  • Assignee set to 0gitnick

Descriptive, not prescriptive; feel free to change this assignment.

#6

Updated by koszko 4 months ago

  • Project changed from Haketilo to Project website
  • Description updated (diff)
#7

Updated by 0gitnick 5 days ago

  • Subject changed from create a website for the project to Create MVP website for the project
#8

Updated by koszko 4 days ago

Btw, we now have to decide whether the website should be part of Hydrilla-served content or a separate project.

My plan for Hydrilla is to have it serve both the JSON API (which Haketilo uses) and HTML pages which humans can browse. The API idea is already described on Hydrilla Wiki and mostly implemented as a Flask app in this git repo. For the HTML part, consider what is currently served at https://hachette-hydrilla.org/. That page lists currently available javascript replacements and is generated using a shell script. Ultimately, we'd like an equivalent of that (and also a separate page with details of each replacement) to be served by Hydrilla software itself.

So, should the website itself also be served by Hydrilla?
Pros:

  • We'd just have to maintain 1 Flask app and nothing besides it. No copy-pasting of code, no doubling of packaging work.
  • It'd be easier to integrate both for fancy features, e.g. having Hydrilla main site always display a random package from the repo.

Cons:

  • We'd be forced to use the same technology that is employed in Hydrilla - Flask.
  • At some point we're likely to have to maintain multiple versions of the JSON API for compatibility reasons. The server would need to be running multiple versions of Hydrilla and having the website included would make setup of this a bit more complex.

I am still not sure what is the best approach, so please share your thoughts. Regardless of what we choose, I think it'd be good to give both Hydrilla and the website the same look&feel

Also available in: Atom PDF