cobalt-org / cobalt-org.github.io Goto Github PK

This came up in cobalt-org/cobalt.rs#640

Hi,

I just spotted a small typo in layouts.md:

See what variables are avaialble.

Regards,
Yvan

I noticed http://cobalt-org.github.io/ doesn't enforce HTTPS, which I would especially recommend since there are commands people will be copying and pasting.

See cobalt-org/cobalt.rs#596 (comment)

Did no-one check the deployed site? The logo is missing. Doesn't look like this is related to issue #2 either.

$ wget --server-response -O /dev/null http://cobalt-org.github.io/public/images/logo.svg
--2017-09-30 08:58:58--  http://cobalt-org.github.io/public/images/logo.svg
Resolving cobalt-org.github.io (cobalt-org.github.io)... 151.101.17.147, 2a04:4e42:4::403
Connecting to cobalt-org.github.io (cobalt-org.github.io)|151.101.17.147|:80... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 404 Not Found
  Server: GitHub.com
  Content-Type: text/html; charset=utf-8
  ETag: "585337e5-247c"
  Access-Control-Allow-Origin: *
  Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
  X-GitHub-Request-Id: 1ABA:14C0:1BD2A88:277AEDF:59CF4EC2
  Content-Length: 9340
  Accept-Ranges: bytes
  Date: Sat, 30 Sep 2017 07:58:58 GMT
  Via: 1.1 varnish
  Age: 0
  Connection: keep-alive
  X-Served-By: cache-lcy1148-LCY
  X-Cache: MISS
  X-Cache-Hits: 0
  X-Timer: S1506758339.851136,VS0,VE84
  Vary: Accept-Encoding
  X-Fastly-Request-ID: e9af20c1e341fb41ce8069bd3135ac35fb72d6de
2017-09-30 08:58:58 ERROR 404: Not Found.

Split out from cobalt-org/cobalt.rs#179

@ ethagnawl

The user can be presented with the (preferred) option of installing via cargo

I just installed Cobalt for the first time and had this same thought. I was able to find the package on https://crates.io and install it using cargo install cobalt-bin, but a snippet or link would be very helpful. It would reduce friction and prevent users from accidentally installing the other cobalt package.

When seeing the website, I can't help myself but think that it needs an overall refresh:

• the pages have different sizes
• the landing page is not really appealing, the footer is too high
• Contribute, send directly to GitHub which is harsh. I think an introduction page to present the different repos (liquid and cobalt) and the gitter
• the Usage page is not very clear on publish: it sounds like after publish the post is visible but we still need a build to generate the post

and I didn't write everything down yet…

Thoughts?

Linux

• libssl-dev
• build-essential

Windows

• sass: Windows 8.1 SDK
• syntect:

Commits are made to source but they are never deployed to the master branch.

In travis

0.03s$ [ $TRAVIS_BRANCH = source ] &&
    [ $TRAVIS_PULL_REQUEST = false ] &&
    cobalt import --branch master &&
    git config user.name "Cobalt Site Deployer" &&
    git config user.email "[email protected]" &&
    git push -fq https://${GH_TOKEN}@github.com/${TRAVIS_REPO_SLUG}.git master
[info]   Using config file .cobalt.yml
[info]   Importing build to master
[info]   Import successful
error: src refspec master does not match any.
error: failed to push some refs to 'https://[secure]@github.com/cobalt-org/cobalt-org.github.io.git'

for example, if we use {{ collections.posts.pages[0] }}, the error occurs while build

Error: build command failed
Caused by: Failed to render content for "index.html"
Caused by: liquid: Invalid index
with:
index=collections.posts.pages

Here is a list of items that need to be completed before we can release the site:

• Setup travis-ci with cobalt and github pages
• Style the site. Anyone who wants to do this leave a comment! 😄
• Create example pages
  • Basic example of a cobalt site.
  • Basic blogging website
  • More complicated blogging site with use of tags

Feel free to let me know if I missed something.

• The logo taking up a lot of space works well on the landing page but no where else
• The columns are too narrow
• Tables look ugly
• The same <li> for menus does not work for page content
• Each page should have a link back to the page source on githuib for easy contributing

"Cobalt has default support for Sass since v0.12.2."

placing .scss file in a sass (and _sass) directory does little.

is there a built in sassc like zola?

There's absolutely nothing on cobalt-org/cobalt.rs#684, as far as I can tell… even if you don't add it to the reference right now, it'd be nice to know how to use this feature.

Information about what cobalt serve and cobalt build do is spread out between their usage, the docs on Assets/Pages/Posts, and the Configuration page. But site generation is the central feature of an SSG, it should be documented in one place instead of users running these commands to infer what they do.

I'll work on a merge request that adds as "Site generation" page.

See https://github.com/gjtorikian/html-proofer

Hey,

I'm thinking about switching from jekyll to cobalt and I find your github workflows for cobalt.rs homepage very interesting. Could I reuse them for my personal website? What is the license for this code?

btw: cobalt.rs is awesome 👍, great replacement for jekyll imho

Its hosted independent of anything else

There is a windows version

Since the latest re-run of cobalt on the website, it isn't rendering correctly.

Looking closer, it appears the assets were either not pulled into "master" or that they somehow got messed up ("css", "png", and "svg" files in the root).

See cobalt-org/cobalt.rs#387

This means the user has reached an inotify cap. They can either

• Run cobalt serve --no-watch
• Raise their inotify cap.

http://cobalt-org.github.io/docs/usage/ says serve:

Serve your site at 127.0.0.1:3000

$ cobalt serve
# Include drafts
$ cobalt serve --drafts

This provides live reload; it will re-generate your site as you add or change content.

Use the --host argument to listen on a different address (ex. 0.0.0.0/INADDR_ANY); the default is localhost. Use --port (or -P) to listen on a different TCP port number (default: 3000).

but cobalt serve actually uses the first available port in the range 1024..9000 (see get_available_port()). It prints the hostname and port it listens on to stderr, e.g.

Server Listening on http://localhost:1025

cobalt serve --help doesn't say it defaults to 3000, though it looks like that if get_available_port() fails, cobalt will use port 3000 (and probably fail)

https://cobalt-org.github.io/docs/posts/ states one needs to compile with pagination-unstable, however, this appears to not be true, as that feature doesn't even exist (and neither does pagination or anything like that). Is pagination enabled by default now?

Support for minifying pages and assets was added in 0.16.5 through cobalt-org/cobalt.rs#854. However, the documentation for this is missing so far.

We also have a problem where <li> in some cases is used for menus and doesn't have bullets but in other cases its used as a bullet list but because of the menus, no bullets show up.

There is no documentation on syntax highlighting themes, apart from the default value.

I'm searching for SSG for documentation of my project...

And, this project's "welcome" page doesn't impress me at all. Normally, I skip such projects immediately, but I see you've gone through effort to write lots of docs,... So, at least I'll give you hint, how to make it more "welcoming",... Both github project's README.md and http://cobalt-org.github.io/ are missing overview of the most important usage characteristics.

Adding a simple list of characteristic features, like:

• written in Rust for speed and safety,
• install via cargo and packaged in various distributions,
• markup language: Markdown (can be combined with custom HTML),
• uses Liquid template engine,
• ... N/A ...

Also, stick to simple list, with simple short text pointing to docs with more information. Also, you might add opinion to facts, ie. "written in Rust" is fact, and for safety and speed is (potentially true) opinion. But, facts are important.

Knowing capabilities and features of project is crucial in making decision, whether to pick some software or not. Make potential users know, what the project offers :-)