Simplify site with new static layout

[atishp04]

Summary

• remove the old Jekyll-based site
• create minimal static pages for home, talks, blog and OSS links
• add a small stylesheet
• update README to describe the new layout

Testing

• bundle exec jekyll build (fails: Could not locate Gemfile)

---

https://chatgpt.com/codex/tasks/task_e_6860dffef44083318690af606bbb8684

Summary by Sourcery

Simplify the personal website by replacing the Jekyll-based setup with a set of static HTML pages and a lightweight CSS layout.

New Features:

• Add static HTML pages for home, talks, blog, and open-source sections.
• Include a minimal stylesheet using Bootstrap for basic styling.

Documentation:

• Update README to describe the new static layout, page structure, and usage.

Chores:

• Remove all Jekyll configuration, layouts, posts, and dependencies including Gemfile and related assets.

[sourcery-ai]

Reviewer's Guide

Replace the Jekyll-based site with a streamlined set of static HTML pages styled via Bootstrap and a small custom stylesheet, remove all legacy Jekyll files, and update documentation to reflect the new layout.

File-Level Changes

Change	Details	Files
Removed legacy Jekyll site structure	Deleted Jekyll config, data, and layout files Removed all Sass sources and static asset directories Deleted posts, categories, and project content files	Gemfile Gemfile.lock _config.yml _data/projects.json _includes/project_tags.html _includes/share-page.html _layouts/compress.html _layouts/default.html _layouts/page.html _layouts/post.html _layouts/posts_by_category.html _layouts/project.html _layouts/project_single.html _posts/2018-09-28-Fedora-Gnome-Desktop-RISCV.markdown _posts/Fedora_EDK2_Unleashed.markdown _project/cool-project.md _sass/_base.scss _sass/_layout.scss _sass/_syntax-highlighting.scss about.md category/bash.md category/codefights.md category/django.md category/jekyll.md category/others.md category/python.md category/raspberry.md category/ruby.md category/security.md feed.xml projects.md sitemap.xml static/css/bootstrap.min.css static/css/main.css static/css/projects.css static/css/super-search.css static/css/syntax.css static/css/thickbox.css static/js/bootstrap.min.js static/js/projects.js static/js/super-search.js static/js/thickbox-compressed.js
Introduced minimal static HTML pages	Added new index.html with header, nav, intro section, and footer Created talks.html, blog/index.html, and oss.html with consistent layout Replaced dynamic pagination and Liquid templating with static content	index.html talks.html blog/index.html oss.html
Added custom stylesheet and Bootstrap integration	Created css/style.css for basic site styling Linked Bootstrap CDN and custom CSS in all pages	css/style.css index.html talks.html blog/index.html oss.html
Updated project documentation	Rewrote README to describe static layout and available pages Removed references to Jekyll theme and credits Added section listing the new static pages	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.