⏳ Changelog

[visortelle]

Day 25.

• Implemented package dependencies page.

https://user-images.githubusercontent.com/9302460/150811390-dc9a744f-7a56-4ab1-bbe6-ab5485da84c6.mov

[visortelle]

Day 26. Mostly polishing and bug fixing.

• Add 'View on Hackage' button.
• Make progress indication more visible.
• Make items more compact on the package versions, dependencies, and dependents pages.
• Show 404 page if a package is not found on Hackage #14
• Add "Unresponsive UI" disclaimer on the dependents page in case of many items on the page. I will handle it in a better way later. I know the root cause of the problem.

[visortelle]

Day 27. No code today. Mosty planning.

[visortelle]

Day 28.

• Implemented the "Developer tools" page.

  As a side-effect, partially implemented a UI kit for "resources" pages.

  Content will be adjusted later.

  https://hackage-ui.vercel.app/resources/developer-tools

https://user-images.githubusercontent.com/9302460/151396340-50100647-2fc5-4295-b978-5e846f3702f3.mov

[visortelle]

Day 29.

• Renamed the project to haskell-spotlight
• Made it available at http://haskellspot.com/
• Added links to the Chrome extension. The Chrome store review process is so slow compared to the Firefox store. On another side, they pointed me to ways how to reduce the permissions amount needed for the extension. https://chrome.google.com/webstore/detail/haskell-spotlight/npadgihccblidebeflijkcgfpklgalkj
• Home page is in progress.

Bonus. 🤣 Played a bit with illustrations, but my wife said that it would be too much for Haskell community.

[ulysses4ever]

Perhaps it will be more straightforward if the name of the (GH) project was the same as the domain name?

[visortelle]

@ulysses4ever you definitely right. 🙂 Probably next time. It's not as straightforward as you might think. One platform doesn't allow more than 15 chars in name, another requires week-long moderation for a name change, etc.

[yutotakano]

My understanding was that, after completion, this UI would replace Hackage at the existing domain (hackage.haskell.org), with help from the Haskell Foundation to transition, using the common backend API.

Did I misunderstand the goal?

[visortelle]

@yutotakano you understood the initial goal right. After some investigation, combining several sub-projects into one seemed like a good idea for me. Let's see what happens and if I was right. 🙂

[visortelle]

Day 30.

• Playing with the servant to start implementing the playground. Repository is here: https://github.com/haskell-spotlight/haskell-playground

[visortelle]

Day 31.

• Continue to work on the playground. Tomorrow plan to start the playground web widget.

[visortelle]

Day 32.

• Continue on the playground.

As I want to make it suitable for courses, it should be able to run tests. A lot of build-related stuff ahead. 😓 Most likely will pick the top 100 packages to support as Rust's playground does.

K8s or a single fat machine with docker is one more item on the agenda. Probably the second one from start. 🙂 Need to think about resource constraints.

Some progress:

https://user-images.githubusercontent.com/9302460/151823078-51fc7e0e-5b8d-41fd-9d01-634045dbdfde.mov

[visortelle]

Day 33.

• Continue working on the playground.

There is a lot of mechanical coding ahead. Probably the same boring "nothing to show" message will be here for the next 2-3 days. 🙂

[visortelle]

Days ☀️34, ☀️35, ☀️36, ☀️37, ☀️38, ☀️39 (6 days, really ⁉️) status report. 😅

• I'm still working on the playground.

  A lot of moving parts here ⚙️.

  Mostly finished work on API and internal reverse-proxy for a single sandbox. Implemented minimal UI. Tested ability to build sandboxes with a custom set of dependencies, commands, and checks.

  I like the intermediate result, but I won't set any deadlines. Need to assemble all the parts first.