Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A blog post about my solving the "water sort puzzle" #113

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

gefjon
Copy link

@gefjon gefjon commented Feb 9, 2023

Likely poorly formatted, because I'm not sure how to preview a rendered version.

incl. some images decribing it.

Likely poorly formatted.
@colescott
Copy link
Member

To preview a rendered version locally you need to install Hugo (somewhat easier with #114) and then run hugo serve. The website should then be available at http://localhost:1313 with live updates.

@gefjon
Copy link
Author

gefjon commented Feb 9, 2023

When I do that, the webpage only shows an unhelpful "Page Not Found," and the terminal prints a bunch of:

WARN 2023/02/09 15:44:27 found no layout file for "HTML" for kind "page": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2023/02/09 15:44:27 found no layout file for "HTML" for kind "home": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2023/02/09 15:44:27 found no layout file for "HTML" for kind "section": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.
WARN 2023/02/09 15:44:27 found no layout file for "HTML" for kind "taxonomy": You should create a template file which matches Hugo Layouts Lookup Rules for this combination.

@colescott
Copy link
Member

Make sure you have the theme submodule cloned either with recursive cloning or git submodule update --init

@gefjon
Copy link
Author

gefjon commented Feb 9, 2023

Ah, that'll do it. Thanks.

@stylewarning
Copy link
Member

Sorry for the delay on getting feedback on this. I discussed the post with Cole and Elias, and we would like it to be included provided it matches the overall style of the previous posts:

  • As written, it feels a little too much like a personal blog post ("I", "me", "on a subway", ...). I think if we were to include it, it would need to be a little more "scholarly" for lack of a better term.
  • Similar to an issue we had in a previous post draft, this post would benefit from a more direct thesis/conclusion/discussion about why Coalton is particularly useful or effective at this problem. (Is it?)
  • It might also be a good idea to structure the post to be a little more "tutorial" in nature. As opposed to being an exposition on how to think about and solve the puzzle, be more of an exposition on how to write a Coalton program to implement a given solution.

Otherwise, it is interesting and simple enough for a blog-post style exposition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants