diff --git a/_config.yml b/_config.yml index 1a7bbf1b6..653db8087 100644 --- a/_config.yml +++ b/_config.yml @@ -3,16 +3,16 @@ # # Name of your site (displayed in the header) -name: Reverie +name: ModSec'20 # Name of the author -author: Amit Merchant +author: # Short bio or description (displayed in the header) -description: An elegant Jekyll theme +description: A MODELS workshop # URL of your avatar or profile pic (you could use your GitHub profile pic) -avatar: /images/reverie.png +avatar: /images/modsec.png # # Flags below are optional @@ -21,15 +21,15 @@ avatar: /images/reverie.png # Includes an icon in the footer for each username you enter footer-links: dribbble: - email: amit.d.merchant@gmail.com + email: facebook: flickr: - github: amitmerchant1990/reverie + github: instagram: linkedin: pinterest: - rss: rss - twitter: amit_merchant + rss: + twitter: stackoverflow: youtube: # channel/ or user/ googleplus: # anything in your profile username that comes after plus.google.com/ @@ -41,24 +41,25 @@ footer-links: disqus: # Enter your Google Analytics web tracking code (e.g. UA-2110908-2) to activate tracking -google_analytics: UA-43339302-11 +google_analytics: # Your website URL (e.g. http://amitmerchant1990.github.io or http://www.amitmerchant.com) # Used for Sitemap.xml and your RSS feed -url: http://www.amitmerchant.com/reverie -enforce_ssl: https://www.amitmerchant.com/reverie +url: +enforce_ssl: # If you're hosting your site at a Project repository on GitHub pages # (http://yourusername.github.io/repository-name) # and NOT your User repository (http://yourusername.github.io) # then add in the baseurl here, like this: "/repository-name" -baseurl: "/reverie" +baseurl: "" # # !! You don't need to change any of the configuration flags below !! # -permalink: /:title/ +permalink: /:basename/ + # The release of Jekyll Now that you're using version: v1.2.0 diff --git a/_includes/meta.html b/_includes/meta.html index b54766fb7..4a0800265 100644 --- a/_includes/meta.html +++ b/_includes/meta.html @@ -23,4 +23,3 @@ {% endif %} - diff --git a/_layouts/default.html b/_layouts/default.html index afac3ec49..21b26f889 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -27,10 +27,10 @@

{{ site.name }}

diff --git a/_pages/about.md b/_pages/about.md deleted file mode 100644 index e8c5fd239..000000000 --- a/_pages/about.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -layout: page -title: About -permalink: /about/ ---- - -[Reverie](https://github.com/amitmerchant1990/reverie) is a Jekyll theme which is simple and opinionated. It's actually a fork of [jekyll-now](https://github.com/barryclark/jekyll-now) with some additional features and personal touches which I've implemented to suit my needs for [my blog](https://www.amitmerchant.com). - -This is a plug-and-play Jekyll theme which you can use on GitHub Pages without even setting up a local environment. - -## Features - -- Command-line free fork-first workflow, using GitHub.com to create, customize and post to your blog -- Fully responsive and mobile optimized base theme -- Sass/Coffeescript support using Jekyll 2.0 -- Free hosting on your GitHub Pages user site -- All the SEO goodies comes in-built -- Markdown blogging -- Syntax highlighting using Pygments - - [Dracula syntax theme](https://draculatheme.com/) included -- Disqus commenting -- Google Analytics integration -- Fuzzy search across blog posts -- Pagination of posts works out-of-the-box. -- Categorize posts out-of-the box -- RSS Feed -- In-built sitemap - -Learn more about it [here](https://github.com/amitmerchant1990/reverie) on how to get started. diff --git a/_pages/categories.md b/_pages/categories.md deleted file mode 100644 index eccf3624d..000000000 --- a/_pages/categories.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -layout: page -permalink: /categories/ -title: Categories ---- - - -
-{% for category in site.categories %} -
- {% capture category_name %}{{ category | first }}{% endcapture %} -
-

- -

{{ category_name }}

- - {% for post in site.categories[category_name] %} - - {% endfor %} -
-{% endfor %} -
\ No newline at end of file diff --git a/_pages/getting-started.md b/_pages/getting-started.md deleted file mode 100644 index f7946a125..000000000 --- a/_pages/getting-started.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -layout: page -title: Getting started with Reverie -permalink: /getting-started/ ---- - -### Step 1) Fork Reverie to your User Repository - -Fork [this repository](https://github.com/amitmerchant1990/reverie), then rename the repository to `yourgithubusername.github.io`. - -Alternatively, you can use [Use this template](https://github.com/amitmerchant1990/reverie/generate) button if you want to create a repository with a clean commit history which will use Reverie as a template. - -Your Jekyll blog will often be viewable immediately at (if it's not, you can often force it to build by completing step 2) - -### Step 2) Customize and view your site - -Enter your site name, description, avatar and many other options by editing the `_config.yml` file. You can easily turn on Google Analytics tracking, Disqus commenting and social icons here. - -Making a change to `_config.yml` (or any file in your repository) will force GitHub Pages to rebuild your site with jekyll. Your rebuilt site will be viewable a few seconds later at - if not, give it ten minutes as GitHub suggests and it'll appear soon. - -### Step 3) Publish your first blog post - -Create a new file called `/_posts/2019-2-13-Hello-World.md` to publish your first blog post. That's all you need to do to publish your first blog post! This [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) might come in handy while writing the posts. - -> You can add additional posts in the browser on GitHub.com too! Just hit the Create new file button in `/_posts/` to create new content. Just make sure to include the [front-matter](http://jekyllrb.com/docs/frontmatter/) block at the top of each new blog post and make sure the post's filename is in this format: year-month-day-title.md - -## Using Categories in Reverie - -You can categorize your content based on `categories` in Reverie. For this, you just need to add `categories` in front matter like below: - -For adding single category: - -```md -categories: JavaScript -``` - -For adding multiple categories: - -```md -categories: [PHP, Laravel] -``` - -The contegorized content can be shown over this URL: - -## RSS - -The generated [RSS feed](https://en.wikipedia.org/wiki/RSS) of your blog can be found at . You can see the example RSS feed over [here](https://www.amitmerchant.com/reverie/feed). - -## Sitemap - -The generated sitemap of your blog can be found at . You can see the example sitemap feed over [here](https://www.amitmerchant.com/reverie/sitemap). diff --git a/_pages/index.md b/_pages/index.md new file mode 100644 index 000000000..4fa7ee952 --- /dev/null +++ b/_pages/index.md @@ -0,0 +1,96 @@ +--- +layout: page +title: First International Workshop on Modeling and Security +permalink: / +--- + +Integrating security in all the design and development steps of a software is an increasingly complex challenge. +Choosing the right language, adopting a correct architecture, building a strong test suite, maintaining the software +after deployment: these are some of the tasks that impacts the overall security of a software. In today's environment, +security cannot be an afterthought and must be integrated from the get-go as it affects the complete life cycle +of a software. One wrong doing can have catastrophic consequences from the leaks of personal data to the shutdown of +an essential service that others are depending on. + +Securely building and maintaining a software throughout its lifetime requires unified effort from many different domains. +One decision early on can cascade and impact the later development stages. Yet, the research done in different fields +feels disconnected as each of them has its own set of objectives and use cases. +We believe that both the software engineering and the security communities need a workshop to meet up and align past and +future research activities. +Methods and techniques in one domain could be leveraged or adapted in another one to better protect modern software and +we feel a workshop is needed to engage the discussion and incite collaboration from researchers in fields that do not +necessarily communicate with one another. + +This first edition of the ModSec Workshop is an attempt to make the Software Engineering community and the Security +community meet and discuss about their own views of models and security. It aims at defining the future directions of +this important research area that will find new applications in the upcoming years by bringing together world experts + in the fields for an intense one-day workshop. + +# Call for papers and demos +We invite you to submit a paper and join us at the ModSec workshop, which will be held on October 18 2020 in Montreal, +Canada. +We are excited to welcome original work describing research, visions, or demos in all areas at the intersection +of software engineering and security for this workshop. +We are interested especially in contributions that look at modeling security either from the software engineering perspective, +or the security point of view (with threats models, attackers and defenders models). + +We accept both longer papers on mature/completed work in a research track, as well as shorter papers on work in +progress or work that has yet to begin in a vision track. This decision to accept both types of submissions aims to +include researchers at all stages of their career and at all stages of their projects. + +We also invite submissions to present a tool during the workshop in a special demo track that can demonstrate interest for +workshop's participants. + + +Topics of interest include, but are not limited to, the following: +- **Modeling Security:** Threat models and attackers, Secure system requirements and architecture, Software variability and diversity for security +- **Security in the Development Process:** Security testing methodologies, Patch and update management, Security in lifecycle development +- **Security in Machine Learning-based Systems:** Security methodologies for machine learning, adversarial machine learning, modeling security in machine learning, modeling machine learning +- **Secure Modeling:** Modeling with security aspects, V&V, Secure Software Variability + +We have observed that the most effective workshops are those that encourage discussion between attendees. +Each paper presentation will be followed by about 10 minutes of discussion to promote engagement and helpful feedback. + +For accepted papers, at least one author must attend the workshop. + + + +### Submission Instructions +Submissions must be uploaded through EasyChair at the following link + +[https://easychair.org/conferences/?conf=modsec2020](https://easychair.org/conferences/?conf=modsec2020) + +We accept three types of publications: + +- **Research track**: Full research papers (10 pages) present a novel, innovative approach to one of the workshop’s topics. +References may be collected in 2 additional pages. +- **Vision track**: Short papers (5 pages) present new ideas or early-stage research related to one of the workshop’s topics. +References may be collected in 1 additional page. +- **Demo track**: Demo papers (2 pages) introduce a tool that allows the modelling of security aspects or + that can demonstrate an interest for workshop’s participants. We expect tool presentation to be 15 minutes or less during the workshop. + +All submissions must be in PDF and in the ACM format. Formatting instructions are available at +[https://www.acm.org/publications/proceedings-template](https://www.acm.org/publications/proceedings-template) for both LaTeX and Word users. +LaTeX users must use the provided acmart.cls and ACM-Reference-Format.bst without modification, enable the conference format in the preamble of the document (i.e., \documentclass[sigconf,review]{acmart}), and use the ACM reference format for the bibliography (i.e., \bibliographystyle{ACM-Reference-Format}). +The review option adds line numbers, thereby allowing referees to refer to specific lines in their comments. + +All accepted workshop papers will be published in the ACM Digital Library along with the main conference’s proceedings. + +# Important dates +Paper submission deadline: **July 24, 2020** + +Notification of acceptance: August 14, 2020 + +Workshop dates: October 18-19, 2020 + +# Venue and Registration +ModSec is co-located with the IEEE 23rd International Conference on Model Driven Engineering Languages and Systems +(MODELS) in Montreal, Canada. The workshop will take place before the main conference. Registration details will be +handled by the main conference and will be posted closer to the event itself on their website. + +# Organization +### Workshop co-chairs +- [Moussa Amrani](https://directory.unamur.be/staff/mamrani), Université de Namur (Belgique) +- [Pierre Laperdrix](https://plaperdr.github.io/), CNRS, CRIStAL (France) +- [Paul Temple](https://templep.github.io/), Université de Namur (Belgique) + +### Program committee (to be communicated) diff --git a/_pages/search.md b/_pages/search.md deleted file mode 100644 index b89ec6a9e..000000000 --- a/_pages/search.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -layout: page -title: Search -permalink: /search/ ---- - -
- -
    -
    - - - - \ No newline at end of file diff --git a/_posts/2019-02-13-introducing-reverie-jekyll-theme.md b/_posts/2019-02-13-introducing-reverie-jekyll-theme.md deleted file mode 100644 index 8b1075da4..000000000 --- a/_posts/2019-02-13-introducing-reverie-jekyll-theme.md +++ /dev/null @@ -1,87 +0,0 @@ ---- -layout: post -title: Introducing Reverie - A ridiculously elegant Jekyll theme -categories: [Miscellaneous, Jekyll] ---- - -[Reverie](https://github.com/amitmerchant1990/reverie) is a [Jekyll](https://jekyllrb.com/)-powered theme which is simple and opinionated. It's actually a fork of [jekyll-now](https://github.com/barryclark/jekyll-now) with some additional features and personal touches which I've implemented to suit my needs for my blog. - -This is a plug-and-play Jekyll theme which you can use on GitHub Pages without even setting up a local environment. - -![](/images/reverie-demo.png) - -## Features overview - -- Command-line free fork-first workflow, using GitHub.com to create, customize and post to your blog -- Fully responsive and mobile optimized base theme -- Sass/Coffeescript support using Jekyll 2.0 -- Free hosting on your GitHub Pages user site -- All the SEO goodies comes in-built -- Markdown blogging -- Syntax highlighting using Pygments - - [Dracula syntax theme](https://draculatheme.com/) included -- Disqus commenting -- Google Analytics integration -- Fuzzy search across blog posts -- Pagination of posts works out-of-the-box. -- Categorize posts out-of-the box -- RSS Feed -- In-built sitemap - -
    - -
    - -## Using Reverie on GitHub Pages - -### Step 1) Fork Reverie to your User Repository - -Fork [this repository](https://github.com/amitmerchant1990/reverie), then rename the repository to `yourgithubusername.github.io`. - -Alternatively, you can use [Use this template](https://github.com/amitmerchant1990/reverie/generate) button if you want to create a repository with a clean commit history which will use Reverie as a template. - -Your Jekyll blog will often be viewable immediately at (if it's not, you can often force it to build by completing step 2) - -### Step 2) Customize and view your site - -Enter your site name, description, avatar and many other options by editing the `_config.yml` file. You can easily turn on Google Analytics tracking, Disqus commenting and social icons here. - -Making a change to `_config.yml` (or any file in your repository) will force GitHub Pages to rebuild your site with jekyll. Your rebuilt site will be viewable a few seconds later at - if not, give it ten minutes as GitHub suggests and it'll appear soon. - -### Step 3) Publish your first blog post - -Create a new file called `/_posts/2019-2-13-Hello-World.md` to publish your first blog post. That's all you need to do to publish your first blog post! This [Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) might come in handy while writing the posts. - -> You can add additional posts in the browser on GitHub.com too! Just hit the Create new file button in `/_posts/` to create new content. Just make sure to include the [front-matter](http://jekyllrb.com/docs/frontmatter/) block at the top of each new blog post and make sure the post's filename is in this format: year-month-day-title.md - -## Using Categories in Reverie - -You can categorize your content based on `categories` in Reverie. For this, you just need to add `categories` in front matter like below: - -For adding single category: - -```md -categories: JavaScript -``` - -For adding multiple categories: - -```md -categories: [PHP, Laravel] -``` - -The contegorized content can be shown over this URL: - -## RSS - -The generated [RSS feed](https://en.wikipedia.org/wiki/RSS) of your blog can be found at . You can see the example RSS feed over [here](https://www.amitmerchant.com/reverie/feed). - -## Sitemap - -The generated sitemap of your blog can be found at . You can see the example sitemap feed over [here](https://www.amitmerchant.com/reverie/sitemap). - -## License - -MIT - - diff --git a/_posts/2019-08-08-no-title-posts.md b/_posts/2019-08-08-no-title-posts.md deleted file mode 100644 index d14509ea8..000000000 --- a/_posts/2019-08-08-no-title-posts.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -layout: post -title: "" -categories: Miscellaneous ---- -Sometimes, your post just stands for itself and doesn't need a title. And that's fine, too! \ No newline at end of file diff --git a/_posts/2019-12-11-pullquotes.md b/_posts/2019-12-11-pullquotes.md deleted file mode 100644 index 647f4edd1..000000000 --- a/_posts/2019-12-11-pullquotes.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -layout: post -title: Pullquotes -categories: [HTML,Code] -excerpt: In graphic design, a pull quote (also known as a lift-out pull quote) is a key phrase, quotation, or excerpt that has been pulled from an article and used as a page layout graphic element, serving to entice readers into the article or to highlight a key topic. ---- - -In graphic design, a pull quote (also known as a lift-out pull quote) is a key phrase, quotation, or excerpt that has been pulled from an article and used as a page layout graphic element, serving to entice readers into the article or to highlight a key topic. {% include pullquote.html quote="It is typically placed in a larger or distinctive typeface and on the same page." %} Pull quotes are often used in magazine and newspaper articles, annual reports, and brochures, as well as on the web. They can add visual interest to text-heavy pages with few images or illustrations. - -Placement of a pull quote on a page may be defined in a publication's or website's style guide. Such a typographic device may or may not be aligned with a column on the page. Some designers, for example, choose not to align the quote. In that case, the quotation cuts into two or more columns, as in the example shown. Because the pull quote invites the reader to read about the highlighted material, the pull quote should appear before the text it cites and, generally, fairly close to it. - -Pull quotes need not be a verbatim copy of the text being quoted; depending on a publication's house style, pull quotes may be abbreviated for space or paraphrased for clarity, with or without indication. - -A disadvantage of pull quotes as a design element is that they can disrupt the reading process of readers invested in reading the text sequentially by drawing attention to ghost fragments out of context. At the other extreme, when pull quotes are used to break up what would otherwise be a formless wall of text, pull quote can serve as visual landmarks to help the reader maintain a sense of sequence and place. \ No newline at end of file diff --git a/_posts/2019-7-27-super-long-article.md b/_posts/2019-7-27-super-long-article.md deleted file mode 100644 index d148630e9..000000000 --- a/_posts/2019-7-27-super-long-article.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -layout: post -title: Some articles are just so long they deserve a really long title to see if things will break well -categories: Miscellaneous ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce bibendum neque eget nunc mattis eu sollicitudin enim tincidunt. Vestibulum lacus tortor, ultricies id dignissim ac, bibendum in velit. Proin convallis mi ac felis pharetra aliquam. Curabitur dignissim accumsan rutrum. In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. Proin eget nibh a massa vestibulum pretium. Suspendisse eu nisl a ante aliquet bibendum quis a nunc. Praesent varius interdum vehicula. Aenean risus libero, placerat at vestibulum eget, ultricies eu enim. Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce bibendum neque eget nunc mattis eu sollicitudin enim tincidunt. Vestibulum lacus tortor, ultricies id dignissim ac, bibendum in velit. Proin convallis mi ac felis pharetra aliquam. Curabitur dignissim accumsan rutrum. In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. Proin eget nibh a massa vestibulum pretium. Suspendisse eu nisl a ante aliquet bibendum quis a nunc. Praesent varius interdum vehicula. Aenean risus libero, placerat at vestibulum eget, ultricies eu enim. Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce bibendum neque eget nunc mattis eu sollicitudin enim tincidunt. Vestibulum lacus tortor, ultricies id dignissim ac, bibendum in velit. Proin convallis mi ac felis pharetra aliquam. Curabitur dignissim accumsan rutrum. In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. Proin eget nibh a massa vestibulum pretium. Suspendisse eu nisl a ante aliquet bibendum quis a nunc. Praesent varius interdum vehicula. Aenean risus libero, placerat at vestibulum eget, ultricies eu enim. Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. diff --git a/_posts/2019-7-27-this-post-demonstrates-post-content-styles.md b/_posts/2019-7-27-this-post-demonstrates-post-content-styles.md deleted file mode 100644 index 99e68c5fe..000000000 --- a/_posts/2019-7-27-this-post-demonstrates-post-content-styles.md +++ /dev/null @@ -1,95 +0,0 @@ ---- -layout: post -title: This post demonstrates post content styles -categories: Miscellaneous ---- - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce bibendum neque eget nunc mattis eu sollicitudin enim tincidunt. Vestibulum lacus tortor, ultricies id dignissim ac, bibendum in velit. Praesent varius interdum vehicula. Aenean risus libero, placerat at vestibulum eget, ultricies eu enim. Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. - -## Some great heading (h2) - -Proin convallis mi ac felis pharetra aliquam. Curabitur dignissim accumsan rutrum. In arcu magna, aliquet vel pretium et, molestie et arcu. - -Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. Proin eget nibh a massa vestibulum pretium. Suspendisse eu nisl a ante aliquet bibendum quis a nunc. Praesent varius interdum vehicula. Aenean risus libero, placerat at vestibulum eget, ultricies eu enim. Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. - -## Another great heading (h2) - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce bibendum neque eget nunc mattis eu sollicitudin enim tincidunt. Vestibulum lacus tortor, ultricies id dignissim ac, bibendum in velit. - -### Some great subheading (h3) - -Proin convallis mi ac felis pharetra aliquam. Curabitur dignissim accumsan rutrum. In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. - -Phasellus et hendrerit mauris. Proin eget nibh a massa vestibulum pretium. Suspendisse eu nisl a ante aliquet bibendum quis a nunc. - -### Some great subheading (h3) - -Praesent varius interdum vehicula. Aenean risus libero, placerat at vestibulum eget, ultricies eu enim. Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. - -> This quote will change your life. It will reveal the secrets of the universe, and all the wonders of humanity. Don't misuse it. - -Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce bibendum neque eget nunc mattis eu sollicitudin enim tincidunt. - -### Some great subheading (h3) - -Vestibulum lacus tortor, ultricies id dignissim ac, bibendum in velit. Proin convallis mi ac felis pharetra aliquam. Curabitur dignissim accumsan rutrum. - -```html - - - - -

    Hello, World!

    - - -``` - - -In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. - -#### You might want a sub-subheading (h4) - -In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. - -In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. - -#### But it's probably overkill (h4) - -In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. - -### Oh hai, an unordered list!! - -In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. - -- First item, yo -- Second item, dawg -- Third item, what what?! -- Fourth item, fo sheezy my neezy - -### Oh hai, an ordered list!! - -In arcu magna, aliquet vel pretium et, molestie et arcu. Mauris lobortis nulla et felis ullamcorper bibendum. Phasellus et hendrerit mauris. - -1. First item, yo -2. Second item, dawg -3. Third item, what what?! -4. Fourth item, fo sheezy my neezy - - - -## Headings are cool! (h2) - -Proin eget nibh a massa vestibulum pretium. Suspendisse eu nisl a ante aliquet bibendum quis a nunc. Praesent varius interdum vehicula. Aenean risus libero, placerat at vestibulum eget, ultricies eu enim. Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. - -Praesent nulla tortor, malesuada adipiscing adipiscing sollicitudin, adipiscing eget est. - -Proin eget nibh a massa vestibulum pretium. Suspendisse eu nisl a ante aliquet bibendum quis a nunc. - -### Tables - -|Title 1 | Title 2 | Title 3 | Title 4 | -|--------------------- | --------------------- | --------------------- | ---------------------| -|lorem | lorem ipsum | lorem ipsum dolor | lorem ipsum dolor sit| -|lorem ipsum dolor sit | lorem ipsum dolor sit | lorem ipsum dolor sit | lorem ipsum dolor sit| -|lorem ipsum dolor sit | lorem ipsum dolor sit | lorem ipsum dolor sit | lorem ipsum dolor sit| -|lorem ipsum dolor sit | lorem ipsum dolor sit | lorem ipsum dolor sit | lorem ipsum dolor sit| diff --git a/_posts/2019-7-28-super-short-article.md b/_posts/2019-7-28-super-short-article.md deleted file mode 100644 index ddb155b7f..000000000 --- a/_posts/2019-7-28-super-short-article.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -layout: post -title: Some articles are just so short that we've to make the footer stick -categories: Miscellaneous ---- - -Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. \ No newline at end of file diff --git a/_posts/2019-8-12-code-snippets.md b/_posts/2019-8-12-code-snippets.md deleted file mode 100644 index 6605910c1..000000000 --- a/_posts/2019-8-12-code-snippets.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -layout: post -title: Code snippets in a blog post -categories: [HTML,Code] ---- - -This post demonstrate the use of code snippets in the theme. The code snippets are powered by [Pygments](http://pygments.org/) and the code theme that is been used in Reverie is called [Draula](https://draculatheme.com/). - -This is a raw snippet: - -``` -hello world -123 -This is a text snippet -``` - -This is a PHP snippet: - -```php - -``` - -This is a JavaScript snippet: - -```js -const add = (a, b) => a + b -const minus = (a, b) => a - b - -console.log(add(100,200)) // 300 -console.log(minus(100,200)) // -100 -``` - -This is a Python snippet: - -```python -def say_hello(): - print("hello world!") - -say_hello() // "hello world!" -``` diff --git a/assets/style.scss b/assets/style.scss index f54b5b4d6..63432857f 100644 --- a/assets/style.scss +++ b/assets/style.scss @@ -459,7 +459,7 @@ body:after { text-align: center; font-weight: bold; font-kerning: auto; - font-feature-settings: "kern","liga","dlig","hlig","cswh"; + //font-feature-settings: "kern","liga","dlig","hlig","cswh"; line-height: 1.2; } diff --git a/favicon.ico b/favicon.ico index ba16a471b..5a75054b5 100644 Binary files a/favicon.ico and b/favicon.ico differ diff --git a/images/modsec.png b/images/modsec.png new file mode 100644 index 000000000..7527602cc Binary files /dev/null and b/images/modsec.png differ